Hi Everyone,

I'm still a bit of a newb to Unraid (had it for a few months now), and generally it's worked well for me, but I'm now having issues that arose a couple of days ago. I didn't change any settings, so I don't know why they are coming up. Here's what's going on:

• The webGUI will become unresponsive to the point I need to reboot the server.

• For both plugins and dockers, the version for all will show as "unavailable," though when I initially log into the webGUI I'll be able to perform updates, which appear to be successful but then do not show as up-to-date.

• The webGUI is more stable in safe mode (no plugins), but still the same issues with plugin and docker versions.

• In safe mode, I am able to start the array, and dockers will work.

• Parity is valid, so I don't think it's a drive or array issue.

• I've tried using ChatGPT to help troubleshoot the issues, with no luck.

Anyways, these are just my observations...I've attached the diagnostic report and the syslog from today.

I am running version 7.2.0, and here's my hardware:

Model:	Custom
M/B:	HP 83E1 Version KBC Version 07.B4.00 s/n PGTXL0BCYB06Q8
BIOS:	HP Version Q01 Ver. 02.02.04 Dated 08/06/2018
CPU:	Intel® Core™ i7-8700 CPU @ 3.20GHz
HVM:	Enabled
IOMMU:	Enabled
Cache:	L1 Cache: 384 KiB, L2 Cache: 1536 KiB, L3 Cache: 12 MiB
Memory:	16 GiB DDR4 (max. installable capacity 64 GiB)
Network:	eth0: 1 Gbps, full duplex, mtu 1500
Kernel:	Linux 6.12.54-Unraid x86_64
OpenSSL:	3.5.4
Uptime:	1 hour, 20 minutes

TIA!

clayserv-safemode-diagnostics-20251221-2037.zip clayserv-syslog-20251222-0244-2.zip

Setup syslog server

Updated with the latest diagnostic, configuration, and syslog files.

One additional bit of information, when I try to ping my primary DNS or google.com, I will often get very high packet loss (around 68%), and when it's not working, if I try the same pings directly from the server (keyboard and monitor connected), it will show 100% packet loss.

Diagnostics.zip

Edited December 23, 2025Dec 23 by DJjclay
Additional information added

Assuming syslog-previous covered an event, the server was running and shut down. How do you initiate the shutdown?

Dec 23 05:27:57 ClayServ emhttpd: spinning down /dev/sdc

Dec 23 06:01:43 ClayServ root: /mnt/cache: 413.3 GiB (443826184192 bytes) trimmed on /dev/nvme0n1p1

Dec 23 15:26:17 ClayServ shutdown[2115428]: shutting down for system reboot

Dec 23 15:26:17 ClayServ init: Switching to runlevel: 6

I initiate the shutdown/reboot from the dashboard. I’ve been doing this so that I can access the webGUI again since I can’t always be physically at the server to work directly in GUI mode

Sorry, but I'm not sure I follow. You mention the GUI being unresponsive, so how did you initiate the shutdown from the dashboard?

The GUI from another computer on my LAN will become unresponsive. So I connect a mouse, keyboard, and monitor directly to the server. In the worst cases when that doesn't work, I have the external power button on my server set up to initiatite a safe shutdown.

If you can still access the GUI locally but not from another PC, it suggests Unraid is not the problem, but something on your network.

That’s true, but even the local GUI becomes unresponsive and I have to reboot. Additionally, pings to my router and outside my LAN consistently get very high packet loss (ranging from 60% to 100%) and both my dockers and plugins all show versions as “unavailable” so I cannot update them or even see if they are the current version.

10 hours ago, DJjclay said:

but even the local GUI becomes unresponsive and I have to reboot.

Enable the syslog server and post that when you cannot also access the local GUI.

My issues seem to have been resolved. Here's what I did:

1. In my router's settings, I set a new, unused IP in the DHCP Reservation settings.

2. In Unraid, changed the IPv4 static IP to the same IP I added in my router settings.

That's it. When I thought to do this, I wasn't even sure it would fix the issues, but I thought I'd just try anyways. l was only having issues with my server, not with anything else on my LAN, hence I was convinced it was my server that was the problem. It seems obvious now that I needed to assign the same static IP in my router as what had been set in Unraid, but I had no issues whatsoever for 8 months, so I was puzzled. Anyways, in hindsight, and considering my router is getting up there in age, it was clearly only barely been working for the last 8 months, and then it finally degraded to the point where the router wasn't able to figure things out on its own.

It's working perfectly now. Lesson learned.

Often you can reserve IP by MAC address in the router then just let Unraid use DHCP

10 minutes ago, trurl said:

Often you can reserve IP by MAC address in the router then just let Unraid use DHCP

I'm just learning this now, haha. Isn't it not good practice to let Unraid use DHCP though? If you want the best reliability, isn't assigning a static IP across server and router the way to do it?

What if you assign a static IP the router has given to something else?

Simpler to control the network from the one place that really matters.