On 01/09/2015 02:15 PM, Mark Hounschell wrote:
I am running 13.2 (x86-64). I have several (removal) disks in the box. I manually unmount one and install another in its place to mount and use temporarily. When done I will put the original disk back in and remount it manually. I get this from systemd complaining about the old disk no longer being there.
systemd[1]: Timed out waiting for device ST3160815AS. systemd[1]: Dependency failed for "blablabla".
Over and over and over for every partition on it that is defined in the fstab file.
What is this? My fstab has "ext4 defaults" for all the partitions on the disk. I think I read a thread here about a similar issue some time back but all I don't think I ever saw a real resolution. It had never affected me at the time. Not sure why, but it sure is now. What is the proper "systemd" way of doing this sort of thing now? Please don't tell me that this is no longer allowed.
Thanks Mark
Systenmd also is able to replace fstab - or parts of it. On systemd linux systems nowadays you sometimes only see real devices in /etc/fstab and a unit generator "systemd-fstab-generator" generates systemd units from the fstab. To see the filesystems systemd controls, see systemctl -a -t mount Another feature of systemd are dependencies. So if systemd wants to mount a filesystem, it can wait for a device to appear before. Use systemd list-dependencies to inspect this. I think you have to cleanup something, that came from installation time or use systemctl disable blabla.mount instead of simply umount. Just a guess, i did not try ...