Cryptsetup: how an upgrade "broke" my system (kernel 6.10.6 -> 6.11.3)

I’ve updated my system today and upon reboot I could start my luks encrypted system anymore.

When I entered my password I was welcomed with:

Failed to start Cryptography Setup for luks-xyz
See 'systemctl status "systemd-cryptsetup@luks-xyz..service"' for details.
[DEPEND] Dependency failed for Local Encrypted Volumes.
[...]
Warning /dev/mapper/luks-xyz doesn't exist.

Scary thing to read. Seems like my main partition doesn’t exist anymore.

Hopefully my main partition still exists. The issue was with my password: I’ve configured and always used this system with an azerty keyboard configuration; the update changed the layout to a default dumb-hat qwerty.

That really sucks.

Where do I report that? I don’t know if it’s a kernel issue, a cryptsetup issue, an arch or endeavour one.

Cheers,

1 Like

Yeah, that error just indicates your device failed to unlock, not that the partition is missing. /dev/mapper/* is a device that is created to access the unlocked partition. Since it failed to unlock, it doesn’t exist.

You are the second person to report this today. It may be a dracut issue. I will open an issue upstream.

EDIT: It has already been reported and a fix is in progress:

1 Like

That was fast! Thanks

Conceptually I knew this but I started panicking nontheless.

1 Like