TL;DR - NAS mounts manually but doesn't mount at boot when added to /etc/fstab.
Hi folks,
My conundrum is that I have a Synology NAS on my network which I am able to mount manually but when added to /etc/fstab, the NAS is not mounted at boot using the NFS protocol.
The NAS (hostname 'virgo') is mounted on my Fedora machine (hostname 'orion') at /mnt/virgo and the NAS folder /volume/file_sync is mounted to this folder.
The command I used to manually mount is:
Quote:
|
sudo mount -t nfs 192.168.0.72:/volume1/file_sync /mnt/virgo
|
However when adapted for /etc/fstab, it is not mounted at startup, the contents of /etc/fstab are:
Quote:
#
# /etc/fstab
# Created by anaconda on Sun Jan 24 08:03:10 2021
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
UUID=39f5fc59-057c-4e47-9483-930d78b6601a / ext4 defaults 1 1
UUID=F0D6-AD83 /boot/efi vfat umask=0077,shortname=winnt 0 2
UUID=bf272d14-6dc9-45f8-861e-760f45549668 /home ext4 defaults 1 2
UUID=3244c1e5-230d-4595-9416-570ee6f14ded none swap defaults 0 0
# NAS drive
192.168.0.72:/volume1/file_sync /mnt/virgo nfs rw,sync,hard,intr 0 0
|
When I checked the log (journalctl -b 0 | grep mount) this is the result which seems to indicate it did try to mount the NAS but failed:
Quote:
Feb 13 20:59:25 orion systemd[1]: Condition check resulted in dracut pre-mount hook being skipped.
Feb 13 20:59:25 orion kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
Feb 13 20:59:25 orion systemd[1]: Condition check resulted in dracut mount hook being skipped.
Feb 13 20:59:26 orion kernel: SELinux: Permission watch_mount in class file not defined in policy.
Feb 13 20:59:26 orion kernel: SELinux: Permission watch_mount in class dir not defined in policy.
Feb 13 20:59:26 orion kernel: SELinux: Permission watch_mount in class lnk_file not defined in policy.
Feb 13 20:59:26 orion kernel: SELinux: Permission watch_mount in class chr_file not defined in policy.
Feb 13 20:59:26 orion kernel: SELinux: Permission watch_mount in class blk_file not defined in policy.
Feb 13 20:59:26 orion kernel: SELinux: Permission watch_mount in class sock_file not defined in policy.
Feb 13 20:59:26 orion kernel: SELinux: Permission watch_mount in class fifo_file not defined in policy.
Feb 13 20:59:26 orion systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
Feb 13 20:59:26 orion systemd[1]: Starting Remount Root and Kernel File Systems...
Feb 13 20:59:26 orion systemd[1]: sysroot.mount: Succeeded.
Feb 13 20:59:26 orion kernel: EXT4-fs (sda2): re-mounted. Opts: (null)
Feb 13 20:59:26 orion systemd[1]: Finished Remount Root and Kernel File Systems.
Feb 13 20:59:26 orion systemd[1]: Condition check resulted in OSTree Remount OS/ Bind Mounts being skipped.
Feb 13 20:59:26 orion audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 13 20:59:27 orion systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway.
Feb 13 20:59:27 orion kernel: EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
Feb 13 20:59:35 orion mount[878]: mount.nfs: Network is unreachable
Feb 13 20:59:35 orion systemd[1]: mnt-virgo.mount: Mount process exited, code=exited, status=32/n/a
Feb 13 20:59:35 orion systemd[1]: mnt-virgo.mount: Failed with result 'exit-code'.
Feb 13 20:59:35 orion systemd[1]: Failed to mount /mnt/virgo.
Feb 13 21:00:06 orion systemd[1]: run-user-988.mount: Succeeded.
Feb 13 21:00:06 orion systemd[980]: run-user-988.mount: Succeeded.
|
Does anyone have any pointers or suggestions please? I am still fairly new to NAS's but not at all new to Linux.
