I think I have the same issue. I have two random key encrypted drives, /tmp and swap, but the problem (so far) only seems to happen with /tmp. The problem seems to be intermittent, but still happens on maybe 50% or more of boots. I can't get a boot log because upstart doesn't appear to use them. I've tried to get around the problem by forcibly mounting /tmp in the init script for GDM with a sleep interval of 5 seconds (as well as changing ownerships on the directory which, due to the drive being wiped on every boot aren't being saved), which so far seems to have stopped the gconf-sanity-check-2 error 256 happening and lets GDM work fine, but every couple of boots I get thrown back to a recovery console because /tmp failed to mount. After checking the boot messages without splash it seems it's trying to mount before the encryption is fully active.
cat /etc/crypttab sda4_crypt /dev/disk/by-uuid/d8ae7e62-57ba-4742-8121-179394693901 none luks sda5_crypt /dev/sda5 /dev/urandom cipher=aes-cbc-essiv:sha256,size=128,swap sda6_crypt /dev/sda6 /dev/urandom cipher=aes-cbc-essiv:sha256,size=128,tmp -- Karmic boot doesn't wait for encrypted disc passphrase https://bugs.launchpad.net/bugs/468885 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
