On-Demand NFS and Samba Connections in Linux with Systemd Automount

4 minute read

If you have a NAS, you probably want to be able to connect to it automatically each time you log into your Linux machine. Adding an entry to your fstab is great for desktops with persistent ethernet connections, but you quickly run into trouble using this method on a laptop that’s frequently jumping on and off the network. Your distribution’s file manager may have a way to do this, but wouldn’t it be nice to have a consistent method accross all modern distributions? Systemd to the rescue!

Instead of trying to mount the network shares at login or boot, we’re going to mount them on-demand by combining Systemd mount and automount units. With this method, the shares won’t appear until you navigate to the designated mount points in the terminal or file manager.

NOTE: These instructions were written for Ubuntu 20.04, but the principles should apply to nearly all modern distributions. Adjust for your distro’s package manager and install locations.

Systemd Unit Files

If you’re not familiar with Systemd unit files and how they work, I would highly recommend reading the Freedesktop.org article on the subject. Unit files are effectively services that can be run on-demand or triggered by events or specific times. For our purposes, we’re going to use both mount and automount unit files.

Create a mount point

You’ll need to create dedicated folders on your machine where the shares will be mounted.

$ sudo mkdir -p /mnt/smb/sambashare
$ sudo mkdir -p /mnt/nfs/nfsshare

Create a credentials file

If your Samba server uses authentication, you’ll need to create a file with your login details that Systemd can use to connect. These should be saved in a safe location with restricted permissions.

$ sudo nano /etc/samba/smbcreds
$ sudo chmod 600 /etc/samba/smbcreds

Install the client packages


$ sudo apt install samba cifs-utils


$ sudo apt install nfs-common

Create the systemd unit files

To make this work, we need (2) unit files for each connection: the mount unit and the automount unit. These use a specific naming convention that follows the path of the mount point. For example, if our share is at /mnt/smb/sambashare the mount file should be named mnt-smb-sambashare.mount. The same goes for the automount file. If you don’t name the units this way they will not function.

The below instructions assume your samba share is located at //example.server/sambafiles.

$ sudo nano /etc/systemd/system/mnt-smb-sambashare.mount
Description=samba mount for sambafiles



A few notes on the above file:

  • vers=2.1 - adjust this based on the version of samba running on your server
  • uid=1000 - adjust this based on your local user ID to avoid permissions problems. This is usually 1000 on a desktop system.

Next we need to create the automount file in the same location.

EDIT 2021-08-26 Reader flansuse pointed out that including Requires=network-online.target in the automount file did not conform with systemd guidelines. I confirmed that the mounts work perfectly well without that line, so it’s been removed.

$ sudo nano /etc/systemd/system/mnt-smb-sambashare.automount
Description=samba automount for yourfiles




The below instructions assume your NFS share is located at example.server:/srv/nfsfiles.

EDIT 2021-08-26 Reader Denis suggested adding the TimeoutSec parameter to the below file to prevent lock-ups when the share isn’t present on your local network. Thank you Denis for the contribution!

$ sudo nano /etc/systemd/system/mnt-nfs-nfsshare.mount
Description = nfs mount for nfsfiles



Same as before, we need to create the automount file in the same location.

$ sudo nano /etc/systemd/system/mnt-nfs-nfsshare.automount
Description=nfs automount for nfsfiles



NFS mounts by nature are a bit more straightforward than samba. In an all-Linux environment they will lead to fewer headaches and I recommend them highly.

Put them to work!

At this point your unit files are ready to go but systemd doesn’t know about them. Run the following commands to test your mount:

$ sudo systemctl daemon-reload
$ sudo systemctl start mnt-nfs-nfsshare.mount
$ sudo systemctl start mnt-smb-smbshare.mount

If all went well, you should see your file shares at their designated mount points. To verify, check the status of your service and look for any errors.

$ sudo systemctl status mnt-nfs-nfsshare.mount
● mnt-smb-sambashare.mount - samba mount for sambafiles
   Loaded: loaded (/etc/systemd/system/mnt-smb-sambashare.mount; static; vendor preset: enabled)
   Active: active (mounted) since Wed 2020-10-07 18:05:34 EDT; 1min 1s ago
    Where: /mnt/smb/sambashare
     What: //example.server/sambafiles
  Process: 13005 ExecMount=/bin/mount //example.server/sambashare /mnt/smb/sambashare -t cifs -o vers=2.1,credentials=/etc/samba/smbcreds,iocharset=utf8,rw,x-systemd.automount,uid=1000 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/mnt-smb-sambashare.mount

Oct 07 18:05:34 raylyon-ThinkPad-T450s systemd[1]: Mounting samba mount for sambafiles...
Oct 07 18:05:34 raylyon-ThinkPad-T450s systemd[1]: Mounted samba mount for sambafiles.

Next, enable your automount files to start at boot. This will allow your shares to mount on-demand.

$ sudo systemctl enable mnt-nfs-nfsshare.automount
$ sudo systemctl enable mnt-smb-smbshare.automount

That’s it! To test, reboot your system, open the mountpoint in terminal or the file manager, and your share will mount before your eyes. If you have any questions or critiques on the above instructions, please shoot me an email or open a Github issue.

Thanks for reading and happy hacking!

Leave a comment