search

qzed / luks-keyfile-dracut

Obsolete. Use the `rd.luks.key` option instead.
GNU General Public License v3.0
5 stars 0 forks source link

Not working with systemd v255 #1

Open dsiggi opened 8 months ago

dsiggi commented 8 months ago

Hi, I'm using your dracut module a long time now. Last week I updated my system (gentoo linux). The was a update from systemc v254 to v255. With v255 the module ist not working anymore.

The unit is created under /run/systemd/system but the directory to mount the usb drive is not created. So the luks-keyfile-generator.sh is not run completely or so. The Unit is also not started during boot.

When I do a downgrade to v254 everything is working again. I looked at the changelog from systemd but can't see something what should be the problem. Maybe you have an idea?

qzed commented 7 months ago

Unfortunately I can't reproduce this right now as the system I have this running on still is on v254 (Fedora 39).

However, this manpage indicates that the output directory should be /run/systemd/generator and not /run/systemd/system (and that those paths are provided via arguments when the generator is run). Can you try and replace this with either 

NORMAL_DIR="/run/systemd/generator"

or (preferably)

NORMAL_DIR="${1}"

and report back whether that works?

qzed commented 7 months ago

but the directory to mount the usb drive is not created

By USB drive you mean the drive holding the key file? That drive should be mounted in the initramfs only, so you should not be able to see it any more once the system has booted into the actual root file system.

qzed commented 3 months ago

So turns out this package is completely obsolete. Anything this package does can also be done with the rd.luks.key option. See https://wiki.archlinux.org/title/Dm-crypt/System_configuration#rd.luks.key. For some reason, I also had to specify the keyfile/drive in /etc/crypttab, but with that everything works for me.