Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
systemd-cryptsetup v220 breaks non-LUKS devices with unspecified type #442
On a system running the Debian testing distribution, I recently upgraded the
The device is configured as a plain (non-LUKS) device using a keyfile with the following line in
I tracked the issue down to a change in commit 7376e83528 at line 408 which now causes systemd-cryptsetup to fail rather than retry as plain for devices of unspecified type. Since there is no mention of this change in Bug 66396, I assume the change was inadvertent. If the change was intentional, I would highly suggest documenting it as a breaking change for system administrators in the upgrade notes.
Seeing exactly the same behaviour, I wonder how come only two of us affected (not a common setup?), and google hasn't indexed "crypt_load() failed on device" to point to this issue, so spent whole evening yesterday trying to bring my laptop back up :) (by downgrading systemd for now :/) ArchLinux here