| 1 |
On 04/04/2010 20:52, Mark Knecht wrote: |
| 2 |
> So this suggests that because I did the install from a running Gentoo |
| 3 |
> chroot that the mknod commands didn't stick? Somehow they were part |
| 4 |
> of, or because part of, the host Gentoo non-RAID install? Interesting. |
| 5 |
|
| 6 |
I don't know what the handbook says these days, but I understand that |
| 7 |
it's lately taken to recommending a bind mount of /dev. If that's the |
| 8 |
case, then none of the static device nodes that are contained with the |
| 9 |
/dev directory within the stage3 tarball will actually make it on to the |
| 10 |
root filesystem because, at the time of unpacking, they will be |
| 11 |
redirected to the (volatile) tmpfs mount at /dev with respect to the |
| 12 |
livecd environment. |
| 13 |
|
| 14 |
From the point of view of the problem you're having, it may not even |
| 15 |
matter but it's one thing to try anyway. |
| 16 |
|
| 17 |
It's interesting that the component disks are available. In principle, |
| 18 |
there's no reason why the array should not be assembled. Here's an |
| 19 |
example of how it looks during the boot process on one of my systems: |
| 20 |
|
| 21 |
Command line: root=/dev/md2 |
| 22 |
Kernel command line: root=/dev/md2 quiet |
| 23 |
ata1: SATA max UDMA/133 cmd 0xcc30 ctl 0xcc28 bmdma 0xcc40 irq 23 |
| 24 |
ata2: SATA max UDMA/133 cmd 0xcc38 ctl 0xcc2c bmdma 0xcc48 irq 23 |
| 25 |
md: raid1 personality registered for level 1 |
| 26 |
md: Waiting for all devices to be available before autodetect |
| 27 |
md: If you don't use raid, use raid=noautodetect |
| 28 |
md: Autodetecting RAID arrays. |
| 29 |
md: Scanned 6 and added 6 devices. |
| 30 |
md: autorun ... |
| 31 |
md: considering sdb3 ... |
| 32 |
md: adding sdb3 ... |
| 33 |
md: sdb2 has different UUID to sdb3 |
| 34 |
md: sdb1 has different UUID to sdb3 |
| 35 |
md: adding sda3 ... |
| 36 |
md: sda2 has different UUID to sdb3 |
| 37 |
md: sda1 has different UUID to sdb3 |
| 38 |
md: created md2 |
| 39 |
md: bind<sda3> |
| 40 |
md: bind<sdb3> |
| 41 |
md: running: <sdb3><sda3> |
| 42 |
md: kicking non-fresh sdb3 from array! |
| 43 |
md: unbind<sdb3> |
| 44 |
md: export_rdev(sdb3) |
| 45 |
raid1: raid set md2 active with 1 out of 2 mirrors |
| 46 |
md2: detected capacity change from 0 to 248798183424 |
| 47 |
md: considering sdb2 ... |
| 48 |
md: adding sdb2 ... |
| 49 |
md: sdb1 has different UUID to sdb2 |
| 50 |
md: adding sda2 ... |
| 51 |
md: sda1 has different UUID to sdb2 |
| 52 |
md: created md1 |
| 53 |
md: bind<sda2> |
| 54 |
md: bind<sdb2> |
| 55 |
md: running: <sdb2><sda2> |
| 56 |
md: kicking non-fresh sdb2 from array! |
| 57 |
md: unbind<sdb2> |
| 58 |
md: export_rdev(sdb2) |
| 59 |
raid1: raid set md1 active with 1 out of 2 mirrors |
| 60 |
md1: detected capacity change from 0 to 1085669376 |
| 61 |
md: considering sdb1 ... |
| 62 |
md: adding sdb1 ... |
| 63 |
md: adding sda1 ... |
| 64 |
md: created md0 |
| 65 |
|
| 66 |
You might consider disabling the framebuffer temporarily, as it may |
| 67 |
impact upon your ability to see what's going on early during the boot |
| 68 |
process. |
| 69 |
|
| 70 |
Cheers, |
| 71 |
|
| 72 |
--Kerin |
Archives