[Expired for grub2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813126
T
Disregard my post, my issue was unrelated. (I inadvertently must have
removed my crypttab file, sigh.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813126
Title:
[19.04] GRUB_ENABLE_CRYPTODISK=y i
I can confirm similar behavior, but slightly different setup.
I installed 19.04 from scratch, and used the disk encryption with lvm
option during setup.
Everything was working fine until upgrading to the latest kernel,
5.0.0-16-generic.
The previous kernel I had installed, 5.0.0-15-generic, stil
Further investigation revealed that a change to the semantics of
'cryptsetup' tool is responsible for the specific manual build I did.
On 18.04 'cryptsetup luksFormat --type=luks ...' would create a LUKS v1
header. On 19.04 it creates a LUKS v2 header. GRUB only supports LUKS v1
headers currently.
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/
--target=abstraction
Should get you outpu
