I've upgrade my unraid server from a very oldIBM x3200 M3 server to new hardware (Intel 245k base). Since then the system become very unstable. The server GUI will become very slow / not responding after a while. I can still ping the server but I am not able to ssh to it anymore.

I've ran a memtest the test result is passed. I've also change the docker to using IPVLAN (previously MACVLAN). However it is still the same.

Attached diagnostics file.

unraid-diagnostics-20251129-1415.zip

11 minutes ago, chhuan said:

I've also change the docker to using IPVLAN (previously MACVLAN).

This is not an issue since 6.12.11, enable the syslog server and post that after a crash, but if the issues started after the hardware upgrade, it suggests a hardware problem.

Syslog attached. This time the GUI freezed but I am still able to connect to the ssh. Tried to issued command powerdown but it's is deprecated ...

syslog-previousunraid-diagnostics-20251129-2044.zip

Edited November 29, 2025Nov 29 by chhuan

Looking at that screenshot suggests an issue with Docker, and the syslog also shows multiple Docker related call traces, e.g.

Nov 29 20:13:43 Unraid kernel: note: docker[199681] exited with preempt_count 1

Nov 29 20:13:43 Unraid kernel: Fixing recursive fault but reboot is needed!

Nov 29 20:13:43 Unraid kernel: BUG: using smp_processor_id() in preemptible [00000000] code: docker/199681

Recommend recreating the Docker image first:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#re-creating-the-docker-image-file

Then:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applications

Also see below if you have any custom docker networks:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networks

P.S. Also, some ATA errors with parity and disk1, check/replace their cables

I've recreated the Docker image but not starting the containers yet. the system is doing parity check. I will update again tomorrow.

I found this igpu error in the syslog. May I know what does it means ?

9 hours ago, chhuan said:

I've recreated the Docker image but not starting the containers yet. the system is doing parity check. I will update again tomorrow.

The system still crashes. here are the latest syslog

syslog-previous

I would be suspecting possibly an issue with the systemboard. While I don't know the reason for the igpu error listed above, your screenshot is also still calling out errors from ata2 and also a little bit further in the logs ata4.

I did have a look to see if there was a bios update for your machine, but it looks like it was updated not too long ago. Before version 7, I did have the issue where the GUI would become unresponsive but could ssh into it at least initially. It was having the web gui open for long periods would cause the issue. Interestingly, searching that syslog file, I don't see any reference to version 7 of unraid, I only see version 6.12.54 mentioned. (But I am no unraid guru.)

As mentioned by JorgeB above, I'd be checking out the hardware, try and run some diagnostics on the board and CPU to see if that helps. Good luck!