Typing the password very fast causes boot failures

Bug #499488 reported by Reinhard Tartler
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)
New
Undecided
Unassigned

Bug Description

Typing the password very fast causes boot failures.

steps to reproduce (e.g., in kvm):

 - install lucid from current daily alternate installer
 - used guided partitioning with root on crypted LVM
 - choose an easy and fast to type password, like 'ubuntu'
 - boot system
 - type the password very fast

Result:
 - after entering correct password fast, the kernel panics with a message similar to this:

cryptsetup: lvm device name (/dev/disk/by-uuid/2010ede2-fff3-4f15-bc79-1d397a414ac6) does not begin with /dev/mapper/
Unlocking the disk /dev/disk/by-uuid/2010ede2-fff3-4f15-bc79-1d397a414ac6 (vda1_crypt)
Enter passphrase:
Unlocking the disk /dev/disk/by-uuid/2010ede2-fff3-4f15-bc79-1d397a414ac6 (vda1_crypt)
Enter passphrase:
Key slot 0 unlocked.
File descriptor 3 left open
  2 logical volume(s) in volume group "ubuntu" now active
cryptsetup: vda1_crypt setup successfully
mount: mounting /dev on /root/dev failed: Input/output error
mount: mounting /sys on /root/sys failed: Input/output error
mount: mounting /proc on /root/proc failed: Input/output error
Target filesystem doesn't have /sbin/init.
/init: line 260: can't open /root/dev/console: Input/output error
[ 16.349463] Kernel panic - not syncing: Attempted to kill init!

Expected Result:
 - normal system startup.

Used versions:
 - Daily from 20091222
 - Alternate installer
 - Architecture: i386

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Without further information, this is likely to be a problem with cryptsetup's plymouth integration

affects: plymouth (Ubuntu) → cryptsetup (Ubuntu)
Revision history for this message
Steve Langasek (vorlon) wrote :

What is the message displayed on the screen when the kernel panics?

Why do you believe this indicates a failure to mount the root filesystem?

Does booting without 'splash' set still work at this point?

Changed in cryptsetup (Ubuntu):
status: New → Incomplete
Revision history for this message
Reinhard Tartler (siretart) wrote :

Hm, I feel a bit stupid now; I retried it and I don't manage to produce the kernel oops anymore. Instead the system boots fine, but it seems that additional ENTER presses help the system to go further. It is a bit poking in the dark since the screen remains dark at this point.

I believe that the root filesystem wasn't mounted because I've seen error messages that indicated this. If I see them again I'll do a screenshot and attach them to this bug. For now, I'm marking this bug as invalid until I have further information.

Changed in cryptsetup (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Reinhard Tartler (siretart) wrote : Re: [Bug 499488] Re: install plymouth breaks "root on crypted LVM" systems

Steve Langasek <email address hidden> writes:

> What is the message displayed on the screen when the kernel panics?
>
> Why do you believe this indicates a failure to mount the root
> filesystem?

In case this problem occurs, I get these messages:

cryptsetup: lvm device name (/dev/disk/by-uuid/2010ede2-fff3-4f15-bc79-1d397a414ac6) does not begin with /dev/mapper/
Unlocking the disk /dev/disk/by-uuid/2010ede2-fff3-4f15-bc79-1d397a414ac6 (vda1_crypt)
Enter passphrase:
Unlocking the disk /dev/disk/by-uuid/2010ede2-fff3-4f15-bc79-1d397a414ac6 (vda1_crypt)
Enter passphrase:
Key slot 0 unlocked.
File descriptor 3 left open
  2 logical volume(s) in volume group "ubuntu" now active
cryptsetup: vda1_crypt setup successfully
mount: mounting /dev on /root/dev failed: Input/output error
mount: mounting /sys on /root/sys failed: Input/output error
mount: mounting /proc on /root/proc failed: Input/output error
Target filesystem doesn't have /sbin/init.
/init: line 260: can't open /root/dev/console: Input/output error
[ 16.349463] Kernel panic - not syncing: Attempted to kill init!

(the output was captured by configuring a serial console and rebooting
the system several times)

Other boot attempts also produce this failure variant:

cryptsetup: lvm device name (/dev/disk/by-uuid/2010ede2-fff3-4f15-bc79-1d397a414ac6) does not begin with /dev/mapper/
Unlocking the disk /dev/disk/by-uuid/2010ede2-fff3-4f15-bc79-1d397a414ac6 (vda1_crypt)
Enter passphrase:
Key slot 0 unlocked.
File descriptor 3 left open
  Volume group "ubuntu" not found
mount: mounting /dev on /root/dev failed: Input/output error
mount: mounting /sys on /root/sys failed: Input/output error
mount: mounting /proc on /root/proc failed: Input/output error
Target filesystem doesn't have /sbin/init.
/init: line 260: can't open /root/dev/console: Input/output error
[ 12.401429] Kernel panic - not syncing: Attempted to kill init!

During my tests I noticed that the problem only occurs if the password
is typed "fast". If I wait half a minute at the password prompt, the
system boots fine. If I type the (admitly simple) password very fast,
one of the above boot failures occur. This confirms Scotts guess that
this bug has nothing to do plymouth as it occurs without plymouth as
well.

In case somebody is interested, I can share the disk image so that you
can try this out yourself in kvm. Unfortunatley, it has 16.1 GB in size
currently.

--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4

description: updated
summary: - install plymouth breaks "root on crypted LVM" systems
+ Typing the password very fast causes boot failures
Changed in cryptsetup (Ubuntu):
status: Invalid → New
Revision history for this message
Reinhard Tartler (siretart) wrote :

Interestingly, my latest boot attempt showed this output:

cryptsetup: lvm device name (/dev/disk/by-uuid/2010ede2-fff3-4f15-bc79-1d397a414ac6) does not begin with /dev/mapper/
Unlocking the disk /dev/disk/by-uuid/2010ede2-fff3-4f15-bc79-1d397a414ac6 (vda1_crypt)
Enter passphrase:
Key slot 0 unlocked.
File descriptor 3 left open
  Volume group "ubuntu" not found
udevd-work[185]: inotify_add_watch(6, /dev/mapper/vda1_crypt, 10) failed: No such file or directory

udevd-work[322]: open /dev/null failed: No such file or directory

mountall: Could not connect to Plymouth
fsck from util-linux-ng 2.16
fsck from util-linux-ng 2.16
udevd[352]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /lib/udev/rules.d/56-hpmud_support.rules:10

/dev/mapper/ubuntu-root: clean, 135622/923888 files, 694797/3694592 blocks
/dev/vda5: clean, 166/124496 files, 31658/248976 blocks
init: ureadahead-other main process (370) terminated with status 4
 * vda1_crypt (running)... [ OK ] * vda1_crypt (running)...

Note the error message about the failure to find the Volume group
"ubuntu" while still being able to boot successfully. Maybe the lvm
initramfs scripts needs to use watershed somewhere?

--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.