After a power blink, my system was unresponsive (UI unreachable) and I had to force shutdown pressing power button. When it got back online, parity check began but after some hours I got some warnings in discord:

 

 

Parity check is now paused in 20.7% and I don't know what I have to do to gracefully restore parity errors and get everything back online. I still can't afford a UPS, unfortunately. So Murphy law applies to me a lot.

 

Diagnostics attached.

tower-diagnostics-20240911-2355.zip

Edited September 12, 20241 yr by lelejau

I stopped the array, unassigned parity disk. Started the array. Stopped the array again. Assigned parity disk. Started array in maintenance mode. Start sync parity. My log is flooded with weird errors:

tower-syslog-20240912-0424.zip

 

Changed sata cables to another port on motherboard but didn't work. It starts the syncing, after a couple of seconds, same errors again and syncing starts to become slow and then stops.

 

Is my motherboard bad because of the power outage ?

Edited September 12, 20241 yr by lelejau

Looks more like a power/connection issue, replace/swap both power and SATA cables and try again.

Parity-sync finished now with no errors. It seems like it fixed itself regarding those SATA errors. I wonder why I got the read check error in the first place that caused all this trouble? is that possible to know?

 

UPS top 1 priority now. Can't be bothered by this again lol

 

Meanwhile I'm setting some settings in parity check tuning:

 

 

Should I enable "write corrections to parity disk"? Seems good idea?

We typically recommend always running a non correcting check unless sync errors are expected.