I just (mostly) finished the switch from Pop_OS to Endeavour and really liking it so far. My first time outside of the Ubuntu/Debian realm and using Arch. Having one issue though that is driving me nuts and I can’t figure out a solution and that’s with mounting NFS shares. I’m 99% sure the issue is related to the network connection not yet being ready when the services try to mount the share but I can’t figure out how to fix that.
I’ve been through the Arch Wiki (and this thread which is basically my issue but doesn’t seem to be a resolution in there) and here’s what I’ve done so far:
Started out with the “normal” fstab entry that I used with Ubuntu and served me well there. However, mount would not come up on boot and I had to do a sudo mount /mnt/Backup to get it to show up. Tried all the various options mentioned in the wiki regarding _netdev and noauto. Nothing worked.
Switched to a systemd mount service. It worked fine/no errors when started initially. However, same problem. Doesn’t mount on boot, only mounts if I go into the terminal and restart the service. I even tried adding noauto figuring that it was fine that the mount wasn’t available right on boot but still get an error. NFS-Backup.mount: Mount process exited, code=exited, status=32/n/a
Enabled NetworkManager-wait-online.service. No errors after boot, Says it started and finished during boot.
I tried a systemd.automount but that didn’t work either.
Here’s my mount service in case I missed something obvious:
Would using autofs - which mounts on demand - meet your requirements?
That is what I use.
For example I just type cd /net/raspberrypi2/export/users and I’m there.
Note the ip address of raspberrypi2 is in my hosts file, substitute with ip address and it works fine as well.
I’ll give a shot. Pretty sure I tried something virtually identical before. Managed to get autoFS working so at least there’s that (needed to do direct mounts).