[root tip] [How To] Use systemd to mount ANY device

Contributions Tutorials
9

Even sshfs ? I am really looking forward to test this.

10

yup - also sshfs

3 Likes
11

wow this is great. :slightly_smiling_face:

12

Any idea if automount works under “–user” as well? Or it’s strictly privilege thing.

I’ve read something on fedora wiki that it might be set up under root which is sad as I can use Fuse to mount things without needing to modify the system.

13

I remember trying - but could not get it to work - probably my own fault - but not investigated further as my use is satisfied by the system mount.

15

You might add that you can generate the correct unit name using systemd-escape(1):

To generate the mount unit for a path:

$ systemd-escape -p --suffix=mount “/tmp/waldi/foobar/”
tmp-waldi-foobar.mount

16

Already mentioned

17

Ahh i didn’t notice, because it was hidden by this:

Maybe put the mentioning of it under the portion i quoted :arrow_heading_up: in the open :wink:

18

How about, once a device is set up (using gnome-disks or fstab) we simply

  1. copy the file from /run/systemd/generator to /etc/systemd/system/
  2. Hash # it from fstab, save/exit fstab
  3. systemd to enable?

I like easy shortcuts. Obviously the automatically generated file isn’t quite up to scratch… tidying up and editing now.

Initially, systemd didn’t like my file and politely declined. However, after a tidy up it seems to be fine - after a reboot, then deleting the hashed lines from fstab it’s automagic.

Thanks for the guide.

However, I did keep the /mnt/T3 and /mnt/T4 paths (as there’d be a few issues raised by changing the path) and I’m curious if there’s really any reason or benefit to create a new folder (/sata for example) to mount my whirly disks?

19

Well - it is not a problem - as long as you know what you are doing - and you appear to do so.

My recommendation on folder structure is what it is - a recommendation from a long time sysadmin - with autistic treats :slight_smile:.

You know the saying - only a genius can make reason out of chaos - just look at my desk - what a mess.

1 Like
20

Lolz but it’s a nice guide - no problems after setting up my systemd mounts, thanks for that :wink:

1 Like
21

2 posts were split to a new topic: Systemd mount unit error

22

6 posts were split to a new topic: Troubleshooting mount unit naming

23

A post was split to a new topic: Where do I start - it all seems difficult to learn

25
26

6 posts were split to a new topic: Mount unit failure after moving to ssd

27

thank you SO MUCH for this. its working fine up to now and it’s not as scary as messing with the fstab file

3 Likes
28

2 posts were split to a new topic: Issue with NTFS

30

The downside of this seems to be that drives don’t get trimmed anymore by the fstrim.service. At least it seems like it when checking with journalctl -u fstrim, since fstrim seems to relate to the fstab file. Am i correct or or is there a workaround?

31

Try

sudo systemctl enable fstrim.timer