On Wed, 08 May 2024 13:48:16 +0100 Luca Boccassi <bl...@debian.org> wrote: > On Wed, 8 May 2024 12:00:34 +0200 Roderich Schupp > <roderich.sch...@gmail.com> wrote: > > I just saw that the missing libkmod (dlopen'ed by udevadm) is already taken > > care of by /usr/share/initramfs-tools/hooks/udev. > > Again, what was the issue exactly? kmod is already taken care of, that > leaves gcrypt or lz4 which are only used for the journal, why would the > abscence of those cause issues for cryptsetup? What was the actual > error and what actually fixed it, precisely?
Sorry for the late answer, but I didn't receive your comments on this bug (as the reporter, shouldn't I be subscribed to it automatically?). Anyway, the culprit is definitely the missing libkmod. I was looking at /usr/share/initramfs-tools/hooks/udev and thought that it would have added it to the initrd, but in systemd/256~rc1-1~exp2 that did work only if update-initramfs is called while standing in /, e.g. when installing a kernel, but **not** when invoking update-initramfs "by hand" in some random directory. This is fixed in 256-rc2 and decryption of my root device works as expected (even though the initrd is lacking libgcrypt and libgpg-error). Cheers, Roderich
