Xubuntu with LUKS FDE hangs upon boot after Hirsute upgrade

Bug #1926972 reported by yitzhaq on 2021-05-03

This bug report will be marked for expiration in 50 days if no further activity occurs. (find out why)

8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)
Undecided
Unassigned

Bug Description

After upgrading to Hirsute, I'm unable to boot my Xubuntu laptop with LUKS FDE. It was working fine on Groovy, and I have made no changes besides upgrading.

The system now hangs on boot. Nothing is displayed (completely black screen, no passphrase prompt, no cursor, nothing), and the keyboard does not respond (not even Caps Lock). This does not appear to be the reported known Xubuntu issue about having to press ESC (once or twice) to see the password prompt; as mentioned, the keyboard does not appear to respond at all. I have also confirmed that this is not #1915579, as the installed lvm2 version includes the fix, and I have manually confirmed that /usr/share/initramfs-tools/hooks/lvm2 is 755.

/etc/crypttab looks fine as far as I can tell, and nothing complained during upgrade. I have tried doing dpkg-reconfigure (and apt-get install --reinstall) against grub-pc, initramfs-tools, cryptsetup and the latest installed kernel, to no avail. No complaints from any of that either.

~ # cat /etc/crypttab
sda4_crypt UUID=<my-uuid-is-listed-here> none luks,discard

All package versions are current as of writing (including hirsute, hirsute-updates, hirsute-security). The volume mounts fine when booting from installation media.

Not sure which package to report this against, as I don't know where the problem is located.

HW in case it matters (though I doubt it) is a Lenovo ThinkPad X220 running latest BIOS (1.46), with Samsung 860 EVO S-ATA. BIOS is configured with "Legacy first", rather than UEFI.

Any help greatly appreciated.

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1926972/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
yitzhaq (yitzhaq) wrote :

Let's try cryptsetup. Perhaps better to have the wrong package than no package at all.

affects: ubuntu → cryptsetup (Ubuntu)
Brian Murray (brian-murray) wrote :

Does the same thing happen if you try to boot the system using an Ubuntu 21.04 installation media e.g. a burned DVD or USB stick?

Changed in cryptsetup (Ubuntu):
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers