On Sat, 3 Apr 2010 16:07:06 -0700, Mark Knecht wrote: > The install is complete but it won't boot. grub finds the kernel > and starts booting but then I get the typical VFS file sync error as > the kernel starts looking for the install on /dev/md3. What I'm not > understanding is how does the boot process get the information > required to assemble the RAID device. By hand in the non-RAID install > I do this: > > keeper ~ # mdadm -A /dev/md3 /dev/sdb3 /dev/sdc3 > mdadm: /dev/md3 has been started with 2 drives. > keeper ~ # cat /proc/mdstat > Personalities : [raid1] > md3 : active raid1 sdb3[0] sdc3[1] > 52436092 blocks super 1.1 [2/2] [UU] > > unused devices: <none> > keeper ~ # > > but when I try to boot the RAID install it says it cannot find /dev/md3.
You need to set the partition type for the RAIDed partitions to "Linux raid autodetect". You'll probably then find that the kernel sets the RAID as /dev/md0, not md3. -- Neil Bothwick "You want us to do WHAT?" - Ancient Chinese wall engineer.
signature.asc
Description: PGP signature
