Comment 31 for bug 473615

Revision history for this message
Sven 'Darkman' Michels (sven+launchpad) wrote :

Hi,

i've the same issue which is driving me nuts actually.

Setup is Ubuntu 9.10 with /home and swap encrypted (setup since 6.10 or so, can't remeber exactly when i added it). It worked fine till 9.10, then the insane problems started. It sometimes work (e.g. i can enter the passphrase at boot) but mostly i'm unable to boot
my maschine since the boot process just hangs.

Today, the problem even got worse. I updated my box today, which installed a new kernel, so i had to reboot. Interesting thing is, that last time i rebooted (28th Jan iirc) i got prompted for my passphrase at the "gui" (i think its upsplash) and all worked fine. So i thought the Problem is gone. Today, nothing(!) works. In the past, a few reboots made it work from now and then and i "accepted" the workaround. Today, even 20 times of booting made it impossible to enter a passphrase at all. The upsplash only shows that one or more devices (/home in this case) failed to mount and offers me a rescue console when pressing ESC. This console works for, lets say a minute or two, after that, next to 0 keystrokes made it to the console. A few times i saw output from cryptosetup which seems to "get" my rootpassword (when entering the rescue console, it asks for the root password, but the keystrokes seems to get to cryptsetup, but only a few/sometimes...) and thus still fails to boot. If i try to enter my cryptodisk password, i got a failed login, so i don't know when i'm able to enter what ;)

After a few workarounds etc. i found, still nothing worked. The workarounds i tried: bootwait to mountpoint, removed "splash" from the kernelparameters, trying to switch to a non gui runlevel... so the good old /etc/init.d/cryptodisks restart && mount /home gave me back my home (i just have to be quick enough) and with crtl + d the boot process continues normally... and voila,
here i am...

So for me, the new version of cryptsetup seems to made it better in the first (reboot of 28th january worked fine), but something after that made it even worse. The following packages where installed since 28th jan:

hal 0.5.13-1ubuntu8
man-db 2.5.6-2
libfuse2 2.7.4-1.1ubuntu4.3
fuse-utils 2.7.4-1.1ubuntu4.3
libwbclient0 2:3.4.0-3ubuntu5.4
libsmbclient 2:3.4.0-3ubuntu5.4
samba-common 2:3.4.0-3ubuntu5.4
smbclient 2:3.4.0-3ubuntu5.4
samba-common-bin 2:3.4.0-3ubuntu5.4
libc-bin 2.10.1-0ubuntu16
initramfs-tools 0.92bubuntu53
man-db 2.5.6-2
hicolor-icon-theme 0.10-2
desktop-file-utils 0.15-2ubuntu1
menu 2.1.41ubuntu1
libid3-3.8.3c2a 3.8.3-7.2ubuntu2
id3v2 0.1.11-4
vorbis-tools 1.2.0-6
gtkpod-data 0.99.14-2ubuntu3
gtkpod 0.99.14-2ubuntu3
libc-bin 2.10.1-0ubuntu16
menu 2.1.41ubuntu1
man-db 2.5.6-2
hicolor-icon-theme 0.10-2
desktop-file-utils 0.15-2ubuntu1
linux-image-2.6.31-19-generic 2.6.31-19.56
libdevkit-power-gobject1 011-1ubuntu2
devicekit-power 011-1ubuntu2
libgtk2.0-common 2.18.3-1ubuntu2.2
libgtk2.0-0 2.18.3-1ubuntu2.2
libgtk2.0-dev 2.18.3-1ubuntu2.2
libgail18 2.18.3-1ubuntu2.2
libgail-common 2.18.3-1ubuntu2.2
libgtk2.0-0-dbg 2.18.3-1ubuntu2.2
gtk2-engines-pixbuf 2.18.3-1ubuntu2.2
gnome-power-manager 2.28.1-0ubuntu1.3
libgtk2.0-bin 2.18.3-1ubuntu2.2
linux-image-generic 2.6.31.19.32
linux-generic 2.6.31.19.32
linux-headers-2.6.31-19 2.6.31-19.56
linux-headers-2.6.31-19-generic 2.6.31-19.56
linux-headers-generic 2.6.31.19.32
linux-libc-dev 2.6.31-19.56
python-ubuntuone-storageprotocol 1.0.1-0ubuntu1
python-ubuntuone-client 1.0.3-0ubuntu1
ubuntuone-client 1.0.3-0ubuntu1
ubuntuone-client-gnome 1.0.3-0ubuntu1
libc-bin 2.10.1-0ubuntu16

any ideas?

Thanks and regards,
Sven