Hi,

 

My monthly scheduled parity check is running now:

 

 

My previous check was actually just a week ago due to adding another parity drive. It went without problems. With this extreme number I cant really see this being due to drive issues? Disk statistics were cleared after about 500GB of the parity check, and these are the current stats:

 

It feels pretty pointless to complete this check now, would you agree? Thinking I should just cancel it and run short SMART tests and file system checks on all drives. If that comes back without errors I'd run memtest. 

 

Any other ideas? Could this simply be misreporting in the UI? 

 

Edit: Removed diagnostics as I dont like it being stored

Edited October 5, 20178 yr by Fredrick

2 hours ago, Fredrick said:

With this extreme number I cant really see this being due to drive issues?

 

No, those are actual sync errors, on the 1st parity disk, parity2 is in sync, on September 29th you did a new config, changed your parity disk and selected "parity is already valid" before starting the array, so parity is not synced.

 

Since parity1 is completely out of sync it's much faster to resync than to correct the errors, unassign parity, start array, stop array, re-assign parity, start array to begin sync, you'll remain protected by parity2.

Well, I passed 0,7B errors before you came and saved the day again, @johnnie.black

 

I must have misunderstood how new config/"parity is valid" works as I thought it was the right thing to do.

 

Thanks again!