failed to boot into encrypted disk after update

elizth · 2026-07-29 20:04:55

https://x02.me/i/EKWWE.jpg https://x02.me/i/TUJH.jpg

I got this error after updating yesterday. I have not encountered this error before, so I'm not sure what happened exactly. I'm using dracut-ukify to automatically generate the unified kernel image after update. I've tried using different kernels to no avail. Is this error due to changes in kernel config between the updates?

Last edited by elizth (2026-07-29 21:50:06)

seth · 2026-07-29 20:45:16

Please replace the oversized images w/ links.

I've tried using different kernels

Which ones?

Are the serpent modules did not make it into the UKI?
https://wiki.archlinux.org/title/Dracut#dracut_modules

after updating yesterday

What was in that update? Next to the kernel, maybe systemd?

elizth · 2026-08-01 06:37:08

It seems like cryptsetup, systemd, linux-lts, linux-hardened, linux-zen, linux are all upgraded. I tried to use all four kernels.

seth · 2026-08-01 06:53:05

If it's not the kernel, try to downgrade systemd first, then cryptsetup to see where this is coming from?

sharow · 2026-08-01 07:16:21

"[cryptsetup] unable to luksOpen: Error allocating crypto tfm" : https://gitlab.com/cryptsetup/cryptsetu … _items/743

also, be sure to include the dependant modules.

diff \
  <(cat <(ldd /usr/bin/cryptsetup | awk '{print $1}') \
    <(lsinitcpio /boot/initramfs-linux.img | sed "s/usr\/lib\///"|sort -u) | sort | uniq -c | awk '{if($1!="1")print $2}') \
  <(ldd /usr/bin/cryptsetup | grep -v linux | awk '{print $1}' | sort)

elizth · 2026-08-01 07:32:55

is it a good idea to rollback to an older snapshot of root partition and regenerate the uki?

seth · 2026-08-01 07:54:24

In order to restore a booting system: likely. But it won't tell us what went wrong or what broke it.
You can also iterate through the updates, https://wiki.archlinux.org/title/Arch_L … cific_date

As asked before and stressed by sharowm the error would indicate that the serpent modules are/were not added to the UKI, but w/o changes to dracut/configuration and affecting all kernels this seems a bit odd, so this is probably caused by the cryptsetup or systemd updates

elizth · 2026-08-01 09:03:04

seems like downgrading systemd, systemd-ukify, etc. & cryptsetup and regenerating the uki did not work. sorry it's getting late so i'll try to solve this tomorrow

seth · 2026-08-01 13:45:44

downgrading … systemd-ukify

I'm using dracut-ukify

How exactly are you generating the UKI?
Also https://man.archlinux.org/man/ukify.1#inspect

Arch Linux

#1 2026-07-29 20:04:55

failed to boot into encrypted disk after update

#2 2026-07-29 20:45:16

Re: failed to boot into encrypted disk after update

#3 2026-08-01 06:37:08

Re: failed to boot into encrypted disk after update

#4 2026-08-01 06:53:05

Re: failed to boot into encrypted disk after update

#5 2026-08-01 07:16:21

Re: failed to boot into encrypted disk after update

#6 2026-08-01 07:32:55

Re: failed to boot into encrypted disk after update

#7 2026-08-01 07:54:24

Re: failed to boot into encrypted disk after update

#8 2026-08-01 09:03:04

Re: failed to boot into encrypted disk after update

#9 2026-08-01 13:45:44

Re: failed to boot into encrypted disk after update

Board footer