Comment 52 for bug 430496

Did another bug get open for this (as per #49/#50)? I haven't been able to find one.

I am seeing the same behaviour as comment #25, with a brand new install of 9.10, which I then updated meaning I have cryptsetup 2:1.0.6+20090405.svn49-1ubuntu7.2 and mountall 1.0. If I don't have 'bootwait', gdm starts, but my encrypted partition isn't mounted (and switching back to tty1 there is no sign of a prompt for the passphrase). If I do set 'bootwait' for the partition, the boot stops when mounting fails. A few hits of return sometimes gives a passphrase prompt, which doesn't work, saying the passphrase is wrong, as if it's only seeing the 'return', and not any other keystrokes. After a mixture of repeated attempts (so cryptsetup fails?) or waiting for mountall to timeout (I'm guessing), I eventually managed to get a maintenance prompt, so that I could remove the 'bootwait', and at least get back in to a state where the machine booted. (trying to boot in to single user mode to remove the 'bootwait' didn't work, because it still hit the failing mount).

/etc/crypttab:
# <target name> <source device> <key file> <options>
data /dev/sda6 none luks
cswap /dev/sda5 /dev/urandom swap

/etc/fstab:
/dev/mapper/data /mnt/data ext3 defaults,relatime 1 2
/dev/mapper/cswap none swap sw 0 0

cswap appears to work *sometimes*, but usually only after a huge delay. dmesg for this boot (no 'bootwaits' in fstab) shows me that it came up after 2137 seconds.

BTW, 'data' isn't one of the 'essential' system mount points, but does contain, among other things, /home.

If there is another open bug that this should be posted to instead, let me know.

Cheers,
--Dave