Public bug reported:
Hello.
I have two machines with crypted /home (one machine, this is directly on
a partition) and the other with crypted /home (on md) and / (using
alternate install method in 8.04 or 8.10). I have since upgraded these
to 9.10 and 10.04 respectively, and the 10.04 machines was running 9.10
at one point. Both of them worked perfectly in 9.04 in respect to the
passphrase was asked correctly and the boot procedure worked properly.
On all these machines, the entering of passphrase at boot works very
badly. Booting without "quiet" and "splash" yields the possibility to
enter it blindly in the boot process, because the request for passphrase
doesn't seem to be in the right place in the bootup process (at least
for crypted /home). With the machine with just crypted /home, I have to
type it multiple times (blindly) and after a few attempts it works.
Sometimes I have to drop to shell to do it manually and then resuming
the boot process.
With the 10.04 machine I also had the problem that when running with
splash and quiet, if the md the crypted volume resided on didn't come up
correctly, this wasn't even detected at all and the boot process would
just wait endlessly without asking to drop to rescue mode.
My crypted volumes are properly entered in /etc/crypttab:
sdb1_crypt /dev/disk/by-uuid/b23e9d57-2ecf-4411-bcbd-23ca39e924e5 none luks
md0_crypt /dev/md0 none luks
My guess is that crypted volumes (either directly on partitions or on
md) isn't part of the verification process for releases? I can supply
more information if needed, but I think it'll be pretty easy to
reproduce, just create a partition on the system, "cryptsetup
luksFormat" it, enter it in /etc/crypttab, start it manually, create an
fs on the /dev/mapper/<volume> , and then put this in /etc/fstab. Then
start to induce problems in the boot process and see what happens.
I can provide more information as needed, I can create a video as well
if needed.
** Affects: ubuntu
Importance: Undecided
Status: New
--
Passphrase request at bootup doesn't work properly
https://bugs.launchpad.net/bugs/516524
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
