I have no idea what is happening, all i know is that after some time, around a few days to a week after i do a manual check on my server, it just suddenly is inaccessible. None of my docker services are available, no gui is accessible, even the one for the server, but all the lights are on and it appears to be functional, expect for the fact that it wont display anything when i connect a display. When this happens, i have to force a restart with the case buttons, and it seems to restart just fine. but i just restarted it probably about an hour ago, and now all the logs for my dockers are just lines of color that vaguely look to be in the shape of what they normally look like. I tried to see if i could see anything obvious in my syslog file, but nothing looks out of place. I cant get a ups atm, but will in the future. Doubt its a power failure, as nothing else is affected. Currently, ive got a 2400g with 8gigs of ram on a B450M-HDV motherboard, no dedicated gpu, and was on 7.2.2 this morning, but its been happening since i was on 7.1.4 i believe. Ive attached the diagnostics.zip file i got from after i got they system up. Can anyone help to see if its a solvable issue, or what i can do to prevent it? Or if i need to provide anything else?

(Edit: Sorry, i accidently put that i had a 3200g installed, it is a 2400g, apologies.

olympus-diagnostics-20250908-1424.zip

Edited December 28, 2025Dec 28 by VALOR

These diags are from September 8th? Also, and since it's an AMD, make sure this has been taken care of:

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

You might also set up the Syslog server to capture the syslog activity leading up to the problem.

13 hours ago, JorgeB said:

make sure this has been taken care of:

I have set the power setting, bios are only a version or 2 behind, but im using my only 32gb flash drive for my unraid system, and this motherboard cant detect partitions, so i wasnt able to update it to the newest version. It says i updated them back in march last.

9 hours ago, Frank1940 said:

You might also set up the Syslog server to capture the syslog activity leading up to the problem.

I believe i have it setup now, so lets see if it record anything. if it does, would i post the most recent file in here after my server breaks again?

4 hours ago, VALOR said:

if it does, would i post the most recent file in here after my server breaks again?

If there is more than one, upload the one that covers the time period up to the time when the server went missing.

The system went down last night, just booted it up, and pulled the syslog file. there was only 1. I did read that the syslog can contain sensitive information, but all i have removed are any ip addresses, even though it looks like theyre only accesible locally, but i didnt want to take any chances. If the full un-edited version is needed for whatever reason, then i can provide that as well.

syslog-Olympus.log

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.

Alright, all i have for dockers that im actively using is a jellyfin server. Ive also got tailscale and maybe smb shares, idk if i actually got that setup on the server side. But i will try disabling those, and report back if anything changes.

@JorgeB After some testing and waiting, it seems like the docker for Jellyfin is causing the issues. I can send the logs again so you can see if anything is logged this time if youd like. It does seem like the docker only crashes when it gets autostarted, bc when i first turned it on after the system had been on for a few days without a crash, it lasted longer than it normally does. but when i did a clean shutdown with the auto start enabled, itd work fine for the first day or so, then crash.

I would recommend asking for help in the existing container support thread; you can find it by clicking on it