On 04/04/2010 20:52, Mark Knecht wrote:
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 don't know what the handbook says these days, but I understand that
it's lately taken to recommending a bind mount of /dev. If that's the
case, then none of the static device nodes that are contained with the
/dev directory within the stage3 tarball will actually make it on to the
root filesystem because, at the time of unpacking, they will be
redirected to the (volatile) tmpfs mount at /dev with respect to the
livecd environment.
From the point of view of the problem you're having, it may not even
matter but it's one thing to try anyway.
It's interesting that the component disks are available. In principle,
there's no reason why the array should not be assembled. Here's an
example of how it looks during the boot process on one of my systems:
Command line: root=/dev/md2
Kernel command line: root=/dev/md2 quiet
ata1: SATA max UDMA/133 cmd 0xcc30 ctl 0xcc28 bmdma 0xcc40 irq 23
ata2: SATA max UDMA/133 cmd 0xcc38 ctl 0xcc2c bmdma 0xcc48 irq 23
md: raid1 personality registered for level 1
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 6 and added 6 devices.
md: autorun ...
md: considering sdb3 ...
md: adding sdb3 ...
md: sdb2 has different UUID to sdb3
md: sdb1 has different UUID to sdb3
md: adding sda3 ...
md: sda2 has different UUID to sdb3
md: sda1 has different UUID to sdb3
md: created md2
md: bind<sda3>
md: bind<sdb3>
md: running: <sdb3><sda3>
md: kicking non-fresh sdb3 from array!
md: unbind<sdb3>
md: export_rdev(sdb3)
raid1: raid set md2 active with 1 out of 2 mirrors
md2: detected capacity change from 0 to 248798183424
md: considering sdb2 ...
md: adding sdb2 ...
md: sdb1 has different UUID to sdb2
md: adding sda2 ...
md: sda1 has different UUID to sdb2
md: created md1
md: bind<sda2>
md: bind<sdb2>
md: running: <sdb2><sda2>
md: kicking non-fresh sdb2 from array!
md: unbind<sdb2>
md: export_rdev(sdb2)
raid1: raid set md1 active with 1 out of 2 mirrors
md1: detected capacity change from 0 to 1085669376
md: considering sdb1 ...
md: adding sdb1 ...
md: adding sda1 ...
md: created md0
You might consider disabling the framebuffer temporarily, as it may
impact upon your ability to see what's going on early during the boot
process.
Cheers,
--Kerin
