500k+ Parity errros

[Jaster]

Hi Guys,

 

After a relocation of my server I had some issues with the hard drives, but having two parties with only seven drives seems to have covered most of it.

I had disks dropping out, but could reassign them after fixing some minor hardware issues (lose cable, etc) and had to xfs_repair a drive.

Now I'm running a parity check and it has over 500k corrected errors. Might there be some corrupted/lost data? I attached diagnostics and extended SMART checks for the two dropping drives.

knowlage-smart-20200718-0946.zip knowlage-smart-20200718-0945.zip knowlage-diagnostics-20200718-2019.zip

[JorgeB]

13 hours ago, Jaster said:

Might there be some corrupted/lost data?

Impossible to know without the previous diags showing everything what happened before the check, you did do a new config, so some (or a lot) of sync errors can happen, depending on the array status before.

[Jaster]

the status array before was fine, literally just completed a parity check.

 

[JorgeB]

So why the new config?

[Jaster]

disk dropped out
 

[JorgeB]

Sop this wasn't correct:

42 minutes ago, Jaster said:

the status array before was fine

And again:

1 hour ago, johnnie.black said:

Impossible to know without the previous diags showing everything what happened before the check,

 

[Jaster]

Parity completes -> Array fine -> No operation or what so ever -> disk drops -> new config -> xfs_repair -> parity check.

Disk dropped due to a damaged cable.

[JorgeB]

That alone doesn't explain 500K sync errors, a few errors yes, but not that much, something is missing.

[Jaster]

All I got - that's why I'm asking. From previous situation I can't remember ever having that many sync errors.

[JorgeB]

So many errors could be explained for example by writing to the emulated disk once it got disabled before doing the new config, there could be other explanations, but again would need the previous diags,