Bug#480334: Regression: local-top scripts run before devices detected

[maximilian attems <max@stro.at>]

tags 480334 moreinfo
stop

On Fri, May 09, 2008 at 10:01:15AM -0400, R. Scott Bailey wrote:
> 
> This seems very similar to reported (old) bugs, but it's a change in 
> behavior for me so I'm opening this new problem to flag it. I recently 
> updated to version 0.92 (I believe -- a couple days prior to 0.92a, 
> which also exhibits the problem). Boots using initrds built after that 
> upgrade do not complete automatically...
> 
> scripts/local-top/mdadm runs immediately, without waiting for device 
> discovery to complete, and of course fails to start anything because the 
> devices don't exist (usually for about another 30-40 seconds). Then lvm2 
> can't find anything, and after a timeout I get punted into the shell.
> 
> Manual recovery (assuming I sit in front of the system) is easy:
> # scripts/local-top/mdadm
> # scripts/local-top/lvm2
> # exit
> 
> But this sucks for unattended reboots, obviously. :-p Maybe I should 
> blame udev instead, but I don't know how to finger the guilty party.

well your report leaves many question opens.
as the corresponding code is untouched between 0.91 and 0.92.
i'd guess the change in behaviour is due to newer kernel.

a quick workaround is to use the roodelay boot param.
see man initramfs-tools
 
-- 
maks