It took itself off the network, locked up, and wouldn't display through gpu to screen.

server-diagnostics-20241231-1356.zip

Make sure this has been taken care of:

 

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

 

I updated bios to FFc, and set Power Supply Idle Control to "typical current idle" and it locked up again. I've attached the diagnostics.

server-diagnostics-20250102-1313.zip

Enable the syslog server and post that after a crash.

Here is my syslogserver-syslog-20250124-1941.zip

Unfortunately, there's nothing relevant logged, this can also 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, including the individual docker containers. 

server-syslog-20250227-2020.zipDoes this one show anything?

9 minutes ago, gecl said:

Does this one show anything?

It only shows a few minutes after reboot.

 

How do you have syslog server configured?

I thought I did, to save to SSD, but I don't see it in that folder. What settings do I ned to change?

If you want it to save to the Local Syslog Folder location then you need to put your server’s address into the Remote server field to get it to log to itself.

 

Alternatively you can set the Mirror to flash setting to get it out into the ‘logs’ folder on the flash drive.

syslog-10.27.27.231.log

Does this explain why it locked up?

There are errors on parity2, but that doesn't explain if the server crashed.

is there a way to remove the errors?

If you mean the ERRORS column in MAIN, you can reset the READS, WRITES, ERRORS columns with the CLEAR STATS button in Array Operation. They will also reset when you reboot.