January 7, 20251 yr I had NFS working happily mounting them in Unraid from a target Synology. I added a second higher speed NIC to the Synology and tested that it works by accessing the web GUI and wanted to mount the shares via the higher speed NIC on the synology. Here is the issue: Let's say NIC 1 (old) is 192.168.1.10 and NIC 2 (new) is 192.168.1.20 on the synology. All mounts are working with the .10 address and .20 address when both Synology NICs are active. Showmount in Unraid shows all shares when running it against each of those two IPs. Now, if I disable the old NIC in Synology all mounts fail. Running a showmount on the new .20 NIC in the Synology gives an "rpc mount export: RPC: Unable to receive; errno = No route to host" error. This doesn't make any sense because .20 worked fine before disabling the .10 NIC in the Synology. This seems like an Unraid issue, because I can mount NFS shares on other Linux machines just fine to the .20 IP with the .10 NIC disabled on the Synology, I'm only having this issue in Unraid. I have no idea what could be causing this.
January 7, 20251 yr Community Expert Show both of the Unraid mount commands (use the 'Code'-- the <> icon --formatting)...
January 7, 20251 yr Author 6 hours ago, Frank1940 said: Show both of the Unraid mount commands (use the 'Code'-- the <> icon --formatting)... Sorry, I'm not exactly clear on what you're asking, do you want to see the showmount result before and after disabling the second synology NIC?
January 7, 20251 yr Author 6 hours ago, Frank1940 said: Show both of the Unraid mount commands (use the 'Code'-- the <> icon --formatting)... If you are looking for the console showmount commands, here is what I'm referring to. I can showmount on .20 (new nic on Synology) when both Synology NICs are active and see all the shares. In this example I then disabled the .10 (old nic on Synology) and ran showmount again against the new .20 NIC and get an RPC error. I immediately pinged .20 to ensure connectivity and that works. Also, other Linux machines can still mount these same NFS shares, for whatever reason Unraid is confused about something. I'm not savvy in Linux to know where to look. .25 is the Unraid server I'm running the commands from. Also, I should add that the Synology firewall is completely disabled. root@Unraid:~# showmount -e 192.168.1.20 Export list for 192.168.1.20: /volume1/Share1 192.168.1.25 /volume1/Share2 192.168.1.25 /volume1/Share3 192.168.1.25 root@Unraid:~# showmount -e 192.168.1.20 rpc mount export: RPC: Unable to receive; errno = No route to host root@Unraid:~# ping 192.168.1.20 PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data. 64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=0.168 ms 64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.202 ms 64 bytes from 192.168.1.20: icmp_seq=3 ttl=64 time=0.218 ms 64 bytes from 192.168.1.20: icmp_seq=4 ttl=64 time=0.168 ms 64 bytes from 192.168.1.20: icmp_seq=5 ttl=64 time=0.243 ms 64 bytes from 192.168.1.20: icmp_seq=6 ttl=64 time=0.251 ms Edited January 7, 20251 yr by Kentucanuck
January 8, 20251 yr Community Expert Sorry, I have not used nfs for a number of years now and the nomenclature has escaped my memory. I was referring to rules that used to are setup to access the servers. And I happened to think of another thing but has been cropping up in discussions over the past few months. Apparently, Unraid and nfs are having issues. See here for one example: https://forums.unraid.net/bug-reports/stable-releases/61214-first-seen-in-61211-nfs3-not-working-properly-because-nfsd-and-lockd-are-not-registered-with-portmapper-r3172/ IIRC, it seems to have affected every release since about 6.12.10 EDIT: and here is another one: https://forums.unraid.net/bug-reports/stable-releases/nfs-mounts-are-gone-after-upgrading-from-61210-to-61214-r3476/ Edited January 8, 20251 yr by Frank1940
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.