October 26, 20241 yr I have this weird issue where my Server starting beginning of this week, would just drop offline. It would send 10 packets and then drop for 40-60 packets. Then send another 10 and down again. I have 3 NICs in this machine, 2 onboard and 1 PCIE 10G NIC. I had them all bonded together so I decided to go into the BIOS and disable 1 of the onboard NICs (1 GBE NIC) and then changed my Unraid Settings to use the 5 GBE Obnboard NIC as eth0. This didn't solve the issue. So then I decided to use my 10GBE PCIE NIC as the main NIC and changed the Network Rules in Unraid to use that NIC as ETH0 instead. This helped some and the system does stay online contnuesly but only for about 10-15 minutes, then it drops completely offline again. I did have an issue earlier this week where I had a network loop in my house. This I know caused some of my intial issues but this was solved as of last night and I am still having issues. It's just not as bad. Edit: I now have both onboard NICs disabled in the BIOS tower-diagnostics-20241026-1154.zip syslog-previous Edited October 26, 20241 yr by ech0chamber
October 27, 20241 yr Community Expert Based on the syslog-previous looks like the link went down, grab the full diags after is happens again and before rebooting, you can grab them from the CLI
October 27, 20241 yr Author 3 hours ago, JorgeB said: Based on the syslog-previous looks like the link went down, grab the full diags after is happens again and before rebooting, you can grab them from the CLI That is what I did for the above logs. and I grabbed the logs before rebooting. The link seems to be constantly going up and down as it'll send 10 packets every couple of minutes or so Also isn'ty there a current syslog in the tower diagnostics? I'll grab fresh logs of you really need it Edit: Ok reboot server and then waited for the issue to occur and then immediately dumped logs tower-diagnostics-20241027-0838.zip Edited October 27, 20241 yr by ech0chamber Logs
October 27, 20241 yr Community Expert Not seeing anything logged, what was the timecode when it failed?
October 27, 20241 yr Author 18 minutes ago, JorgeB said: Not seeing anything logged, what was the timecode when it failed? It was about 10 seconds before I dumped the logs
October 27, 20241 yr Community Expert There's nothing logged that I can see, suggesting it may be an external issue, you can boot with a new flash drive using a stock Unraid install, no key needed, then retest, that will rule out a config/app issue.
October 27, 20241 yr Author 2 hours ago, JorgeB said: There's nothing logged that I can see, suggesting it may be an external issue, you can boot with a new flash drive using a stock Unraid install, no key needed, then retest, that will rule out a config/app issue. I let it run without the array started for about 30 minutes with a continueues ping and no packets were dropped. Usually it happens with 10-15 minutes. But as soon as I started the array I started having issues. Testing with a another drive with a trial license in a few minutes Edited October 27, 20241 yr by ech0chamber
October 27, 20241 yr Author 6 hours ago, JorgeB said: There's nothing logged that I can see, suggesting it may be an external issue, you can boot with a new flash drive using a stock Unraid install, no key needed, then retest, that will rule out a config/app issue. Okay. I think I've narrowed it down. So now with a Fresh thumb Drive it seems to only occur once I've started the docker service. But it's pretty immediate. As soon as I start the service shit goes haywire. Is it a container freaking out? Edit: Okay I have the docker service running but with 0 containers running. I'm going to wait about 10 minutes and then start running each container one at a time till I notice an issue. I have 90 containers (probably only 60-70 I really need) so it'll take some time for me to narrow down the culprit probably Edited October 27, 20241 yr by ech0chamber
October 28, 20241 yr Community Expert Could be an issue with the docker networks, try recreating the docker image.
October 28, 20241 yr Author 2 hours ago, JorgeB said: Could be an issue with the docker networks, try recreating the docker image. I'm using directory. Not an image
October 28, 20241 yr Author 10 hours ago, Veah said: Long shot: switch your ipvlan/macvlan setting. I guess I can try but I know from prior instances, server really hates Macvlan
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.