[Bug 1979159] Re: Cannot unlock encrypted root after upgrading to 22.04

[Thomas]

Alternative workaround steps (w/o live cd):

1) Access initramfs environment at boot

2) # ls /dev/mapper

3) If you only see something like "isw_bdihdgjaaf_v1" and "control", but
no "isw_bdihdgjaaf_v1pX" at all, proceed.  Take note of whatever the
name is besides control.

4) # cd /sbin

5) # ./kpartx -a /dev/mapper/isw_bdihdgjaaf_v1  <- put your mapped
device name here

6) # /scripts/local-top/cryptroot

7) # cryptroot-unlock  <- it should properly prompt for your password
now

I have only done this remotely, I am unsure how local would react to
step 6.  After running the cryptroot script, it will boot you if you are
doing this remotely.  SSH back into the system, then do step 7.

-- 
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