Having some weird behavior on my server since early this morning. Last night at some point my server rebooted and when it came back up both parity drives showed as disabled.

 

I stopped my array, unassigned the parities, started my array, stopped again, re-assigned them, started array and let the parity check get going.

 

After 5% was complete I noticed the GUI went unresponsive and my terminal window connected to my server was giving some funky errors. Luckily I was able to use "parity.check Pause" and then "powerdown -r" successfully. When the server came back up and I logged in it said my flash drive was corrupt. I don't think that's especially likely since I just replaced my flash drive a few months ago but fine, I downloaded a backup and then powered down and changed the USB port just in case that would help. Powered back up, started the array, and the name of the server had reset to "Tower" but all other prefs are unchanged, array assignments still intact, parity check progress is even remembered. No error about the flash drive either. I changed the name back and started the array back up. I am jumpy now that something is wrong. Attaching diags to see if anyone could take a look and see if there is stuff indicative of issues. I've also got logs from the flash drive from the reboots I've done this morning

sydneycarton-diagnostics-20250407-1121.zip sydneycarton-diagnostics-20250407-1020.zip sydneycarton-diagnostics-20250407-1115.zip

52 minutes ago, MyNameWasTaken said:

GUI went unresponsive

Lots of ethernet adapter problems in that first syslog

I just got this ehternet card a few months back because the port on my mobo died. I felt like maybe those errors were a result of the OS not recognizing it correctly during some kind of panic it was having? Idk

There are 2 intel ethernet controllers and that is what was logging errors. I assume these are on the motherboard, they don't seem to be plugged in.

 

There is also a realtek 8125, is that the one you added? There is a driver plugin for that one.

Yes the realtek is being used, the onboard intel was giving the errors and causing me to lose connection all the time

8 minutes ago, MyNameWasTaken said:

the realtek is being used

2 hours ago, trurl said:

There is a driver plugin for that one.

On the Apps page

 

Rebooted again this morning halfway through parity check and now one of the parity drives went to disabled status

sydneycarton-diagnostics-20250408-0555.zip

1 hour ago, MyNameWasTaken said:

Rebooted again this morning halfway through parity check

Technically, this was a parity sync, not a parity check. Do you mean it rebooted itself?

 

Is your server on an UPS? Is your BIOS set to boot on power restored?

50 minutes ago, trurl said:

Technically, this was a parity sync, not a parity check. Do you mean it rebooted itself?

 

Is your server on an UPS? Is your BIOS set to boot on power restored?

It is on a UPS and BIOS is not set to power on after a power restore. The server rebooted itself. 

Rebooting itself isn't something computers normally do. Crashing and becoming unresponsive until you manually reboot is typical.

 

Unraid might crash and become unresponsive, but it won't reboot itself, though it would be possible to have something run the reboot command.

 

Maybe something about the reset or power switch or its connectors on the motherboard?

So just to clarify you’re thinking it’s something up with the mobo that results in unraid going unresponsive and ultimately the pc is rebooting because of it? Not one of the drives?

No, I'm thinking something with the mobo is rebooting, not related to Unraid. If it was just Unraid unresponsive, it would just sit there until you rebooted.