Hi,

I'll try to explain.

I upgraded hardware from 9+years old to almost current gen.

Intel® Core™ i5-14500 @ 4554, and new motherbord, that was the best i could find for the application.

I have attached diagnostics and MB info.

Since then i have had several weird behaviur, fixing one after another.

Now im stuck at one issue, where the unraid becomes unresponsive.

Sometimes i can still access shares but dockers is always unresponsive same with direct hdmi from the server with gui running.

Hoping you can shed some light on the issue, im adding from syslog at the bottom with marked timestamp.

Dec 26 16:18:19 LairStorage monitor_nchan: Stop running nchan processes

Dec 26 16:28:38 LairStorage nginx: 2025/12/26 16:28:38 [error] 10335#10335: *856637 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.0.6, server: , request: "GET /Dashboard HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.sock:", host: "192.168.0.175", referrer: "http://192.168.0.175/Dashboard"

Dec 26 16:28:39 LairStorage nginx: 2025/12/26 16:28:39 [error] 10335#10335: *859116 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.6, server: , request: "GET /plugins/unassigned.devices.preclear/assets/sweetalert2.js?_=1766762279696 HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php-fpm.sock", host: "192.168.0.175", referrer: "http://192.168.0.175/Dashboard"

Dec 26 16:28:39 LairStorage nginx: 2025/12/26 16:28:39 [error] 10335#10335: *859116 auth request unexpected status: 504 while sending to client, client: 192.168.0.6, server: , request: "GET /plugins/unassigned.devices.preclear/assets/sweetalert2.js?_=1766762279696 HTTP/1.1", host: "192.168.0.175", referrer: "http://192.168.0.175/Dashboard"

Dec 26 18:00:01 LairStorage move: Starting Mover Tuning ...

Dec 26 18:00:01 LairStorage move: Cron + options: start

Dec 26 18:00:01 LairStorage move: ionice -c 2 -n 0 nice -n 0 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start

Dec 26 18:14:56 LairStorage php-fpm[9573]: [WARNING] [pool www] server reached max_children setting (50), consider raising it

Dec 27 00:00:02 LairStorage move: Starting Mover Tuning ...

Dec 27 00:00:02 LairStorage move: Cron + options: start

Dec 27 00:00:02 LairStorage move: ionice -c 2 -n 0 nice -n 0 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start

Dec 27 06:00:01 LairStorage move: Starting Mover Tuning ...

Dec 27 06:00:01 LairStorage move: Cron + options: start

Dec 27 06:00:01 LairStorage move: ionice -c 2 -n 0 nice -n 0 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start

Dec 27 12:00:01 LairStorage move: Starting Mover Tuning ...

Dec 27 12:00:01 LairStorage move: Cron + options: start

Dec 27 12:00:01 LairStorage move: ionice -c 2 -n 0 nice -n 0 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start

Dec 27 13:43:16 LairStorage root: ACPI action left is not defined

Dec 27 13:43:17 LairStorage root: ACPI action left is not defined

Dec 27 13:43:17 LairStorage root: ACPI action left is not defined

Dec 27 13:43:17 LairStorage root: ACPI action left is not defined

Dec 27 13:43:17 LairStorage root: ACPI action right is not defined

Dec 27 13:43:18 LairStorage root: ACPI action left is not defined

Dec 27 13:43:18 LairStorage root: ACPI action left is not defined

Dec 27 13:43:18 LairStorage root: ACPI action right is not defined

Dec 27 13:43:18 LairStorage root: ACPI action down is not defined

Dec 27 13:43:19 LairStorage root: ACPI action up is not defined

Dec 27 13:43:19 LairStorage root: ACPI action left is not defined

---

Dec 27 13:49:57 LairStorage rc.rsyslogd: Syslog server daemon... Started.

Dec 27 13:49:57 LairStorage root: Delaying execution of fix common problems scan for 10 minutes

Dec 27 13:49:57 LairStorage unassigned.devices: Mounting 'Auto Mount' Devices...

Dec 27 13:49:57 LairStorage emhttpd: Starting services...

lairstorage-diagnostics-20251227-1352.zip W680-NAS-Motherboard-10G-3L12Bay-English.pdf

Nothing really relevant in that snippet, suggesting more of a hardware issue. Make sure the board BIOS is updated to deal with the Intel 13/14 gen issue, while non K CPUs are much less affected, there have been multiple confirmed cases here in the forum.

Also, and because memtest is only definitive if it finds errors, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM.

Hi,

Thank you, for your reply,

I assumed it would not be helpfull but trying to include everything. *syslog does not capture the actual error.

The last snippit i managed to log (unable to capture the img, was only logged on monitor)

BTRS error something Kernel panic

and something akin to unrecoverable fault.

So i have started the following process to try to fix the issue thank you @JorgeB

1. Updated Unraid *becouse of the kernel panic error i saw.

2. Bios is updated for the cpu issue, i have contacted support to make sure

3. i will do memtest again and test 1 stick at a time if the issue persists if abuve fail.

Will update. *might take some time ^_^

2 hours ago, SwedeOzzie said:

syslog does not capture the actual error.

Setup syslog server

Ok, found the issue it seams.

after a bit of pain i managed to get the output but only with screen attached since for some reason the error cant be writen to syslog. *even copy to flash

This is what i found.

kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x176/0x1d0

kernel: BUG: unable to handle page fault for address: ffff8805081ac63b

kernel: note: lsblk[63268]

This seams to be memory related, and i tested stick by stick and suddenly it became stable. *i only did memtest before so no issues there i thought.

and keeps being stable now for a weeks time.