Comment 4 for bug 499488

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