December 1, 2025Dec 1 Server has been consistently spotty. Thought I had it worked out but it continues to crash or become unresponsive.primaris-diagnostics-20251201-1305.zip
December 2, 2025Dec 2 Community Expert Enable the syslog server and post that after a crash, but I see it's a 14700K, so very possibly it's the Intel 13/14 gen issue, looks for a BIOS update; it can help if the CPU is not too far gone.
December 2, 2025Dec 2 Author Crashes every night. Log before the last two crashes. I thought it might be the Intel issue. But I built this in January of 2025 and had the latest BIOS flashed onto the board before I did anything else.Nov 30 19:55:22 Primaris rc.docker: tautulli: started successfully!Nov 30 19:55:22 Primaris rc.docker: tautulli: wait 270 secondsNov 30 19:59:52 Primaris rc.docker: Containers started.Dec 1 01:00:01 Primaris kernel: mdcmd (36): check Dec 1 01:00:01 Primaris kernel: md: recovery thread: check P ...Dec 1 01:12:40 Primaris flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup updateDec 1 19:09:05 Primaris kernel: eth0: renamed from vethc39a167Dec 1 19:09:05 Primaris kernel: docker0: port 4(vethe361b60) entered blocking stateDec 1 19:09:05 Primaris kernel: docker0: port 4(vethe361b60) entered forwarding stateDec 1 19:14:53 Primaris flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup updateDec 1 19:44:46 Primaris kernel: md: sync done. time=25180secDec 1 19:44:46 Primaris kernel: md: recovery thread: exit status: 0Dec 1 19:44:53 Primaris flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
December 2, 2025Dec 2 Community Expert Solution There's nothing relevant logged there, assuming it covers a crash, it suggests a hardware issue. Based on the number of issues I've seen with those CPUs, it would be my main suspect, but if you have multiple RAM sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM.
December 2, 2025Dec 2 Author I just replaced the RAM kit this weekend hoping it would fix it. Yea that's the only thing logged before the reboot.
December 2, 2025Dec 2 Author I'm on a 2023 BIOS. Checked DMESG and found that. Now to just hope I haven't ruined the CPU
December 4, 2025Dec 4 I think 7.2.2 isn't playing nice with the intel iGPU, try rolling back the OS.https://forums.unraid.net/bug-reports/prereleases/69x-611x-intel-i915-module-causing-system-hangs-with-no-report-in-syslog-not-alder-lake-r1674/page/14/?tab=comments#comment-36452
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.