On Mon, 2016-04-18 at 15:34 +0200, Miquel van Smoorenburg wrote: > We (as in the company I work for) have a bunch of wheezy boxes on which > a 3.16 wheezy-backports kernel is installed: > > ii linux-image-3.16.0-0.bpo.4-amd64 3.16.7-ckt25-2~bpo70+1 > ii linux-image-amd64 3.16+63~bpo70+1 > > Sometimes (not always) a box fails to boot and ends up in the > (initramfs) prompt. We found out that this only happened on boxes with > LVM, and it appears to be a timing issue. If you run the 'lvm2' script > by hand, the system resumes booting: [...] > One of my collegues found out that by installing the 'udev' from > wheezy-backports, the problem goes away. It seems that a newer kernel > needs a newer udev. Or perhaps it is a heisenbug that gets masked by > installing a newer udev. [...] I'm fairly sure this is not a fault in udev, but in initramfs-tools and lvm2 (bugs #678696, #762984). Those were fixed in jessie but can't practically be backported. As a workaround, you can use the kernel parameter 'rootdelay=N' for a sufficiently large value of N. Ben. -- Ben Hutchings Always try to do things in chronological order; it's less confusing that way.
Attachment:
signature.asc
Description: This is a digitally signed message part