[lkml]   [2000]   [Feb]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectbooting md0 (RedHat lilo patch)

I would like some help concerning a broken md0 booting configuration,
where I have no clue what can be wrong...
What have happened is that I have put two out of the three disks of the
RAID1 array on an UDMA66 add-on card, which the standard linux kernel does
not recognizes w/o Andre's patches. Once I had to boot the stock kernel
and modify /etc/rc.d/rc.sysinit (add hdparm -d0 /dev/hd[aeg]). During this
the kernel had seen, that I have a mirror set with only one drive of the
four in the system. Unfortunatelly, then I issued a lilo command, and
since that lilo is not agreeing with my raid1 md0. At first it just did
not know what to do with the device (md0). This might be ok because two
disks to write to were missing.
But when I booted an ide patched kernel, and ran lilo again, and here
comes the strangest thing: it did its work, but not for all the three
drives, az previously, but only for the middle one (e out of hd[aeg]).
Since then I am running the box with a and e swapped, so it boots, and the
arrays still autorun fine, but cannot get lilo write its stuff on the e
and g drives.

What might be the resolution for this problem?

/proc/mdstat seems ok to me...
[root@iq /root]# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid5]
read_ahead 1024 sectors
md0 : active raid1 hdg1[1] hde1[2] hda1[0] 204992 blocks [3/3] [UUU]
md1 : active raid5 hdg3[0] hde3[2] hda3[1] 2097408 blocks level 5, 64k
chunk, algorithm 0 [3/3] [UUU]
md2 : active raid5 hdg5[0] hde5[2] hda5[1] 153984 blocks level 5, 64k
chunk, algorithm 2 [3/3] [UUU]
md3 : active raid5 hdg6[0] hde6[2] hda6[1] 511872 blocks level 5, 64k
chunk, algorithm 2 [3/3] [UUU]
md4 : active raid0 hdg7[0] hde7[2] hda7[1] 675456 blocks 32k chunks
md5 : active raid0 hdg8[0] hde8[2] hda8[1] 40803456 blocks 32k chunks
unused devices: <none>

-- SaPE

Peter Sasi <>

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:56    [W:0.081 / U:1.052 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site