Ubuntu
cryptsetup package

  1. Bug #1979159
  2. Comment #23

Comment 23 for bug 1979159

Revision history for this message
asi (gmazyland) wrote : Re: Cannot unlock encrypted root after upgrading to 22.04

LUKS1/LUKS2 never used any algorithm in *default* setting that is now in legacy OpenSSL3 provider (RIPEMD160 or Whirlpool hash is in legacy now).
Also, cryptsetup (since version2.4.0) always tries to load both default and legacy provider for OpenSSL3.

That said, you can try luksFormat with --hash ripemd160 (that is only in legacy) but I doubt this is the problem you are seeing here.

If user had plain device instead of LUKS (that uses RIPEMD160 by default) then you need legacy always.

Also the problem can be in kernel modules (usually missing kernel crypto module in initramfs; note xts need aslo ecb module to work).