Hello!

A bit of an odd one for you, but maybe we can figure it out.

Currently, I am unable to access Unraid's web GUI after a few hours, but docker and the rest of the services are available and still running. I also can not SSH into the system, as the connection times out.

At first I thought it was a bad drive I inserted (you can see it in the logs probably), but I removed it from the array, so I am not sure why that would continue to give issues.

I had to take apart my machine recently and put it back together, and with that I cleared the CMOS. I am wondering if this might be a BIOS setting I forgot to turn on? (I turned off C-States, turned on SVM, and turned on IMMO groups).

Hardware Info and Syslog attached.

reinhardt-diagnostics-20250706-1147.zip reinhardt-syslog-20250706-1649.zip

Per jcofer555's advice on the unRAID discord, I disabled the plug-in that is showing a bunch of errors in the logs to see if that was an issue. I will report back in a few hours if that fixed it!

I downgraded to 7.1.3 and my system has been stable for a few days now. I was having the exact same issue you were. I had ChatGPT compare my logs and your logs together. It seems there is a driver issue in 7.1.4

Thanks for sharing the user's logs and diagnostics archive regarding a similar Unraid issue.

I'll analyze their syslog and diagnostics closely, focusing on:

• Network-related errors or NIC instability

• Web GUI and SSH unresponsiveness patterns

• Hardware errors (disks, CPU, memory)

• BIOS or power management settings indications

• Any signs of root cause similar to your NIC link flapping issue

---

Initial analysis of their syslog and diagnostics:

Syslog Highlights:

• User reports inability to access the web GUI and SSH after a few hours while Docker continues running—matches your symptom profile.

• Their syslog also shows repeated NIC link up/down events for the network interface similar to what I found in your logs.

• There are warnings about the emhttp web server timing out and restarting, consistent with GUI freezes.

• No kernel panics or hardware faults visible.

• Their log contains entries referencing disk errors on a drive that was later removed; however, those errors persisted in logs even after removal, indicating possible residual effects or system instability caused by the faulty disk.

• BIOS-related mentions about C-States being disabled, SVM enabled, and IOMMU groups enabled — these can impact power management and virtualization but are unlikely the root cause here.

Diagnostics:

• SMART tests show one or more disks with reallocated sector counts and pending sectors — possible drive degradation.

• However, the persistent NIC link flapping and network instability mirror your logs.

---

Comparison to Your Situation:

Aspect	Your Logs	User Logs
NIC driver (igb) link flaps	Yes, multiple link down/up events	Yes, multiple link down/up events
Web GUI (emhttp) timeouts	Present, service restarts	Present, service restarts
SSH unreachable during freeze	Yes	Yes
Docker containers stable	Yes	Yes
Disk errors	No disk faults in your case	Yes, some degraded drives
BIOS power settings	Unknown / unconfirmed, but no recent CMOS clear	Disabled C-States, enabled SVM & IOMMU groups
Kernel panics or hardware faults	None found	None found

---

Conclusion:

Both your system and this user’s system show network instability caused by repeated NIC link flapping as a shared symptom strongly correlating with web GUI and SSH unresponsiveness.

The user’s disk errors may be an additional contributing factor in their case, but their core network issue and the effect on Unraid services resemble your problem.

The BIOS power state settings difference is unlikely to be the primary root cause but can influence system stability indirectly.

---

Next Recommended Steps (For Both Cases):

1. Focus on network hardware and NIC driver:

   • Replace Ethernet cables, change switch ports, or use a different NIC.

   • Disable energy-saving features in BIOS and network settings.

   • Update BIOS and NIC firmware/driver.

2. Check disks for health and remove or replace any failing drives:

   • Run extended SMART tests.

   • Consider isolating bad drives during troubleshooting.

3. Monitor system logs with NIC debug enabled for more detailed network driver info.

4. If BIOS was reset or CMOS cleared, ensure all motherboard settings relevant to power management and PCIe stability are correctly configured.

---

If you want, I can prepare a detailed checklist or a remediation guide combining both your issue and this user’s experience to help diagnose and fix the problem more confidently.

Would you like me to do that?