Wes Kurdziolek wrote: > > When I did an MDK 9.0 install that resembled this (ext3 /boot, RAID-0 /, > /usr, /usr/local, /var/, and /tmp -- yes, performance is critical), the > system failed to come up after rebooting b/c the raid0 module was not > included in the initrd and/or not loaded by the initrd's linuxrc script > therefore / couldn't be mounted. I believe this is a simple fix that > involves checking to see if / is a software RAID volume, including the > correct module in the initrd, and loading it in the initrd's linuxrc. I > will submit a patch if someone can tell me if this is part of mdkinst or > mkinitrd that is broken.
This was my first guess as well, but the system still wouldn't come up after I built my own initrd with raid1 and raid5 support. I added aliases for md-personality-3 and md-personality-4 to /etc/modules.conf, but no luck. Every array would still fail to startup with "kmod: failed to exec /sbin/modprobe -s -k md-personality-x, errno=2\n md: personality x is not loaded!". I would guess that Mandrake's initrd has RAID support built in (they would have to go out of their way to exclude it, which seems unlikely). Although this looks like the problem, it seems actually to be more fundamental. > Also, the diskdrake that comes with 9.0 seems to have some issues with > software RAID as well: in order to get my server up and running, I first > installed w/ an ext3 /boot and a just big enough ext3 /. Then after a > successful reboot, I fired up diskdrake and proceeded to create software > RAID partitions and then volumes. When it successfully created all my > mount points and moved the files (all except / -- non-RAID-0 performance > is fine), and I exited, diskdrake saved my changes and recommended I > reboot. Upon doing so, none of the software RAID volumes came up -- they > all had invalid superblocks (but *were* recognized as Linux software > RAID autodetect partitions), and my system was useless (had to > reinstall). This leads me to believe that diskdrake never actually ran > mkraid on the new volumes, just raidstart. I will poke around diskdrake > this week if I get a chance to see if that is true. Is the clue the reference to RAID-0? Did you move /boot to a RAID-0 array? If so, this will fail. Alternatively, you are hitting the same problem as before. Try building a kernel with support for whichever RAID levels you need. As long as /boot is not on RAID-0 or RAID-5, this should work. Cheers, Bruno
