Update: On Tue, Oct 28, 2008 at 8:20 AM, Joe Landman <joe.landman@xxxxxxxxx> wrote: > On Tue, Oct 28, 2008 at 2:43 AM, Luca Berra <bluca@xxxxxxxxxx> wrote: >> On Mon, Oct 27, 2008 at 08:34:01AM -0400, Joe Landman wrote: [..] >>> This implies that /etc/mdadm.conf is in the initrd. Peeking inside >>> the default centos one, I can see that this is not true. Which >>> implies that it doesn't see /etc/mdadm.conf before it assembles the >>> array, as the /etc/mdadm.conf is on the array, and not in the initrd >>> image. >>> >>> Is there a way to include the /etc/mdadm.conf into the initrd? >> >> mkinitrd should include mdadm and /etc/mdadm.conf if it decides your >> root is on md > > Ok. This is what I think (e.g. am guessing) is the likely culprit at > the moment. In fact, now looking at the generated initrd and the base distro initrd, neither one has mdadm.conf nor mdadm. > > [...] > >>>>> Any suggestions? More things to read? >>>> >>>> is your fstab correct? >>> >>> Yes. Boots fine with older kernel. fstab doesn't change between the two. >> >> i mean, mkinitrd reads /etc/fstab to decide what your root device is, >> sometimes it fails and creates a wrong initrd > > Ok. I was unaware that it would build an incorrect initrd, I thought > we could just miss the modules if they weren't explicitly included > using --with= or similar. I have seen that with a number of RAID > cards, that mkinitrd will not generate a workable initrd (no software > RAID) as it leaves out the right drivers. I have been (defensively) > including RAID card drivers in our initrd builds. It looks like nash is the thing responsible for raidautorun, and it doesn't look like this is doing the right thing in the generated initrd. Will post the captured trace from nash on downwards soon. -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
