Earlier this week, I woke up to find that my server had crashed during the night and was completely unresponsive. Not having time due to work, I simply restarted the machine and headed out for the day.

Server was fine for the day, but crashed again that night, only to be noticed the next morning. I shut it down and decided to look into it this weekend. Yesterday, since it hadn't been done in a while and I noticed the fans were spinning pretty high earlier in the week, I opened the case up and carefully blew out any dust buildup in the machine.

Upon restarting, the system came up with no issues, other than wanting to run a parity check. Having too much planned for the day, I left it to do it's parity check and went about my business. It crashed again last night.

I'm again sitting in a place where my fans are pegged at 100%, I can't access the web interface, and I can't ssh into the machine, so I can't pull any diagnostics to see what the hell happened.

Enable the syslog server so that logs will be retained after unraid goes unresponsive.

Also I would still post diagnostics after a reboot to see if anything abnormal is being logged early on.

Edited 2 hours ago2 hr by MowMdown

Well, I looked just now after a restart, and it seems that I did have syslog server set up. I'll take a look and see if I can figure anything out and report back if I'm too dumb to understand.

I'm lost, any chance someone can help me see what might be wrong here?

phreeq-unraid-diagnostics-20260913-1343.zip