On Tue, Oct 07, 2008 at 03:02:05PM +0200, maximilian attems wrote: > Subject: Re: lenny regression initrd/lvm/ rootfs detection timeout > > On Tue, Oct 07, 2008 at 02:20:13PM +0200, Florian Lohoff wrote: > > > > Hi, > > after upgrading an FSI RX/300 from etch to lenny the machine would not > > boot anymore. It got stuck in the initrd not beeing able to find the > > root filesystem. The cause was that the aacraid took too long to make > > the root filesystem available. Thus the boot timed out and the initrd > > waited for the root filesystem to get available. After some seconds >45 > > the root disks (sda on an aacraid) got available but the boot failed > > anyway dropping into the initrd. The cause was that the root is an lvm > > which is on that disk and the lvm does not get retried after more disks > > get available. > > > > I got the machine to boot by running /scripts/top-local/lvm2 which made > > the root filesystem in the lvm available and ctrl-d to continue booting. > > > > I think after more disks get available the initrd should retry running > > the lvm detection otherwise a lot of lvm based systems might die/get > > stuck on upgrade. > > > > I'd consider this a RC bug - no clue whose fault this is though ... > > standard answer boot with > rootdelay=X
It worked with etch without that parameter and the upgraded did not add
it so its a lenny regression - isnt it?
And in my case it was a remote reboot where the machine did not come
back - so i needed to go there physically - i am on the lucky side as
i tested with a machine next door and not 400km away ...
Flo
--
Florian Lohoff [EMAIL PROTECTED] +49-171-2280134
Those who would give up a little freedom to get a little
security shall soon have neither - Benjamin Franklin
signature.asc
Description: Digital signature
