My server is crashing seemingly randomly and I can't figure out why.

[Paravane]

My unRAID server just keeps randomly freezing up and rebooting. It started off happening 1 time. I just figured it was a power flicker and/or the UPS wigged out. Rebooted it and it was fine. About 3 weeks later I woke up to notice Plex wasn't responding so I tried to login and it had froze. Rebooted and it was fine. About 1 week later and it did it again. Now it's every 30 minutes to 1 hour. It'll come up and be fine every time with no clues as to what errors might be causing it.

 

I haven't made any changes recently.
 

The only error I get is a Machine Check that tells me my CPU (Ryzen 5800x) isn't supported and I need to download a different plugin? But when I look into it, I've seen my version of unRAID (latest stable) it is supported and that error really doesn't mean anything. Also I've been getting that error since I installed this over a year ago and it hasn't been a problem.

 

Things I've tried:

Exporting Syslogs to my desktop

    -No clues

Stopping all Dockers and VM's

    -With all Dockers and VM's stopped it stayed on long enough for me to backup my dockers to my desktop but otherwise will froze and

     rebooted after about 1.5 hours.
Safemode

    -Still freezes

Disabled XMP Profile
    -No change

Checked SSD scrubbing and balancing

    -No change

 

 

I've exported my diags below. Maybe someone here smarter than me can make sense of what might be going on.

I'm currently running a memtest but it's now 5am and I can't keep going. Gonna let it run till it's finished.

I'm going to catch some sleep and I'll be back, so if I don't reply quickly that would be why.

 

And thanks in advanced to any kind souls who wonder in here in an attempt to help!

 

lodgecloset-diagnostics-20240414-0434.zip

Edited April 14, 2024 by Paravane

[itimpi]

The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted.  You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to a crash.  The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field. 

[Paravane]

10 hours ago, itimpi said:

The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted.  You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to a crash.  The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field. 

 

That's what I did. I've been exporting the syslogs to my desktop using win-syslog server running there.

But I'll set it to export to the flash drive and see what comes up.

log_1233317640.log

Edited April 14, 2024 by Paravane
Added Log.

[Paravane]

Memtest passed without errors btw.

[JorgeB]

Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.