Hello,

My Unraid server is rebooting by itself about 10-15 mins into the Parity Check.

I recently had an issue with where some of my drives were throwing codes and were being disabled. The forum helped me out to solve this. The old post is: https://forums.unraid.net/topic/192547-help-needed-accidentally-used-new-config-with-a-failed-drive/

Since I got my server up and running again, 3 of the drives were disabled again so I rechecked the cables to make sure everything is seated correctly. I noticed that a plastic screw holding the heatsink on my LSI HBA had snapped off. I rigged up a temp zip tie fix and booted up again.

Upon rebooting, I got the unclean shutdown message so I decided to complete a Parity Check. 10-15 mins into this, the server randomly reboots. Several times, I opened up the server and reconnected different components, but to no avail. Before I go and start replacing components, is there something in the logs that can tell me what's wrong? Logs attached.

I was thinking about starting with the HBA.

Thanks

leungunraid-diagnostics-20250819-1722.zip

Edited August 20, 2025Aug 20 by UnraidRog
Changed Title

Unfortunately after a crash there is nothing useful logged as the syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to the problem. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field and log to a share instead.

One other thing that occurs to me - have you checked there is no power related issue. A Parity Check is one time the system has all drives active so can be under maximum power draw. There can also be power cabling issues to the drives themselves - particularly if you use Power Splitters to get the required number of connectors.

7 hours ago, UnraidRog said:

My Unraid server is rebooting by itself

This is almost always a hardware issue, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM, PSU would also be a good suspect.

On 8/20/2025 at 12:51 AM, itimpi said:

Unfortunately after a crash there is nothing useful logged as the syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to the problem. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field and log to a share instead.

One other thing that occurs to me - have you checked there is no power related issue. A Parity Check is one time the system has all drives active so can be under maximum power draw. There can also be power cabling issues to the drives themselves - particularly if you use Power Splitters to get the required number of connectors.

Thanks - I’ll try the mirror to flash drive option. I don’t mind the additional wear on the flash drive for now.

I don’t think it’s the PSU unless it’s going out. I actually have one less drive HDD now than before. Hopefully the syslog server can tell me something.

On 8/20/2025 at 1:03 AM, JorgeB said:

This is almost always a hardware issue, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM, PSU would also be a good suspect.

Sounds good. I’ll start troubleshooting one hardware at a time to see if I can narrow it down.

Just wondering, can a bad HBA controller trigger a reset? I ordered a new one that ‘s coming on Monday. The heatsink on the old one was disconnected. I wonder if the chipset was damaged before I discovered that the heatsink came off.

10 hours ago, UnraidRog said:

Just wondering, can a bad HBA controller trigger a reset?

It can, but it would not be my first suspect.

On 8/24/2025 at 12:27 AM, JorgeB said:

It can, but it would not be my first suspect.

Got it. I have a spare PSU somewhere. I'll look for that. Thanks everyone

I'm starting to swap out different parts to get to what's causing this.

I noticed something strange. The Parity Check will always stop at the 17min mark and NAS will reset.

Does that help narrow down what's causing the crashes?

Not really, but it's rather strange if it's always at the same mark, this is typically a more random issue.

I was wrong... it stopped crashing at the 17 min mark.

I've attached a couple Syslog's. One is with the Dockers turned on and the other is with the Dockers turned off.

I'm going to try replacing the PSU next. Should I also do a memtest to rule out the RAM?

Thanks again

syslog-previous 08.26.2025 12.28.txt syslog-previous 08.26.2025 12.39.txt

PS I have 4 sticks of 16GB RAM. I tested 2 at a time but that didn't isolate the problem. Unless I had terrible luck and had more than 2 sticks of RAM go bad on me.

10 hours ago, UnraidRog said:

I tested 2 at a time but that didn't isolate the problem

That suggests the RAM is not the problem; the PSU, board, CPU would be my next suspects, in this order.