I was about to report this exact same bug, and my patch is the same too. Without the patch, boot pauses for 3 minutes on a system with encrypted /home.
What normally happens is you enter the disk passphrase, and it would say it's unlocked and continue booting immediately. But recently, you enter the passphrase and then there are no messages after you press enter for 3 minutes. Then it continues, starting with the udev rendezvous error message. Even "failsafe" boot pauses for 3 minutes before giving you a root shell. Unless you know to wait, it seems like boot has hung - I did many reboot until I figured out that entering the _wrong_ passphrase gets me to a root shell in failsafe mode, where I could trace the problem. The patch to udev's 65-dmsetup.rules fixes this problem. (I'm not sure why cryptsetup needs to rendezvous with udev at all, though. It seems to be fine when that fails. Maybe it would be better to remove that from cryptsetup, making boot a bit faster?) Scott, I think your comment is the wrong way around. _Without_ this patch, vol_id isn't run on read-only devices - at least, not by dmsetup.rules. If you want vol_id to run on read-only devices so they are mounted by udev, you need this patch, I think. -- udev rules don't create device nodes for readonly devices https://bugs.launchpad.net/bugs/117089 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
