shingaling

Actually name resolution doesn’t happen. I had it idle for 20+ minutes without Unraid resolving the name of the NFS-Sharing-Servers. Only after this „trick“ with calling their ip‘s first, did the nameresolution happen at all. at least now i can let it run and not worry that once the power fails, all connectivity is gone after reboot. thanks for your help @dlandon 👍🏻

Hey @dlandon I found (a weird noob) solution: On each Synology serving the NFS-Shares I created a new share (wakeywakey) Then in UD i added this share (wakeywakey) as a remote NFS share, but not using the name of the (Synology) Server but instead using the IP-Adress (192.168.xx.xxx:/volume1/wakeywakey) Now when I reboot the system (or it reboots after a power failure), it mounts all shares with no issue and no delay (i set the delay down to 12secs, guess I could go to the standard of 5sec. This works for me ... hope this helps anyone having the same issue.

thanks @dlandon I set new permissions (on the synology serving the NFS shares) I tried to lower the protocol (from 4.1 to 3) The weirdest thing: A reboot on my second unraid server doesn't auto-mount any NFS shares (see attached diagnostics) A reboot on my first unraid server auto-mounts only one of the 2 servers that have nfs shares (issue as described above by you) So I am stuck. I mean: Everything will be easy, as long there is no power outage. If there is, all wheels stand still, and I have to manually mount each share.

those servers are always on ... is there a way to set unraid (and UD) to wait on restart/reboot until network-connectivity is reached?

Actually, after powerfailure/on reboot none of them mount. But when I go into Unraid and even just click on "Add NFS Share", refresh the available NFS-Servers, Select one, and then cancel the procedure .... suddenly all mounts from this server are found again, and the "MOUNT"-button turns from grey to orange, But it doesn't find them by itself on reboot/power failure-restart Is there anything that can be done for UD to find the NFS-Shares again by itself, to automount them? I come from Ubuntu. There I could just add the NFS-Shares to the /fstab. If power failed and came back, the server would restart, and load the paths from the /fstab anew. Never had to open any port on the NFS-Share-Servers.

sure

Hi I noticed, that after a power failure & (auto)restart of my Server (NUC), the NFS-Shares (on local Synologys) do not get mounted automatically. I use the U(nassigned)D(evices) Plugin, all NFS-Shares are set on automount. What can I do, so the NFS-Shares get mounted "by themselves"? PS: I also noticed, that the NFS-Shares don't get mounted on reboot ... Do I need to set /etc/fstab-entries, like in linux? then again I would think the plugin is there for that. any help is welcome

Sorry, will do Posted the question here (for anyone stumbling over this thread here)

Hi I noticed, that after a power failure & (auto)restart of my Server (NUC), the NFS-Shares (on local Synologys) do not get mounted automatically. I use the U(nassigned)D(evices) Plugin, all NFS-Shares are set on automount. What can I do, so the NFS-Shares get mounted "by themselves"? PS: I also noticed, that the NFS-Shares don't get mounted on reboot ... so maybe UD's auto-mount is broken? Or do I need to set /etc/fstab-entries, like in linux? then again I would think the plugin is there for that. any help is welcome