On Sat, Oct 31, 2009 at 10:12:35PM -0000, Blue wrote: > This is a quite simple and straightforward scenario
Well, no, not really. To have run into the problem you did, you must have devices configured in your /etc/crypttab that are being enabled at boot time, but that are not used as the underlying devices for any core filesystems, including /, /usr, /var, or /home (or even swap). I think that's quite an unusual setup. To work around this issue, you can mark the filesystem that sits on the encrypted volume as "bootwait" in your /etc/fstab, as documented in the release notes: <http://www.ubuntu.com/getubuntu/releasenotes/910#Login%20screen%20presented%20before%20optional%20filesystems%20are%20mounted> We could do with an explicit comment there about the need for this with cryptsetup. Opening a task on ubuntu-release-notes for this. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- cryptsetup devices not mounted on boot 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
