Encrypted LVM on UEFI prevents GRUB booting successfully

Bug #1901488 reported by TJ
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
subiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

20.04.1 Encrypted LVM install, sda4 > LUKSv2 > VG > LVs

cryptsetup creates LUKSv2 containers. GRUB can only understand LUKSv1 and therefore cannot access its root device making the installation unbootable.

Making matters worse, installer has not added GRUB_ENABLE_CRYPTODISK=y to /etc/default/grub.d/local.cfg so grub-install hasn't passed the crypto device info to GRUB's core and thus there is no cryptomount command in /EFI/ubuntu/grub.cfg

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.