On Sun, Apr 4, 2010 at 12:29 PM, Kerin Millar <kerfra...@gmail.com> wrote: <SNIP> > > Ah, that looks better. Not that I've pored over every line, but at first > glance everything seems to be in order. There are no obvious gotchas that I > can see, so I'm somewhat puzzled.
As am I! > > Here are a few random things that spring to mind though ... > > I would suggest switching off CONFIG_IDE. It may contend for control of your > hardware with the AHCI driver, assuming that emulation/comptability mode is > enabled in the BIOS. > > The device nodes may be unavailable at the time that they are needed, for > some strange reason. If you mount the root filesystem from a livecd (with no > bind mounts), try creating static nodes in dev/: > > mknod /dev/md0 b 9 0 > mknod /dev/md1 b 9 1 > mknod /dev/md2 b 9 2 > mknod /dev/md3 b 9 3 So this suggests that because I did the install from a running Gentoo chroot that the mknod commands didn't stick? Somehow they were part of, or because part of, the host Gentoo non-RAID install? Interesting. I'll boot next ffrom the Live CD and try it. > > Note that the preferred minor of your array can be determined by examining > any component partition. For instance, "mdadm -E /dev/sdb3". That's what I thought from the install guide but it seemed others here had other opions. > > Avoid manual specification of the RAID parameters. The kernel should be > perfectly able to assemble the array by examining the superblocks of > partitions of type "FD". > > Does it work if you specify "root=/dev/sdb3" or "root=/dev/sdc3"? With > raid1, it's possible to mount just the component partition (although it will > later result in a resync). The point is, it would at least confirm as to > whether the underlying block devices are available to the kernel from the > outset. OK, this was interesting, and I suppose it depends on what you mean 'should work'. Clearly it gets much further, into the interactive portion of the boot with the green asterics on the right. When it finally gets to the md0 portion it says the the superblock does not correctly specify an ext2 filesystem and asks for a password or Control D. Control D reboots and entering the password results in a (none) prompt and seems to require a hard reset. None the less it got much further, but not to a usable state. Off to do the Live CD work. Back in 30 minutes. Cheers, Mark
