Kentucanuck

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

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?

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.

I have a Cyberpower CP1350PFCLCD set up with the Nutv2 plugin. The plugin can start and read a lot of static information, but it does not show any output or load metrics. I'm using the usb-hid driver and everything else seems to work. Amy I missing something? Output is one of the more important metrics behind time remaining.

I can't seem to find out how to add it back. I've added a metric of 1 to the gateway in the NIC settings. Rebooting and disabling/re-enabling the bridge doesn't bring it back. I added a NIC and under network settings changed my old nic to ETH1 and new nic to ETH0, I'm wanting the new 2.5gb ETH0 NIC to handle all functionality, I also noticed under "Interface Extras" that it only shows br0, eth1, and tailscale1, but not eth0. Is that a problem? If so, I'm not seeing a way to add it back.

Thanks for the input, how would I go about narrowing down the problem plugin?

I left that out of my initial post, but I have logged into safe mode and could not replicate the problem. Also, it seems like a lot of times when the web gui hangs and doesn't load, if you leave it long enough it comes back with an nginx 500 error.

When I log into the Web UI and navigate around the web ui freezes usually within a few minutes of working with it. The fans spin up high on the NUC, which isn't normal, indicating to me that the CPU is pegged. The server is still pingable, but going to the web gui just results in a spinning browser. The issue does not seem to occur when it is left alone to just run, only when navigating the web UI. Only physically power cycling brings it back. unraid-diagnostics-20230404-1824.zip unraid-syslog-20230404-2204.zip