How to stop systemd automounting a removable device [SOLVED]

Hi!
I have a password protected thumbdrive and systemd asks for a password for it in every boot. If I don't have it plugged in at boot time, systemd waits for one and a half minute before completing boot.
Investigating, I found a service called systemd-cryptsetup@luks\\x2dcf6c1ade\\x2d443a\\x2d4d90\\x2db8d0\\x2d373238f75eed.service that I can't disable.
Trying
Is there any way to disable that?
moved to appropriate forum. ~Germ
I have a password protected thumbdrive and systemd asks for a password for it in every boot. If I don't have it plugged in at boot time, systemd waits for one and a half minute before completing boot.
Investigating, I found a service called systemd-cryptsetup@luks\\x2dcf6c1ade\\x2d443a\\x2d4d90\\x2db8d0\\x2d373238f75eed.service that I can't disable.
Trying
- Code: Select all
systemctl disable systemd-cryptsetup@luks\\x2dcf6c1ade\\x2d443a\\x2d4d90\\x2db8d0\\x2d373238f75eed.service
- Code: Select all
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled or disabled using systemctl.
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
Is there any way to disable that?
moved to appropriate forum. ~Germ