Public bug reported:

Binary package hint: cryptsetup

Yesterday I upgraded from ubuntu 9.04 to 9.10 and I experience the following 
problem when booting.
(everything was fine in 9.04)

What I expected to happen:
I expected to the boot luks passphrase entering procedure to be the same as in 
9.04. Boot with usplash disabled, prompt for passphrase appears, I enter the 
passphrase, boot procedure continues.

What happened instead:
I have / on a lvm volume (not encrypted) and /home on a lvm volume (luks 
encrypted).
(probably not important, but mentioning it anyway: I have /tmp as a symlink to 
/home/tmp, so /tmp may not be usable until /home is mounted)
Without usplash enabled it is almost impossible to enter the passphrase. It 
looks like multiple processes during the boot process start fighting for the 
input/output. I could not even use the recovery shell, it stopped 
working/accepting input within 10-20s. (ctrl-alt-del works, and reboots the 
machine)

After I read on launchpad that entering the passphrase will only work
with usplash enabled I was able to enter the passphrase, but I have to
enter it 3 times before it is accepted and boot continues.

The problem is worse when the machine is cold-booted, because swap uses
/dev/random as a key, I assume it takes some time to acquire enough
entropy for the key but this causes usplash to enter text mode, and
entering the passphrase becomes impossible. In this scenario the
recovery shell is functional and allows me to manually unlock the luks
partition.


crypttab:
storage01-swap_crypt /dev/mapper/storage01-swap /dev/random 
cipher=aes-cbc-essiv:sha256,size=192,swap
storage01-home_crypt /dev/mapper/storage01-home none 
luks,cipher=aes-cbc-essiv:sha256

fstab:
# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# / was on /dev/mapper/storage01-rootfs during installation
UUID=9032eca8-28c2-4d6e-bdc0-ea85d835a0f7 /               ext3    
relatime,errors=remount-ro 0       1
# /boot was on /dev/sda3 during installation
UUID=2f6b4f5a-4945-4ff5-9447-04cb063936e3 /boot           ext3    relatime      
  0       2
/dev/mapper/storage01-swap_crypt none            swap    sw              0      
 0
/dev/mapper/storage01-home_crypt /home  ext3    defaults,errors=remount-ro      
00
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto,exec,utf8 0       0

ProblemType: Bug
Architecture: amd64
Date: Sun May 16 17:00:02 2010
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: cryptsetup 2:1.0.6+20090405.svn49-1ubuntu7.2
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-21.59-generic
SourcePackage: cryptsetup
Uname: Linux 2.6.31-21-generic x86_64
XsessionErrors:
 (gnome-settings-daemon:2957): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
 (gnome-settings-daemon:2957): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
 (polkit-gnome-authentication-agent-1:3000): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2981): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed

** Affects: cryptsetup (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug

-- 
passphrase needs to be entered 3 times with luks encrypted /home
https://bugs.launchpad.net/bugs/581351
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

Reply via email to