On Mon, Oct 27, 2008 at 1:56 PM, Doug Ledford <dledford@xxxxxxxxxx> wrote: > On Mon, 2008-10-27 at 10:36 -0600, Brendan Conoboy wrote: >> Joe Landman wrote: [...] > Keep in mind that mkinitrd senses what it needs to boot the machine from > the currently running setup. So, if you run mkinitrd with a root raid > array, it should detect that it needs to start the md raid device, copy > mdadm.static and mdadm.conf to the initrd, and add the appropriate lines > to the initrd script. If you aren't running the md raid array (maybe It did not copy mdadm.static or mdadm.conf. Interesting. I added the "-x" argument, and instrumented the handleraid function so I could see what it was doing. It looks like I have to dig into this deeper. > it's a raid1 and you just mounted a bare member long enough to create an > initrd for instance), then it won't. But, since the system works with a > centos provided kernel, and not with the custom kernel, I'm guessing > that this isn't the issue, that mkinitrd is just fine, and instead the > custom kernel's config is somehow fubar'ed and that's what's causing all > the problems. Hmmm... not likely. My rationale for that is that the same kernel (identical .config) runs perfectly in this mode (software RAID1) on a Ubuntu/Debian machine (the exact same machine, e.g. same physical hardware, different OS load, as it turns out). Moreover, this kernel has been in production for months at many sites with nary a peep as to problems (it actually solves other problems for users with stock kernels). Will dig into this more, and let people know what I find. It seems the consensus is that there should be an mdadm.conf and mdadm.static in the initrd, and I'll see if the mkinitrd generates this correctly or not. Note that I didn't see this in the default initrd, I will look again. > > -- > Doug Ledford <dledford@xxxxxxxxxx> > GPG KeyID: CFBFF194 > http://people.redhat.com/dledford > > Infiniband specific RPMs available at > http://people.redhat.com/dledford/Infiniband > > -- 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
