Unlocking a LUKS volume with a keyfile on an USB stick

[hamrheadcorvette (hammerhead corvette)]

@smirgl

That differs from my use case. During my test, my first USB stick suddenly died. This prompted me to look for a simple replacement solution. So I would like to avoid any UID based mount points for this specific use case.

That’s unfortunate, but it does happen and can happen with any device.

@smirgl

My udev rule only looks at the label of the stick and mounts it automatically if it has a certain name So I can quickly replace a dying stick. I don’t use any fstab entry so far. It’s all done by systemd.
Maybe my stick is mounted after the LUKS prompt. I was digging through journalctl to find more information, but I wasn’t successful.

That is a more difficult approach IMO. udev > systemd.service > bash script ? I can’t test this for a system unlock, and I have had my own problems unlocking devices and running udev rules and systemd.services for a project I am doing with mixed results in the process. . .

How to setup systemd.service files for auto backup to USB Drive

Hey Everyone I need to set up a sysemd.service for an rsync script I have. I want the service to run once the USB drive is mounted (this is usually on /run/media/$USER/$UUID/). Here is my Service file : [Unit] Description=Backup directories to external drive After=mount.target [Service] User=root Type=oneshot ExecStart=/usr/local/bin/rsync_backup_script.sh [Install] WantedBy=multi-user.target The service file did have a SELinux context of : unconfined_u:object_r:systemd_unit_fi…

---

On the way here : I just thought another method that might work for you…

I have a small collection of USB drives that I bought from Amazon. They are very cheap 32GB drives. I have key files in most of them. So in the //etc/fstab you can use by-name instead of by-uuid.