Hello everyone

 

Logged onto unraid today and saw an error message, parity disabled.  So I took a diagnostic and shut down unraid.

 

I add the diagnostics here. Disregard the error messages for the UPS, its disconnected but I have not updated unraid.

 

What to do now? Start up the raid again ? Or boot in safety mode?

 

I am not tech savy so hoping someone can help with fairly detailed descriptions....

 

I did a parity check a few weeks ago, showed no errors. And have not had disc error messages either.

 

Very thankful for any help.

 

Kind regards, Kjetil

 

 

federalreserve-diagnostics-20230628-1043.zip

Edited June 28, 20233 yr by Kjetil

Both disks look healthy and dropped at the same time, so most likely a power/connection issue, do they share something in common, like a splitter?

Not sure actually. Should I restart Unraid and check if all is ok ?

I would at least check/replace cables and then re-sync parity

Don't have any cables, so would need to order in. But I can do it. 

 

Do I boot as normal, and start the unraid? How do I do the re-sync?

 

https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself

 

You can do both at the same time.

So I remove the two parity discs by choosing "no device", then start and stop the array, then reassign the two discs, and start the array again in maintenance mode (choosing sync to rebuild) ?

Yes, but no need to do it maintenance mode, or the array will not be available during the sync.

 

 

Rebuilt parity, so now it's working. Thanks for your help JorgeB 😊

After using the server a few weeks, it suddenly fell out of the network. It was still on but not responding, also there was no picture when connecting a screen directly to the server vga output. Had to do a forced power off. And power on again. Now it's working again and online. I added the diagnostics here, are you able to see anything from the diagnostics? Error message etc ?

federalreserve-diagnostics-20230719-2055.zip

And now it happened for a 2nd time in just 1 hour... must be some hardware fault... mainboard?

Not sure how to find the fault...

That looks more like a hardware issue but you can enable the syslog server and post that after a crash.