You are not logged in.

#1 2017-01-30 20:07:47

Azured
Member
Registered: 2014-02-08
Posts: 9

systemd insists on generating service files for non-existant drives

Been troubleshooting this for a little while after switching to a systemd boot on an encrypted arch installation with Gnome 3.

Every time I boot I'm greeted with multiple attempts to mount my encrypted root.

 [azured@archdesktop ~]$ journalctl -b -r
<snip>
Jan 30 19:23:33 archdesktop systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-446ce30\x2d09b0\x2d48b7\x2d9f60\x2df3a4d9ae1c83.device.
Jan 30 19:23:33 archdesktop systemd[1]: dev-disk-by\x2duuid-446ce30\x2d09b0\x2d48b7\x2d9f60\x2df3a4d9ae1c83.device: Job dev-disk-by\x2duuid-446ce30\x2d09b0\x2d48b7\x2d9f60\x2df3a4d9ae1c83.device/start timed out.
<snip>
Jan 30 19:22:01 archdesktop systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-446ce30\x2d09b0\x2d48b7\x2d9f60\x2df3a4d9ae1c83.device.
Jan 30 19:22:01 archdesktop systemd[1]: dev-disk-by\x2duuid-446ce30\x2d09b0\x2d48b7\x2d9f60\x2df3a4d9ae1c83.device: Job dev-disk-by\x2duuid-446ce30\x2d09b0\x2d48b7\x2d9f60\x2df3a4d9ae1c83.device/start timed out.
<snip>
Jan 30 19:19:24 localhost systemd[1]: Found device /dev/disk/by-uuid/b06ffc2a-271a-4fb7-9d42-fa8ccb407730.
Jan 30 19:19:24 localhost systemd[1]: Found device /dev/mapper/luks-4469ce30-09b0-48b7-9f60-f3a4d9ae1c83.

In total it makes 3 attempts to mount the encrypted root, the first succeeds (after I type my password), and the 2 others eventually timeout, after which the boot continues and I can log into GDM (albeit with ~3 min delay). I assume the 2 others timeout because they cannot mount an already mounted root..

These are supposed to be mounted by generators, generated from /etc/crypttab & /etc/fstab, however, I don't have any entries for these in crypttab / fstab!

[azured@archdesktop ~]$ cat /etc/fstab
# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>

# /dev/sda1
UUID=6ACB-AD9A      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro	0 2

LABEL=Data /home/azured/Data ntfs-3g defaults,x-gvfs-show 0 0
[azured@archdesktop ~]$ sudo cat /etc/crypttab
cat: /etc/crypttab: No such file or directory

According to the man files, these files are re-generated with systemctl daemon-reload

[azured@archdesktop ~]$ man systemd.generator

       After editing /etc/fstab, the user should invoke systemctl
       daemon-reload. This will re-run all generators and cause systemd to
       reload units from disk. To actually mount new directories added to
       fstab, systemctl start /path/to/mountpoint or systemctl start
       local-fs.target may be used.

So I go to invoke "systemctl daemon-reload" and a reboot continues to attempt to triple mount the encrypted root.

It's probably something simple, but at this point I'm staring myself blind at it.. help appreciated!

Offline

Board footer

Powered by FluxBB