I noticed this regression after re-installing 9.10 and performing normal
system updates. I was backing out of a full Lucid install to dual 9.10
/ lucid installs.
I can enter the passwords for / and swap correctly within the initrd.
Then fsck is run on /boot (/dev/sda3) and / (lvm).
Next a second round of cryptsetup runs, indicating that the devices that
had been started are running, and starting that it is about to try
starting lin-home_crypt ; which is when it then displays a message:
One or more of the mounts listed in /etc/fstab cannot yet be mounted:
(ESC for recovery shell)
/home: waiting for /dev/mapper/lin-home_crypt
No input displays on the screen, but I am unable to enter the password
to unlock exactly what it needs.
A workaround of appending break=bottom and manually running cryptsetup
luksOpen src destname allows me to unlock the device before this race
condition occurs.
** Changed in: cryptsetup (Ubuntu)
Status: New => Confirmed
--
cryptsetup can't get input at boot.
https://bugs.launchpad.net/bugs/518964
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
