Monthly parity check found 5 errors


Recommended Posts

After the scheduled monthly parity check i discovered 5 errors reported.

Looking at the log, here is what I saw:

Feb  1 03:23:12 UNRAID kernel: md: parity incorrect, sector=1565565768 (Errors)

Feb  1 03:23:12 UNRAID kernel: md: parity incorrect, sector=1565565776 (Errors)

Feb  1 03:23:12 UNRAID kernel: md: parity incorrect, sector=1565565784 (Errors)

Feb  1 03:23:12 UNRAID kernel: md: parity incorrect, sector=1565565792 (Errors)

Feb  1 03:23:12 UNRAID kernel: md: parity incorrect, sector=1565565800 (Errors)

On the other hand looking at the main screen I can see the parity is valid.

Please see the screenshot of it.

I would like to ask what does it mean? Probably the parity was incorrect and then corrected or the errors still remain.

What I should do? To run a new (correcting) parity or?

 

Thank you in advance.

p.s. Log file attached as well

Screen_Shot_2014-02-01_at_11_30.49_AM.jpg.5e5f85f1c5eee0d29e93dc2d5007ca56.jpg

syslog-2014-02-01.txt

Link to comment

Thanks dgaschk.

No pending sectors discovered after short smart test.

I am currently running a correcting parity check. Unmenu reports that 5 sync errors have been corrected.

Will wait for it to finish and will run non-correct parity check to be 100% sure parity was corrected and will report back later the results here.

BR.

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.