I am on a Unraid Pro license and currently on Unraid 6.10.1. The machine is a Dell T340 server. The issue started about a week and a half back when I was on RC-8 or RC-10. I  can ssh to server from my home network and ping to yahoo.com just fails/timeouts. A few minutes later, it will start working again. Seems to be happening every few minutes. At the same time my other machines: mac mini, windows desktop, macbook pro, are not seeing this issue.

I also have another Unraid Pro license which is run on an older HP-Z800 running Unraid 6.9.2. That seems to not be experiencing such problems at this time.

I have tried multiple things at this time including switching network cables, trying different switch ports, changing the ethernet connection in unraid from bonded (active-backup) to unbonded but nothing has helped. Additionally, I have made multiple restarts, changed DNS servers, ran the extended Fix Common problems as well with no difference.

 

I have attached the diagnostics logs here and am really hoping someone can help since my server is close to unusable at this time. Help will be greatly appreciated. I would be very happy to provide any additional info.

 

Edit: I also want to add that the docker updates tab, plugins tab all show unavailable quite often due to this reason. Also, the apps page can also timeout or just take way too long to load.

tower-diagnostics-20220522-1229.zip

Edited May 22, 20224 yr by thegrumpyone

eth0 have up/down several times, eth1 never have link up ( suppose no cable insert )

 

May 21 20:41:40 Tower kernel: tg3 0000:05:00.0 eth0: Link is up at 1000 Mbps, full duplex

May 22 01:02:39 Tower kernel: tg3 0000:05:00.0 eth0: Link is up at 1000 Mbps, full duplex

May 22 01:35:52 Tower kernel: tg3 0000:05:00.0 eth0: Link is up at 1000 Mbps, full duplex

May 22 03:10:30 Tower kernel: tg3 0000:05:00.0 eth0: Link is up at 1000 Mbps, full duplex

May 22 03:11:10 Tower kernel: tg3 0000:05:00.0 eth0: Link is up at 1000 Mbps, full duplex

May 22 11:52:30 Tower kernel: tg3 0000:05:00.0 eth0: Link is up at 1000 Mbps, full duplex

 

4 hours ago, thegrumpyone said:

I have tried multiple things at this time including switching network cables, trying different switch ports, changing the ethernet connection

 

Usually it is cable problem, if above not help, pls try disable bonding on eth0 & eth1, then next swap NIC-1,2 be eth-0,1 and check again.

 

 

37 minutes ago, Vr2Io said:

eth0 have up/down several times, eth1 never have link up ( suppose no cable insert )

 

May 21 20:41:40 Tower kernel: tg3 0000:05:00.0 eth0: Link is up at 1000 Mbps, full duplex

May 22 01:02:39 Tower kernel: tg3 0000:05:00.0 eth0: Link is up at 1000 Mbps, full duplex

May 22 01:35:52 Tower kernel: tg3 0000:05:00.0 eth0: Link is up at 1000 Mbps, full duplex

May 22 03:10:30 Tower kernel: tg3 0000:05:00.0 eth0: Link is up at 1000 Mbps, full duplex

May 22 03:11:10 Tower kernel: tg3 0000:05:00.0 eth0: Link is up at 1000 Mbps, full duplex

May 22 11:52:30 Tower kernel: tg3 0000:05:00.0 eth0: Link is up at 1000 Mbps, full duplex

 

 

Usually it is cable problem, if above not help, pls try disable bonding on eth0 & eth1, then next swap NIC-1,2 be eth-0,1 and check again.

 

 

I have already swapped the cables a few times with new ones as well as the switch port that this server uses. I have also tried disabling bonding but I just tested with one port so will try to disable it and try the secondary port this time.

 

Not sure what you mean by "then next swap NIC-1,2 be eth-0,1 and check again." Did you just mean disabling bonding and trying both NIC's one at a time?

Only eth0 can manage Unraid, so if you try another network port, you need set it be eth0.

 

If you disable the problematic port and try next once, that's fine too.

Edited May 23, 20224 yr by Vr2Io

43 minutes ago, Vr2Io said:

Only eth0 can manage Unraid, so if you try another network port, you need set it be eth0.

 

If you disable the problematic port and try next once, that's fine too.

Ah gotcha. Did not know that. I have already disabled bonding and seeing the same error on current NIC. Will switch to the other soon and test.

Just an update. Switching the NIC's or disabling bonding didn't work.

 

The one thing that has helped so far is actually scheduling a cron to do a 'ping -c1 yahoo.com' every 2 minutes. I am also writing the results of this to a local file to monitor the success/failure on this.

 

So far, I have gone close to 40 minutes without an issue on the machine.

The issue looks to have resurfaced. I have ordered 2 new NIC cards and a new Netgear 24 port switch to replace my older TP-LINK one. Should be able to set this up by Wed/Thu and find out more.