1 |
On Thursday 28 December 2006 12:06, "Peter Humphrey" <prh@××××××××××.uk> |
2 |
wrote about '[gentoo-amd64] SATA mdraid woes': |
3 |
> Then I'm invited to specify another device, or enter a shell. I use the |
4 |
> shell to say "ls -l /dev/md2", which shows the block device I expect to |
5 |
> see, but "cat /dev/md2" returns an empty result. If I do that from the |
6 |
> installation CD I get a dump of the contents of the md disk, so it seems |
7 |
> that the node exists but it isn't connected to the array /dev/md2. |
8 |
|
9 |
I have the same symptoms on my RAID 0, although I have a slightly different |
10 |
setup. I am able to boot because although the RAID 0 is a pv in my single |
11 |
vg LVM setup, all the data for my root lv is on other disks, but I haven't |
12 |
been able to boot unattended for many months now. |
13 |
|
14 |
Anyway, I have two suggestions for you. First, use your favorite fdisk |
15 |
tool to confirm all your RAID partitions are set to be RAID autodetect; |
16 |
some initrds and particularly the kernel code for RAID detection is very |
17 |
picky about this. [Unfortunately, this is not possible for me, since I |
18 |
put whole disks into the RAID array; not partitions.] |
19 |
|
20 |
If that fails to fix the problem, you might create your own |
21 |
initrd/initramfs that includes the full mdadm tool and your mdadm.conf, |
22 |
because genkernel (and indeed all "mkinitrd"s I've run under Gentoo) just |
23 |
doesn't seem to be able to handle all RAID correctly -- in particular my |
24 |
setup has never worked, independent of the options I provide the script. |
25 |
|
26 |
-- |
27 |
"If there's one thing we've established over the years, |
28 |
it's that the vast majority of our users don't have the slightest |
29 |
clue what's best for them in terms of package stability." |
30 |
-- Gentoo Developer Ciaran McCreesh |