K1ngFiasco

Ran Memtest86+ until a pass, and installed the plugins to monitor temps. Never saw the CPU get above 85c, usually sat between 60c to mid-70c depending on load, and still had a crash. Swapped out the PSU and it's been up for nearly 4 days straight at this point. Thank you again for your help. I had a bad feeling it was the PSU but wanted to be sure, and the advice here gave me enough information to narrow things down.

I see. Is there an easy method to determine which of those two are the culprit, such as some kind of logging of temps or load?

The server is off despite me not asking it to shutdown/reboot. It seems like a crash because it begins a parity check every time I turn it back on. Typically it goes like this: I wake up, and check to see if the server is on. I turn it on if not. Everything seems to boot up fine and a parity check is automatically started. Then at some point, usually the next morning or evening, I will find the server is off again. The parity checks are often logged as "completed" so I don't think it's crashing while that is going on. A typical parity check takes ~16 - ~18 hours to complete for me.

Let me start by thanking you in advance for taking a look at my problem and helping me. I am a complete layman when it comes to Unraid, Docker, and Linux as a whole. Everything I have put together has been done by following guides (specifically those by spaceinvaderone and TRaSH Guides) and nearly nothing has been done from my own knowledge. Your time, patience, and help are appreciated. I get frequent unclean shutdowns on my server. Sometimes it can stay up for about a week, other times it will go down multiple times in a day. I have a UPS connected and the rare times I have a power outage, everything shuts down cleanly. The only time I have been able to really replicate it, has been when running a Minecraft server with binhex-crafty-4 docker container. It would go down every couple hours while playing. However, the unclean shutdowns predate me having a Minecraft server at all so I am assuming it's a victim of the problem and not the cause. Today, after powering on the server, I turned all the docker containers off to see if it can stay up without anything really running on it. In the meantime, I am hoping one of you can identify a solution. Thank you again for your time and help. I think I have attached everything I need to, but if you require more I can provide it so long as you can explain where. I have mirrored syslog to flash, and have prefixed those files with "Flash-". The others I obtained via Unraid GUI. pheonix-diagnostics-20250928-2032.zip pheonix-syslog- IP -20250929-0131.zip pheonix-syslog-20250929-0130.zip pheonix-syslog-previous-20250929-0131.zip Flash-pheonix-diagnostics-20250927-0946.zip Flash-pheonix-diagnostics-20250928-2032.zip Flash-syslog Flash-syslog.zip Flash-syslog-20250927-094704.txt Flash-syslog-previous

Hello all, apologies in advance as I am a very inexperienced user. I appreciate you taking the time to look at this and help me. My server recently has been shutting itself down seemingly every 11-14 hours. Most recently, it will crash while trying to transcode a fairly innocuous video through Plex. A while back, I remuxed a copy of Godzilla Minus One. This file was very large, over 60gb if I recall correctly, and my server was having trouble transcoding it and giving an error that there wasn't enough space on the disk (which there was). I did some looking about, and I had read that instead of having my transcode folder be saved to RAM that it should instead be saved on my Cache (which is an SSD). I made the switch, and the video was able to play just fine. I had assumed that my 32gb of RAM just wasn't enough to hold the transcode, and the 500gb SSD made it possible. Prior to this, I had never had a parity drive. I finally got one, hooked it up, and started the parity check. However, the server kept crashing in the middle of it. I could only get a few hours into the parity check before the system would have an unclean shutdown. I finally decided to postpone the parity check and instead left the disk unmounted on the next reboot, with the intention of coming here and seeking a solution. However, the unclean shutdowns continued and it's gotten to the point that it shuts down while trying to transcode a very lightweight file. Please let me know if I can provide any further information to help you in your troubleshooting. syslog-previous syslog pheonix-diagnostics-20240626-1511.zip