[Bug 1979159] Re: Cannot unlock encrypted root after upgrading to 22.04
Benjamin Drung
1979159 at bugs.launchpad.net
Fri Jul 29 15:15:33 UTC 2022
Ubuntu 18.04 installation with encryption:
$ sudo cryptsetup luksDump /dev/vda5
LUKS header information for /dev/vda5
Version: 1
Cipher name: aes
Cipher mode: xts-plain64
Hash spec: sha256
Payload offset: 4096
MK bits: 512
MK digest: 55 0b b3 df c2 ba 30 0c 1d b1 80 9d 22 38 af 0d 60 6d de 0f
MK salt: 26 a0 b7 c7 7f 94 d4 2e 70 e7 33 32 19 b9 49 8d
90 21 c6 4e 2a 80 31 1c c8 5e ef 8e e8 21 2f ed
MK iterations: 143091
UUID: 9f59f808-c690-482c-8e58-0f5551b2af8f
Key Slot 0: ENABLED
Iterations: 2289466
Salt: 29 f6 c7 43 d5 0b f1 a1 42 71 2b fb 93 a0 6f 48
b6 94 87 c5 ac 39 0e 67 33 02 30 ee 6d 93 2e f0
Key material offset: 8
AF stripes: 4000
Key Slot 1: DISABLED
Key Slot 2: DISABLED
Key Slot 3: DISABLED
Key Slot 4: DISABLED
Key Slot 5: DISABLED
Key Slot 6: DISABLED
Key Slot 7: DISABLED
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/1979159
Title:
Cannot unlock encrypted root after upgrading to 22.04
Status in cryptsetup package in Ubuntu:
Confirmed
Status in cryptsetup source package in Jammy:
Confirmed
Status in cryptsetup source package in Kinetic:
Confirmed
Bug description:
After upgrading to Ubuntu 22.04 with an encrypted root filesystem, the
root drive can no longer be unlocked at the "Please unlock disk
<diskname>" prompt on boot.
The encrypted root disk can be unlocked fine from the liveCD, but not
from the initramfs environment on boot.
The issue is caused by support for various luks encryption protocols
now being missing from the initramfs environment due to changes
introduced in OpenSSL 3.0 and Ubuntu pre-release testing not including
a test-case of upgrading older Ubuntu versions with an encrypted root
to the new version.
The issue can be worked-around by:
1. Booting from the 22.04 liveCD.
2. chrooting into the target system's root.
See https://help.ubuntu.com/community/ManualFullSystemEncryption/Troubleshooting
3. Creating a file /etc/initramfs-tools/hooks/custom-add-openssl-compat.conf containing:
---
. /usr/share/initramfs-tools/hook-functions
copy_exec /usr/lib/x86_64-linux-gnu/ossl-modules/legacy.so /usr/lib/x86_64-linux-gnu/ossl-modules/
---
4. Mark the file as executable: chmod +x /etc/initramfs-tools/hooks/custom-add-openssl-compat.conf
5. Regenerating the initramfs. ie. update-initramfs -k all -u
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1979159/+subscriptions
More information about the foundations-bugs
mailing list