TJ, It's an important distinction that the original bug submitter's keyfiles are listed as being located on /etc, whereas yours are on an external USB device. If your keys aren't on the root device, then yes, decrypting the devices is not going to work reliably at boot because there's no way for the cryptdisks-udev job to know it's supposed to wait for this other device to be mounted.
You can customize /etc/init/cryptdisks-enable.conf for your environment by editing its start line to: start on stopped udevtrigger and mounted MOUNTPOINT=/mountpoint/for/my/keys to ensure the cryptsetup upstart job doesn't run before the USB disk is mounted. However, I know of no general fix for this that's going to work with an event-driven boot because the start condition will be different for each user. Daniel, unless your key files are actually symlinked to some other partition, this also doesn't address the problem you were seeing, so it would be helpful to have a mountall log from your system as well. -- lucid: Failure to bring up cryptsetup devices by key files (when not using "splash") https://bugs.launchpad.net/bugs/532898 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
