Ubuntu
cryptsetup package

  1. Bug #532898
  2. Comment #21

Comment 21 for bug 532898

Revision history for this message
TJ (tj) wrote :

I'm experiencing this with ubuntu-desktop i386 with nvidia-current 195.x.y drivers installed.

In this case I cannot find any combination of kernel command-line options (inc. "nomodeset" and "nosplash") or interrupts to get past the issue, whether multi-user or single (recovery), and am currently experiencing an unusable system so I cannot at this moment report the exact package versions installed.

I had managed to boot it via 'recovery' and entering the shell then manually starting GDM about 24-hours ago. I had avoided restarting until around 23:00 UTC because of the difficulty in getting things started. At that time I'd just ensured all packages were upgraded from the GB mirror.

The configuration is:

sda1, sda2 legacy Windows partitions
sda3 ext3 /boot
sda4 LVM VG=Ubuntu

Within VG "Ubuntu" are approximately 15 Logical Volumes (LV). Some are encrypted, others are not.

The encrypted VGs are secured only using a LUKS key-file (no passwords). The key-file is on a USB key. I have a custom script (/usr/local/sbin/crypt-usb-key.sh) that has worked fine since Hardy and still works with Lucid. /etc/crypttab specifies the key-file and custom script.

Ubuntu/Lucid_enc is LUKS containing the root ext4.
Ubuntu/Lucid_var_enc is LUKS containing the /var ext4.
Ubuntu/swap is swapfs
Ubuntu/usr_local is /usr/local ext3.
Ubuntu/home is LUKS containing the /home ext4.

Obviously Ubuntu/Lucid_enc has to be unlocked from initrd using my custom script and it is. Here's a snippet of the output (after Escaping the splash screen):

Unlocking encrypted volume using a key-file
Waiting up to 30 seconds for removable devices...
Success loading key-file
Key slot 0 unlocked.

However, /var never gets unlocked.

If splash is enabled I see "Waiting for /var [SM]" but regardless of what key I press nothing appears to happen.
If I press Escape I see that pressing "M" causes:

init: plymouth main process (438) killed by SEGV signal

I also see several fsck reports for several unecrypted LVs. I don't see anything to suggest cryptsetup has tried to unlock any encrypted partitions.

If I switch away from tty7 and return to it before pressing a key the consoles freeze - no reaction to regular keys or tty switching, although SysReq keys are still responsive.

I'm wondering if this is another symptom of tty7 being 'grabbed' by plymouth?