Hi, I am not using LVM, so I do not reproduce the exact same problem, but after upgrading to udev 168-1 my system also became unbootable.
It looks like root gets mounted (I do not use an initrd), but some disk device nodes in /dev are not yet present when the fsck are started, so they fail, and I get an emergency prompt. If I press C-d, boot continues normaly. The devices which fail to be fscked are different each time, so it looks a bit like a timing problem. With 167-3, everything is fine. I do not have a /run directory. I am a bit surprised nobody has reported this earlier, maybe people do not reboot that often... Best, -- Damien Wyart -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
