[Bug 1813126] Re: [19.04] GRUB_ENABLE_CRYPTODISK=y ignored

[Mathieu Trudel-Lapierre]

If you manage to boot off a USB key or something else and discover the
drives, can you then run grub-probe on the device to check if grub
correctly identifies the disk as a crypto disk?

Running the following command:

sudo grub-probe --device=/dev/mapper/<your crypto device>
--target=abstraction

Should get you output a bit like the following:
cryptodisk
luks
gcry_rijndael
gcry_rijndael
gcry_sha256

If not, then the device is not getting recognized properly.

At a glance, my first guess would be that the format changes in LUKS
that happened in 19.04 are causing an issue, but I'm not sure. I would
not have expected this to be a problem on upgrade.

Please report with the output for the command above if possible, so we
can dig in more into what is happening in grub's probing.

** Changed in: grub2 (Ubuntu)
       Status: Confirmed => Incomplete

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

Title:
  [19.04] GRUB_ENABLE_CRYPTODISK=y ignored

Status in grub2 package in Ubuntu:
  Incomplete

Bug description:
  On my freshly-installed and up-to-date 18.10 with full-disk encryption, I decided to upgrade to 19.04 (dev) using _update-manager -d_.
  Everything seemed fine, until I rebooted and the Grub configuration apparently had been overwritten, and it does not offer to enter the master password, so cannot find the root VG.

  This is all happening on my Lenovo T480 PC, with only Ubuntu (no dual-
  boot).

  I tried boot-repair, applying any suggestion it threw at me, but it
  could not fix the issue.

  I did try to add GRUB_ENABLE_CRYPTODISK=y in /etc/default/grub and
  successfully run update-grub in a chroot, but this did not fix the
  issue.

  Feel free to ask for more details, but diagnostic is limited, as the
  system is not booting, from the very early stages.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1813126/+subscriptions