cryptsetup does not ask for password during graphical boot on karmic

[Laurens]

Binary package hint: cryptsetup

Since a few weeks ago my Ubuntu Karmic no longer asks for the encrypted root partition during startup. If I start in recovery mode it however does ask me for the password and the system boots normally (although in text mode).

Expected result:
Graphical boot requests password and mounts LVM.

Actual result:
Graphical boot just hangs.

I set up my encrypted LVM according to the instructions that can be found here:

https://help.ubuntu.com/community/EncryptedFilesystemLVMHowto

Ubuntu 9.10 karmic (development branch)
Cryptsetup version 2:1.0.6+20090405.svn49-ubuntu1

Please let me know if you need additional information.

[Laurens (laurensb)]

This bug still exists in the lastest Karmic. Seems to be a problem with "askpass".

[evanjfraser (evanjfraser)]

I seem to have a very similar problem, although it occurs on both graphical and recovery mode.

After recovery mode drops to busybox shell I can then manually type:

cryptsetup luksOpen /dev/sda1 root

enter the password
exit busybox

And then it resumes booting fine.

My system is upgraded from jaunty rather than a clean karmic alpha install.

[Andrzej Wójcik (andrzej-hi-low)]

Same for me after update from Jaunty to Karmic I'm not asked about password to encrypted filesystems.

However whole cryptofs works fine if I use mainline kernel version so bug can be caused by succesor of usplash.

[Laurens (laurensb)]

Actually it started working for me again a few days ago. This may caused by an upgrade to usplash 0.5.33, usplash-theme-ubuntu 0.24, initramfs-tools 0.92ubuntu38, or {sysvinit-utils,initscripts,sysv-rc} 2.86.ds-61ubuntu16. I'm not sure which one (of even if it is one of these).

evanjfraser, Hantu, could you check the versions of the above mentioned packages you have installed?

[evanjfraser (evanjfraser)]

Hi Laurens,
I'm sorry about the long time since responding. The problem still occurs for me, and my package versions are newer than those you have listed above:

usplash 0.5.37
usplash-theme-uibuntu 0.25
initramfs-tools 0.92bubuntu46
sysvinit-utils 2.87dsf-4ubuntu3

Many thanks,

Evan.

[Saivann Carignan (oxmosys)]

This should probably be fixed by recent updates in cryptsetup (see bug 430496).

Laurens : With a completely uptodate cryptsetup package, can you confirm if you can still reproduce the bug?

[Reinhard Tartler (siretart)]

The referenced help.ubuntu.com website decribes various ways to setup a crypted filesystem. Which configuration do you use? Please always attach your /etc/crypttab.

FWIW, root on crypted LVM worked for me all the time, because in that configuration, all magic is done in the initramfs, before any upstart magic can jump in. Bug 430496 is about decrypting devices from the init script.

[Garland (garland.zero)]

Hi, I just upgraded from jaunty, and have the problem that I am not being asked for the password during system startup, but am able to do the neccessary steps by hand once the recovery console have started.

My crypttab:
enchome /enc/home none luks

My fstab:
/dev/mapper/enchome /home jfs noatime 0 2

On the recovery console i use
cryptdisks_stop enchome
cryptdisks_start enchome
fsck /dev/mapper/enchome
mount /dev/mapper/enchome /home
Ctrl-D

[Garland (garland.zero)]

The message before is:

One or more of the mounts listed in /etc/fstab cannot yet be mounted:
/home: waiting for /dev/mapper/enchome
/var/tmp: waiting for tmpfs
Press ESC to enter a recovery shell

[Steve Langasek (vorlon)]

The problem as originally described should have been fixed well before the karmic released, and the bug submitter appears to confirm this in comment #4. Marking as fixed.