Earlier, I suggested a data-collection exercise involving udevd
--verbgose, but this didn't do much good because the race went away
when testing in this way.
I think this was probably due to udev writing to the console. I have
now prepared a version of udev which can be made not to write to the
c
Reinhard Tartler writes ("Re: [Bug 75681] Re: initramfs script: race condition
between sata and md"):
> Ian Jackson <[EMAIL PROTECTED]> writes:
> > 2. Run
> > /scripts/local-top/mdadm from-udev
> >(NB `from-udev' is an argument you mus
Ian Jackson <[EMAIL PROTECTED]> writes:
> 1. Check that
> cat /proc/partitions
>lists all of the components of your array. If not, then we need to
>understand why not. What are those components ? You will probably
>find that it does not list the array itself. If it does then we
Aurelien Naldi writes ("[Bug 75681] Re: initramfs script: race condition
between sata and md"):
> The array should _not_ be started _at_all_ unless all needed devices
> have been detected (including spare ones) OR when all device
> detection is done.
Unfortunately, in Linux 2.6, there is no way t
Aurelien Naldi writes ("[Bug 75681] Re: initramfs script: race condition
between sata and md"):
> The first boot went fine. The next one hanged. And the next one went
> also fine. For all of them, I get the message "no devices listed in
> cinf file were found" but it looks harmless. I do not kno
Aurelien Naldi <[EMAIL PROTECTED]> writes:
> It looks like it was fixed by recent updates, but at the expense of
> breaking LVM (my initramfs does not contain (/scripts/local-top/lvm
> anymore).
I can confirm. Latest updates changed the behavior, now the raid is
activated but not lvm. booting with
