I successfully modified FSTAB file to automount an NFS share in Manjaro XFCE, it automounts after reboot.
I modified the exact same file(FSTAB) with the exact same text in Manjaro Gnome on a different machine(same NFS share), but the share dose not automount after reboot. Please note the share can be mounted manually, but after reboot, it does not automount, but functions normally after manually mounting.
Is there a difference in automounting via FSTAB in XFCE vs. Gnome distributions?
Not even the provided systemd targets address this thoroughly, as seen in previous threads on this forum.
You could create your own custom “target”, which returns “true” when the NFS server is reachable (by ping), in which a systemd-mount (or fstab entry) depends on this target.
Just as an aside, I have a systemd service that rsyncs to a local NAS server, and when I view the logs it indeed shows that it “fails” multiple times before actually running when I resume from suspend. (This is because within the script, it keeps trying to ping the local NAS server every 2 seconds, and only when the NAS server responds to the ping will the rsync task execute. Think about that…) Before I had that “condition” the systemd service would fail and abort, to much of my confusion.)
It’s not only that. Some network adapters are terrible about establishing a working connection when resuming from suspend, for example. My laptop lacks an ethernet port, and so I have to use a USB-C-to-RJ45 dongle, which takes it dear sweet time to re-connect after resuming from suspend.
EDIT: I prefer the systemd units method (since it feels more “modular” and you can make copies of these files to use for later or as templates), but some people will hold a knife to your throat if you dare veer away from the fstab.
@dude_1776, in your case, it’s not “resume from suspend” but “immediately after reboot” that seems to be the issue. However, I wouldn’t be surprised if you noticed the NFS mount hangs for a few seconds (or more) if you resume from suspend from this machine.