This also seems to affect a /home on a regular old LVM volume (no encryption, nothing special). During the boot sequence, udev, complains about some bits of its files which it doesn't understand. "%k" warnings and "SYMLINK" errors. I'll see if I can get a photo of the boot screen if that'll help.
Isn't this just a case of mountall waiting for devices to appear when they actually need extra help to appear? (vgchange -a y, comes to mind for LVM.) -- mountall blocks boot before cryptsetup is started https://bugs.launchpad.net/bugs/430496 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
