Difference between revisions of "Fstab - Use SystemD automount/fr"
Views
Actions
Namespaces
Variants
Tools
(Created page with "Introduction") |
(No difference)
|
Revision as of 01:35, 5 February 2022
I found a combination of systemd options (on the ArchWiki [1]) that can be used in the /etc/fstab when mounting storage devices --be they internal, external, or network shares.
The magic (to me) that these mount options bring is that if a network share or an external drive that is being called via /etc/fstab is not present, they save your machine from hanging for a minute or two during the boot process.
A device called this way via /etc/fstab is mounted the first time data is attempted to be accessed from it. Only on this first mount is there any (minor) noticeable delay, when compared to having the device mounted the "old" way.A problem that this causes is that if I forget to comment out the NFS share(s) that I'm using from the /etc/fstab file, I have to wait for a minute or two during the boot process whilst the system repetitively tries to make a connection.
I attempted to get AutoFS [2]to work for me. I got close but I just wasn't allowed to see the files on the NFS NAS share.
So then I found the following extremely simple & effective solution. (Wish I had of done this one first, as it would have saved me a couple of hours of a loosing battle!)noauto,x-systemd.automount,x-systemd.device-timeout=10
After I added the above to the following line in my fstab:
192.168.1.15:/media-2 /mnt/NAS-media-2 nfs noauto,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,hard,intr,noatime 0 0
I could boot Manjaro whilst the ReadyNAS' Cat-6 network cable was unplugged, & there was NO noticeable delay. After the system was booted, I plugged the cable in & then called the NFS share /media-2 in Worker & it read the drive & listed the contents.
UUID=<id.number> /home noauto,x-systemd.automount,ext4 defaults 0 1