Ken,
For any dasd greater than dasdz you must run mknod
mknod -m 660 /dev/dasdaa   b 94 104
mknod -m 660 /dev/dasdaa1 b 94 105
mknod -m 660 /dev/dasdab   b 94 108
mknod -m 660 /dev/dasdab1 b 94 109

Get the major/minor node numbers from a cat of /proc/dasd/devices
I don't create nodes for partitions 2 and 3 because I don't use them.  No
harm in doing it though
mknod -m 660 /dev/dasdaa2 b 94 106   etc

Betsie
----- Original Message -----
From: "Ken Vance" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 22, 2004 9:22 AM
Subject: more than 26 disks


> Hi,
>
> We were adding a large number of disks to our SuSE8 image.  Normally, it
> adds the dasd as "dasda", "dasdb", etc.  When we added disk 27, it adds
> the dasd as "dasdaa".
>
> Here is the log when the devices were added:
>
> dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: 3390/0A(CU:3990/01) Cyl:3338
> Head:15
> dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: 3390/0A(CU:3990/01) Cyl:3338
> Head:15
> dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: DIAG210 returned VRDCRCCL = 04,
> VRDC
> dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: XRC_supported reset because of
> missi
> dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: 3390/0A(CU:3990/01):
> Configuration d
> Apr 22 13:00:02 linvm01 kernel: debug: dasdz: new level 3
> Apr 22 13:00:02 linvm01 kernel: dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]:
> 3390
> Apr 22 13:00:02 linvm01 kernel: dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]:
> DIAG
>  82
> dasd(eckd): /dev/dasdy  ( 94: 96),[EMAIL PROTECTED]: (4kB blks): 2403360kB at
> 48kB/trk li
> Apr 22 13:00:02 linvm01 kernel: dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]:
> XRC_
> Apr 22 13:00:02 linvm01 kernel: dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]:
> 3390
> Apr 22 13:00:02 linvm01 kernel: dasd(eckd): /dev/dasdy  ( 94: 96),[EMAIL PROTECTED]:
> (4kB
> debug: dasdaa: new level 3
>
> The Linux administration group then formatted and made a file system on
> the various dasd volumes.  He had a problem when he went to format the
> "dasdaa" volume.  It could not find the "dasdaa" device.  He created it,
> and then he could format it.  When he tried to make a files system, it
> again failed.  When he creates the filesystem, he specifies the dasd
> without a number, ie. "dasdj", "dasdk", etc.  I noticed in Mark Post's
> presentation , he has the following:
>
> > 2.4.x Kernels
> > mke2fs -b 4096 /dev/dasd?1,2,3
> > mke2fs -b 4096 /dev/dasda1
> > mke2fs -b 4096 /dev/dasda2
> > mke2fs -b 4096 /dev/dasda3
>
> What is the difference betweem 1, 2, and 3.  Also, why did the system not
> create the "dasdaa", and "dasdaa1" information?  Is there something
> special we must do when we reach disk number 27?  Are the numbers used if
> you partition the drive into smaller areas?  We only have one area on the
> disk, so I would guess that it would be the "1".
>
> Here is the log:
>
> linvm01:~ # dasdfmt -b 4096 -d ldl -f /dev/dasdaa
> dasdfmt: Unable to open device /dev/dasdaa: No such file or directory
>
> This was true:
>
> linvm01:~ # ls -la /dev/dasda*
> brw-rw----    1 root     disk      94,   0 Nov  6  2002 /dev/dasda
> brw-rw----    1 root     disk      94,   1 Nov  6  2002 /dev/dasda1
> brw-rw----    1 root     disk      94,   2 Nov  6  2002 /dev/dasda2
> brw-rw----    1 root     disk      94,   3 Nov  6  2002 /dev/dasda3
>
> And then (checking major/minor numbers before)
>
> linvm01:~ # mknod -m 660 /dev/dasdaa b 94 104
> linvm01:~ # ls -la /dev/dasdaa
> brw-rw----    1 root     root      94, 104 Apr 22 17:27 /dev/dasdaa
> linvm01:~ # chown root:disk /dev/dasdaa
> linvm01:~ # ls -la /dev/dasdaa
> brw-rw----    1 root     disk      94, 104 Apr 22 17:27 /dev/dasdaa
>
> Afterwards dasdformat runs without complains.
>
> linvm01:~ # dasdfmt -b 4096 -d ldl -f /dev/dasdaa
> Drive Geometry: 3338 Cylinders * 15 Heads =  50070 Tracks
>
> I am going to format the device /dev/dasdaa in the following way:
>    Device number of device : 0x274
>    Labelling device        : yes
>    Disk label              : LNX1
>    Disk identifier         : 0X0274
>    Extent start (trk no)   : 0
>    Extent end (trk no)     : 50069
>    Compatible Disk Layout  : no
>    Blocksize               : 4096
>
> --->> ATTENTION! <<---
> All data of that device will be lost.
> Type "yes" to continue, no will leave the disk untouched: yes
> Formatting the device. This may take a while (get yourself a coffee).
> Finished formatting the device.
> Rereading the partition table... ok
>
> When I tried a mkfs it failed.
>
> linvm01:/ # /sbin/mkfs.ext3 -b 4096 /dev/dasdaa
> mke2fs 1.28 (31-Aug-2002)
> mkfs.ext3: No such device while trying to determine filesystem size
> linvm01:/ # ls -la /dev/dasdaa
> brw-rw----    1 root     disk      94, 104 Apr 22 17:27 /dev/dasdaa
> linvm01:/ #
>
> Thanks,
>
> Ken Vance
> Amadeus
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to