Ubuntu nfs manager Pc#

Looks like (to me) that my Ubuntu client PC can't find the network share when it needs to. deb extension so I expect it may be Debian? I expect it runs some propitiatory flavor of Linux. My network storage (NAS) is not an Ubuntu device. Sep 23 21:25:25 david-System-Product-Name systemd: Finished Permit User Sessions. Sep 23 21:25:25 david-System-Product-Name apport: * Starting automatic crash report generation: apport Sep 23 21:25:25 david-System-Product-Name systemd: Started Tool to automatically collect and submit kernel crash signatures. Sep 23 21:25:25 david-System-Product-Name systemd: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 23 21:25:25 david-System-Product-Name systemd: rvice: Found left-over process 1270 (kerneloops) in control group while starting unit. Sep 23 21:25:25 david-System-Product-Name cron: (CRON) INFO (Running jobs) Sep 23 21:25:25 david-System-Product-Name systemd: Starting Permit User Sessions. Sep 23 21:25:25 david-System-Product-Name systemd: Starting Tool to automatically collect and submit kernel crash signatures. Sep 23 21:25:25 david-System-Product-Name cron: (CRON) INFO (pidfile fd = 3) Sep 23 21:25:25 david-System-Product-Name systemd: Started Regular background program processing daemon. Sep 23 21:25:25 david-System-Product-Name systemd: Starting LSB: automatic crash report generation. Sep 23 21:25:25 david-System-Product-Name systemd: remote-fs.target: Job remote-fs.target/start failed with result 'dependency'. Sep 23 21:25:25 david-System-Product-Name systemd: Dependency failed for Remote File Systems. Sep 23 21:25:25 david-System-Product-Name systemd: Failed to mount /mnt/photos. Sep 23 21:25:25 david-System-Product-Name systemd: mnt-photos.mount: Failed with result 'exit-code'. Sep 23 21:25:25 david-System-Product-Name systemd: mnt-photos.mount: Mount process exited, code=exited, status=32/n/a Sep 23 21:25:25 david-System-Product-Name mount: mount.nfs: Network is unreachable The options that were applied by that fstab line: If it doesn't work at your place, I'd suggest checking the system logs and dmesg for problems. Istar:/d/D1 /d/D1 nfs _netdev,proto=tcp,intr,rw,async 0 0 dev/vgubuntu-mate/swap_1 none swap sw 0 0 dev/vgubuntu-mate/home /home ext4 errors=remount-ro 0 1 dev/vgubuntu-mate/root / ext4 errors=remount-ro 0 1 dev/mapper/vgubuntu-mate-home ext4 12G 6.0G 5.2G 54% /home Let me try _netdev in the fstab from a seldom used client machine (so it can be rebooted).įilesystem Type Size Used Avail Use% Mounted on Anyway, the DNS lookup for istar has to work before the NFS mount can be attempted. The client machine /etc/hosts only has 2 lines (I don't use IPv6). Ran, sudo systemctl daemon-reload to get the fstab reloaded by systemd, and did a sudo mount -aĮverything expected is in /d/D1. Istar:/d/D1 /d/D1 nfs proto=tcp,intr,rw,async 0 0 If I used the fstab, the line would be this: The options that I use for NFS mounts via autofs are 'proto=tcp,intr,rw,async' 192.168.178.26:/data/Photos /mnt/photos nfs _netdev 0 0Īlso, other errors in the fstab file could be breaking this line.