Hi, 

My server has randomly frozen a few times now (I think 3 times in total) over the last few months. When it happens I'm unable to access the GUI and I have force shutdown by pressing the power button. I haven't been able to identify what is causing the crash - attached are the diagnostics. 

plex-diagnostics-20240528-1942.zip

syslog-previous only covers a couple of minutes, enable the syslog server and post that after a crash.

Okay, I have enabled the local syslog server on my cache drive, being that it can be days or weeks before the crash occurs again. Should I create a new thread at that time?

You can use this one.

Hi! It crashed again. I rebooted (twice actually) but it doesn't look like the syslog file was stored anywhere? It should be on the root of the appdata folder where I assigned it but there are no files there. 

Is there a reason why the log wouldn't have saved? 

Post a screenshot from the syslog server settings.

Nevermind. I found it! I had the option to copy to flash on shutdown. I don't know if the file is rewritten on every reboot but hopefully this captures what's causing the crash.

syslog-previous

4 minutes ago, jackcurry said:

Nevermind. I found it! I had the option to copy to flash on shutdown. I don't know if the file is rewritten on every reboot but hopefully this captures what's causing the crash.

You need to either set the Mirror to Flash option or put the Unraid servers address into the Remote Server field.   The option you set only helps if the system actually goes through a shutdown sequence rather than crashing.

Got it, updated the syslog settings. I will provide the syslog after the next server crash. 
 

Took a long while for the server to crash again, but here is the most recent system logs. syslog

That syslog is just after a reboot, it's not the persistent one from the syslog server.

Huh, well now I can't connect to the web gui. The dockers are still running but I can't sign into the server to grab the file. If I reboot it now is it going to overwrite my previous syslog? 

It should be renamed to syslog-previous, assuming you are on the latest release.

Okay it failed again,
syslog (1)
Here is the most recent syslog and the syslog-previous. syslog-previous (2)

That syslog-previous only covers a few minutes uptime, what is the data/time of the last crash?

I'm not sure why the syslog previous isn't capturing the data you're looking for. It was crashed on July 8 I think around 9-10:30pm PST. When I logged in today I also received an error stating:  "Your flash drive is corrupted or offline."

Syslog-previous is from July 5th, the other log is after the crash, did you enable the syslog server as asked before?

Here are my current syslog settings. The way I read the user manual it sounded like mirror syslog to flash and local syslog server were separate settings so I currently only have "Mirror syslog to flash" Enabled. Do I need to enable Local Syslog Server as well? 

You should have the persistent syslog in the flash drive, but not that if you reboot twice after the crash the one that matters will be gone.

Yeah it doesn't seem to be working that way. It crashed again this morning, so I pulled the drive and popped it into a separate windows computer. Attached are the only logs available and they are both not capturing anything from the clean reboot I did on the 9th to when it crashed today.  

When I try to go to the manual about these settings the URL links are broken. 

syslog-previous syslog

Possibly the server is rebooting multiple times on its own, enable the remote syslog option, you just need to choose a share and set the server local IP in the remote syslog field

Okay I'll try try that. Thanks for your continued help. 

Hi - Crash happened sometime this morning. Again - unable to access via the GUI and if I connect directly to comp with a monitor and keyboard I just get a blank screen and it's is completely unresponsive to any keystrokes. 

syslog-192.168.0.113.log

Unfortunately there's nothing relevant logged, this can be 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.