Hi guys,

maybe somebody has an idea what to do...

 

First the parity check had a slim 180k corrections at ~60% and now it has completely stopped a few hours in giving me a read error

The system and disks are almost virgin

 

A bit of background: I've been letting the server gather dust for a year, then finally got around to it a month ago and wanted to start using it productively. At that time, a parity check was running without any errors, but when I rebooted the system recently, the array was somehow disabled, but it was running again, I have no idea what I did there.

This morning at 00:00 I started the parity check via schedule, but a file transfer from PC to disk was still running, it didn't like that, it detected many errors. So I stopped the check and waited for the transfer to finish, then I restarted the check, at first there were no errors, but then there were more and more corrections. Resulting in an auto disable when the read error occured

Edited January 3, 20251 yr by cottec

Please post the diagnostics.

oh sorry, forgot it....

there's two, one while the parity check ran an one after the error

 

I'd start by checking the wiring, is there any log or whatever that might be deleted on shutdown?

 

 

 

unramsch-diagnostics-20250103-0108.zip unramsch-diagnostics-20250103-1536.zip

Edited January 3, 20251 yr by cottec

There are constant ata errors with parity and disk1, looks more like a cable/connection problem, do they share a power splitter or similar?

yes, they are both plugged into the mainboards sata power supply using a Y splitter.

But i hotglued that thing in as it was quite loose

Edited January 5, 20251 yr by cottec

Try again, if issues persist replace the splitter.

Yeah, that might be necessary then. 

 

Very strange....

 

I cleared both disks now, no issues during the pre read, clear and post read. wasn't a productive system anyways, so all is fine for the moment. 

Thanks! 

 

My mistake was overlooking the checked checkbox to correct parity issues during manual parity check. That killed my parity + I had no confidence in the data stored on the data disk due to the read errors.