On Thu, 17 Feb 2005 12:22:08 -0600 (CST), Nate Carlson <natecars at real-time.com> wrote: > On Wed, 16 Feb 2005, Shawn Fertch wrote: > > Now we're back to Monday... I run LVM on /dev/md4. Therefore, when I > > partition it, it comes up as /dev/md4p1. > > > /dev/sdc1 * 1 2212 17767858+ fd Linux raid autodetect > > /dev/sdd1 1 2212 17767858+ fd Linux raid autodetect > > /dev/sde1 * 1 2221 17770189+ fd Linux raid autodetect > > OK, that's what I was looking for. > > > [root at netman etc]# uname -a > > Linux netman 2.4.21-27.0.1.ELsmp #1 SMP Mon Dec 20 18:47:45 EST 2004 i686 i686 i386 GNU/Linux > > Ah - if I recall correctly, 2.4.x kernels can't do autodetect for RAID5. I > could very well be recalling incorrectly, though. > > Is mdadm or raidtools being started on bootup? (Check your init scripts.) > That should be able to figure out the array and get it going, even if the > kernel autostart didn't. > > If you're using raidtools, you might want to switch to mdadm - it has the > nifty ability to e-mail you when a drive goes belly-up. > 2.4 supports the RAID5 kernel and, I'm using raidtools which startup. Again, all of the RAID1 devices would startup, it was only the RAID5 that wouldn't on system initialization. What it wound up being was that I had to run: mkinitrd -v --preload=raid5 /boot/initrd-test.img `uname -r` Then tell grub to boot using that, and it seems to be working for the moment. Red Hat finally came thru on the support with that. I need to figure out the various options for mkinitrd as everytime I try to upgrade my kernel it blows up on me... Thanks for the help Nate, as well as others who have contributed! -- -Shawn -Nemo me impune lacessit. Ne Obliviscaris..