WARNING!!!! A word of warning to those who have removed the file 65-dmsetup.rules. I had found that this temporary fix worked quite well on all my machines, but got burned when an automatic update of cryptsetup got installed without me thoroughly considering the possible ramifications. The net result was that my machines were rendered unbootable. All I got at startup was a message that my cryptroot could not be found and then routed to a busy box.
I'm not entirely sure what happened, but think that 65-dmsetup.rules needs to be there if the update is going to update the initframfs. Without the file the update of initramfs doesn't complete. Since there is no warning of this from update manager, you're stuck with an unbootable system on restart. This was my first major panic with Linux and I spent a lot of time googling and futzing with a LiveCD before I figured out the problem and repaired the mess. Bottom Line: Avoid this situation by putting 65-dmsetup.rules back where it belongs before you run any automatic updates related to the cryptsetup. Hope this saves someone some time! -- mounting Luks encrypted USB-HDD does not work reliably https://bugs.launchpad.net/bugs/148003 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
