My suggestion - Add "_netdev" to the parameters list:

NAS2HOST:/volume1/export/ /mnt/NAS2 nfs _netdev,rw,vers=3,soft,bg,intr 0 0

And, if it doesn't work, try this instead and please let us know which one worked best:

NAS2HOST:/volume1/export/ /mnt/NAS2 nfs rw,vers=3,soft,bg,intr,x-systemd.requires=network-online.target 0 0

The 'x-systemd.requires=network-online.target' makes sure that this NFS mount is _only_ mounted fter a network interface is really online.

And I'm wondering why systemd doesn't do this by default because NFS mounts are always _only_ possible with an online network.

Can someone explain to me the logic of what systemd does here?

Regards, Simon

======== Bill Gee

On Tuesday, August 17, 2021 9:18:53 AM CDT Felix Natter wrote:

...

hello fellow CentOS Users,

on Scientific Linux 7 (_very_ similar to CentOS7), I get this when trying to mount NFS Shares (exported from Synology NAS) automatically at boot time:

[root@HOST ~]# journalctl -b 0 | grep NAS[20] Jul 01 13:32:09 HOST systemd[1]: Mounting /mnt/NAS0... Jul 01 13:32:09 HOST systemd[1]: Mounting /mnt/NAS2... Jul 01 13:32:09 HOST systemd[1]: mnt-NAS0.mount mount process exited, code=exited status=32 Jul 01 13:32:09 HOST systemd[1]: Failed to mount /mnt/NAS0. Jul 01 13:32:09 HOST systemd[1]: Unit mnt-NAS0.mount entered failed state. Jul 01 13:32:09 HOST systemd[1]: mnt-NAS2.mount mount process exited, code=exited status=32 Jul 01 13:32:09 HOST systemd[1]: Failed to mount /mnt/NAS2. Jul 01 13:32:09 HOST systemd[1]: Unit mnt-NAS2.mount entered failed state.

I read that enabling NetworkManager-wait-online.service can mitigate that, but it's already enabled:

[root@HOST ~]# systemctl list-unit-files|grep wait chrony-wait.service disabled NetworkManager-wait-online.service enabled plymouth-quit-wait.service disabled

/mnt/NAS2 is defined in /etc/fstab (/mnt/NAS0 is mounted analogously):

NAS2HOST:/volume1/export/ /mnt/NAS2 nfs rw,vers=3,soft,bg,intr 0 0

This does not always occur, and it seems to be a race condition, because it did not occur a few months ago, before we moved offices (when only the networking changed slightly).

Of course, once the computer is booted, I can always mount the shares without problems.

Does someone have an idea?

Many Thanks and Best Regards,

---

CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos

Felix Natter fnatter@gmx.net writes:

hi Bill,

Bill Gee bgee@campercaver.net writes:

...

My suggestion - Add "_netdev" to the parameters list:

NAS2HOST:/volume1/export/ /mnt/NAS2 nfs _netdev,rw,vers=3,soft,bg,intr 0 0

thanks for the hint. I added this, and so far I did not see the problem. Cannot say for sure though, as this does not occur always.

For the record: I worked around the problem with the "xsystemd.automount" mount option, which triggers the mount on first access. This seems to work fine.

Best Regards, Felix