April 12, 20242 yr This has happened to me twice. I'll just be working on my server, and all the sudden, it goes completely dark from my network. The only way I'm able to interact with it is via command line on the machine itself. The first time, I "fixed" it by restarting my machine. The second time. I "fixed" it by unplugging and re-plugging the ethernet cord from the computer. Here's a diagnostics file I took shortly after the second time it happened. tower-diagnostics-20240411-1828.zip
April 12, 20242 yr Community Expert I assume you only pulled the cable once? Log shows the link going down multiple times:, e.g: Apr 11 14:06:45 tower kernel: r8169 0000:02:00.0 eth0: Link is Down Apr 11 14:06:46 tower kernel: r8169 0000:02:00.0 eth0: Link is Down Apr 11 14:49:32 tower kernel: r8169 0000:02:00.0 eth0: Link is Down Apr 11 14:49:56 tower kernel: r8169 0000:02:00.0 eth0: Link is Down Apr 11 15:00:25 tower kernel: r8169 0000:02:00.0 eth0: Link is Down Usually this would be a cable, switch or NIC issue.
April 12, 20242 yr Author I was doing a decent amount of network work on the day this incident happened. I restarted my router multiple times. My internet just got fixed today, so I had to restart my router to get the internet working. Then I restarted it at least twice to change some settings on the router. So many of those are legitimate. Not sure if that covers all of them or not. > I assume you only pulled the cable once? Yes, to fix the issue, I pulled the cord once, around 10:24pm, but the diagnostics was taken way before then. I ended up needing to restart the machine to get everything fully working again though. Some containers weren't able to recover, even after restarting them. The issue started suddenly around 9:20pm. Edited April 12, 20242 yr by asherbig
April 12, 20242 yr Community Expert Reboot to clear the log and post new diags when it happens again.
April 30, 20242 yr Author It finally happened again. There were 2 diagnostics taken, one manually by me, and another when rebooting failed and it had to force reboot. tower-diagnostics-20240429-2241.zip tower-diagnostics-20240429-2244.zip
April 30, 20242 yr Community Expert Not seeing anything relevant logged, do you know the time code it happened?
April 30, 20242 yr Author It was around 10:40pm, it should be 3 or 4 minutes before the first diagnostic
April 30, 20242 yr Author What else could the problem be? The router seems like the only other relevant part of this system, but this behavior has only ever happened to the Unraid server.
May 8, 20242 yr Author This has happened again. I've attached another diagnostics report. This one happened early in the morning. Based on the logs from some services, I think this outage happened right around 2AM. (1:59:00, logs look okay, 2:00:37, logs show issues) tower-diagnostics-20240508-1506.zip
May 9, 20242 yr Community Expert 12 hours ago, asherbig said: (1:59:00, logs look okay, 2:00:37, logs show issues) Where are you seeing this?
May 9, 20242 yr Author Oh, I didn't see it in the logs in the diagnostics, but in some logs for programs that were running around the time of the Internet cutting out.
May 9, 20242 yr Community Expert Ah, OK, I still don't see anything logged in Unraid, do you have a different NIC you could try with?
May 10, 20242 yr Author I don't, but I've switched ethernet cables with another computer that I know to be working. I'll see if the error still happens. It's hard to know if it's fixed or not because it happens so randomly
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.