I can confirm I'm having this problem also. I upgraded from Jaunty to Karmic on 12/18, and haven't found a solution over the weekend.
My crypto setup follows the howto here: https://help.ubuntu.com/community/EncryptedFilesystemHowto3 My /etc/crypttab: cryptoswap /dev/sda6 /dev/urandom cipher=aes-cbc-essiv:sha256,size=256,hash=sha256,swap cryptotmp /dev/sda5 /dev/urandom cipher=aes-cbc-essiv:sha256,size=256,hash=sha256,tmp cryptohom /dev/sda1 none luks Relevant fstab entries: /dev/mapper/cryptohome /home ext4 relatime,errors=rmount-ro 0 2 /dev/mapper/cryptotmp /tmp ext2 defaults 0 2 /dev/mapper/cryptoswap none swap sw 0 0 Some output from booting: --------------------------------- fsck from util-linux-ng 2.16 fsck.ext2: Device or resource busy while trying to open /dev/mapper/cryptotmp Filesystem mounted or opened exclusively by another program? mountall: fsck /tmp [1171] terminated with status 8 mountall: General fsck error General error mounting filesystems. A maintenance shell will now be started. CONTROL-D will temrinate this shell and re-try. Enter passphrase to unlock the disk /dev/sda1 (cryptohome): -------------------------------- After this, no input is echoed until I press ctrl-D, which spits out terminal interactions of whatever I'd typed (like my passphrase), which were presumably happening in the background. Other times, it looks like this: -------------------------------- init: upstart-udev-bridge main process (545) terminated with status 1 init: upstart-udev-bridge main process ended, respawning modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.31-16-generic/kernel/drivers/crypto/padlock-sha.ko): No such device init: upstart-udev-bridge main process (1054) terminated with status 1 init: upstart-udev-bridge main process ended, respawning Enter passphrase to unluck the disk /dev/sda1 (cryptohome): One or more of the mounts listed in the /etc/fstab cannot yet be mounted: (ESC for recovery shell) /home: waiting for /dev/mapper/cryptohome -------------------------------- These two different errors error show up intermingled with the passphrase prompt. Using ctrl-alt-F1 to go to another terminal doesn't do much good here, it just has a message that it's waiting for boot. I removed crypttab and the crypto entries in fstab, and I can boot normally, though I had to chmod 777 /tmp. I can mount /dev/sda1 using cryptsetup luksOpen as normal once booted up. -- Upgrade to Karmic completely broke password prompt for cryptdisks at boot https://bugs.launchpad.net/bugs/475293 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
