I thought I was doing everything right, based on all the HOWTOs and such,
but it's not working for me.

The DASD devices have been formatted, and I even put an ext2 file system on
them (out of desperation).  I can mount them as ext2 file systems, so I know
they're accessible.
# cat /proc/dasd/devices
0300(ECKD) at (94:0) is   dasda:active  at blocksize: 4096, 600840 blocks,
2347 MB
0301(ECKD) at (94:4) is   dasdb:active  at blocksize: 4096, 600840 blocks,
2347 MB
0302(ECKD) at (94:8) is   dasdc:active  at blocksize: 4096, 600840 blocks,
2347 MB
0303(ECKD) at (94:12) is   dasdd:active  at blocksize: 4096, 600840 blocks,
2347 MB
0400(FBA ) at (94:64) is   dasdq:active  at blocksize: 512, 500000 blocks,
244 MB
0401(ECKD) at (94:68) is   dasdr:active  at blocksize: 4096, 600840 blocks,
2347 MB

Here's my /etc/raidtab:
raiddev                 /dev/md0
raid-level              linear
nr-raid-disks           2
persistent-superblock   1
chunk-size              64k
device                  /dev/dasdc1
raid-disk               0
device                  /dev/dasdd1
raid-disk               1

I have the linear.o module loaded, and /proc/mdstat shows that:
Personalities : [1 linear]
read_ahead not set
md0 : inactive
md1 : inactive
md2 : inactive
md3 : inactive

The device node is defined:
brw-r-----    1 root     root       9,   0 Apr  1  1998 /dev/md0

But, when I issue the mkraid command, I get an error:
# mkraid /dev/md0
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/dasdc1, 2403348kB, raid superblock at 2403264kB
disk 1: /dev/dasdd1, 2403348kB, raid superblock at 2403264kB
mkraid: aborted, see the syslog and /proc/mdstat for potential clues.


But, there are no messages in /var/log/messages, or dmesg, or anywhere else
that I can see.  Anybody have any ideas?

Mark Post

Reply via email to