Parity check finished (6984804 errors)


J05u

Recommended Posts

Some sync errors are normal after an unclean shutdown, though with so many it is only normal if happened the middle of writing to the array.

 

Jan 12 11:26:55 Fortress emhttpd: unclean shutdown detected

 

Still, run a correcting check and in a couple of days run a non correcting one, except after an unclean shutdown the only acceptable number of sync errors is 0.

Link to comment
30 minutes ago, johnnie.black said:

Some sync errors are normal after an unclean shutdown, though with so many it is only normal if happened the middle of writing to the array.

 


Jan 12 11:26:55 Fortress emhttpd: unclean shutdown detected

 

Still, run a correcting check and in a couple of days run a non correcting one, except after an unclean shutdown the only acceptable number of sync errors is 0.

Thanks, i will run this one now. Its parity check with Write corrections to parity ticked. right?

I am just wondering can this be because one of drives has Reallocated_Sector_Ct 116 (HGST one, pulled from old NAS)

Link to comment
8 minutes ago, J05u said:

Its parity check with Write corrections to parity ticked. right?

Yes, but you need to start it manually, auto parity check after an unclean shutdown is non correct.

 

8 minutes ago, J05u said:

am just wondering can this be because one of drives has Reallocated_Sector_Ct 116 (HGST one, pulled from old NAS)

Possible, but not the most likely culprit.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.