On Mon, 30 Mar 2009, 00:19:59 +0200, Joe Morris wrote:
On 03/30/2009 02:03 AM, Manfred Hollstein wrote:
On Sun, 29 Mar 2009, 18:50:38 +0200, Florian Gleixner wrote:
Hi,
thanks, that did the trick. When looking at the script i wonder why the script tries to find the md device of the root device. It does not matter if the root device resides on a md. It should simply include all running or configured md devices or do i miss something?
that's exactly what my patch does, but the reason for the way how the original script works is probably some kind of an optimization; imagine you're using some complicated setup with about 20 md's; scanning all available block devices for the UUIDs noted in /etc/mdadm.conf can take some time (depending on which kind of devices are connected...), and I remember some e-mail threads about how booting the system can be made faster.. ;-) But for this optimization to be valid, it should simply work!
From the README.initramfs file in the mdadm package, "It should be noted up front that only the array containing the root filesystem should be assembled from the initramfs. Any other arrays should be assembled under the control of files on the main filesystem as this enhanced flexibility and maintainability."
While this is true in general, I'm just using the host's /etc/mdadm.conf file from inside the initrd, so the arrays should look exactly the same as they will after potential re-assembly later on.
So it appears this has more to do with the creation of the device nodes needed while running from the initrd than anything else. I wonder if it has any relation to bnc#445490. But this fix is in the mkinitrd package. I may need to do some experimenting... Can you tell Manfred? I am not a programmer.
It may be related, but my situation was different, as for me (remember, I'm still on openSUSE 10.3!) the bug was caused by mkinitrd (or one of its scripts) identifying the wrong md-device to be used for the root file system :-( You should unpack the generated initrd and look at its etc/mdadm.conf file; I bet you'll find some inconsistencies compared to the one from your root file system at /etc/mdadm.conf . Did you try, if my patch helps in your situation? You just need to ensure, that your system has a valid /etc/mdadm.conf file before you run mkinitrd. HTH, cheers. l8er manfred -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org