[Bug 1901488] [NEW] Encrypted LVM on UEFI prevents GRUB booting successfully

[TJ]

*** This bug is a duplicate of bug 1876989 ***
    https://bugs.launchpad.net/bugs/1876989

Public bug reported:

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

** Affects: subiquity (Ubuntu)
     Importance: Undecided
         Status: New

** This bug has been marked a duplicate of bug 1876989
   Encrypted LVM install with no separate /boot results in unbootable system

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to subiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1901488

Title:
  Encrypted LVM on UEFI prevents GRUB booting successfully

Status in subiquity package in Ubuntu:
  New

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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1901488/+subscriptions