My /etc/raidtab file for my /dev/md0 device is as follows.


raiddev /dev/md0
        raid-level              5
        nr-raid-disks   4
        nr-spare-disks  0
        chunk-size              4
device  /dev/sda1
raid-disk               0
device  /dev/sdb1
raid-disk               1
device  /dev/sdc1
raid-disk               2
device  /dev/sdd1
raid-disk               3

As far as I know, this is correct.  And has worked before under kernel
version 2.2.5, now I have upgraded to Mandrake Linux v6.0 with kernel ver
2.2.9, and the raid-tools that accompanied the distribution.

When I do a "mkraid --force /dev/md0", it apparently writes a
raid-superblock to each partition included in /etc/raidtab for the /dev/md0
device, but then it craps out and aborts, with no further diagnostic
information.  Nothing in the syslog and mdstat reports nothing more than I
have the Raid 4/5 personality registered, read-ahead not set and /dev/md0
still inactive?

What the heck is going on??? I have been pulling out my hair for days trying
to solve this one...

My hardware is as follows...

Asus P2B-DS - Adaptec 7890 SCSI Onboard
2 x P3-450 CPU
1 3.2 GB Udma Bootup/System Drive
4 9.1 Gb IBM 7200 rpm 2Mb Cache U2W SCSI Drives
256Mb PC-100 SDRAM
Mandrake Linux v 6.0
Mandrake SMP Kernel 2.2.9-19

Any information would be immensely appreciated.

Best Regards,


Matthew Coene.
-Systems Administrator





Matthew Coene

- Technical Support & Asst. Systems Admin
  Alliance Gas

- Question the Knowledge - Know the Question -
BEGIN:VCARD
VERSION:2.1
N:Coene;Matt
FN:Matt Coene
NOTE:Systems Support Technician
EMAIL;PREF;INTERNET:[EMAIL PROTECTED]
REV:19990428T164303Z
END:VCARD

Reply via email to