Hi all,

 

I am hoping that someone might be able to help me with this every frustrating issue. 

 

For around a month now, I have noticed that when I get home from work, and log in to the dashboard, my server is running a Parity Check. Every day - and the uptime shows just 14 hours (ish).

 

I've since realised that the server has started doing hard resets early in the morning, Sometimes just a single rest, sometimes a few in succession: 02:30, 03:15, 04:30, etc. It always seems to be that these resets stop around 04:00-04:30, and the server stays up until the next morning. 

 

This happens every morning, without fail. It's always a reset, and the server turns back on, acts as if everything is fine, and begins a Parity Check. Usually just to be cut short again when the server decides to do another hard reset - but then magically decides it doesn't need to do any more resets after about 04:30 and remains stable until the next morning, when the process starts again. 

 

Prior to this issue starting, I had not made any hardware changes, and the server had been running for months on end without incident. I've had almost a year straight of uptime at one point, until I had to move it to another room so powered the server down and lost my streak. 

 

Also, no major software changes over this time. Maybe a couple of plugin updates for Community Apps, etc. and a couple of Docker updates for Plex, etc. - but I hadn't made any Unraid OS updates over this time.

 

So far, I have powered down the server to give it a good clean (but there was not much dust at all), I have turned off my scheduled daily SSD Trim and Mover functions, and finally I have updated Unraid OS to 6.12.0-rc2 just to see if that alleviated any issues - but it has made to change.

 

Right now, I don't know where to go next with trying to fix this issue. 

 

I am hoping one of you fine people can offer some assistance, and I attach my diagnostics logs in the hope that will help.

plot49-diagnostics-20230323-1644.zip

Enable the syslog server and post that after a crash, but if it's a hardware problem most likely it won't log anything of interest.