Jump to content

5 errors during parity check... not sure how to resolve..need help


Recommended Posts

I think this is due to an unclean shut down when we lost power; but im unsure how to proceed form here and what further checks i need to do or if i need to replace a disk.   I have very limited knowledge on how to resolve errors in unraid with regard to the array or how to interpret the results...... any help would be appreciated.  I have ran a parity check twice... each time it did the same thing...5 errors.   The array is still running and the disks appear to be operating normal; but the 5 errors makes me nervous as am thinking something is wrong somewhere.  

WDC_WD60EFRX-68L0BN1_WD-WX11D668XTNN-20220620-0739 disk3 (sdd).txt WDC_WD60EFRX-68L0BN1_WD-WXL1H1621Z29-20220620-0739 disk2 (sdb).txt WDC_WD100EMAZ-00WJTA0_JEHYGH9N-20220620-0739 disk1 (sde).txt WDC_WD100EMAZ-00WJTA0_JEJE7U6N-20220620-0739 parity (sdf).txt syslog.txt main-diagnostics-20220620-0739.zip

Link to comment

thanks for your reply.  My settings show write corrections to parity and still get the 5 errors... not sure if i unwisely should of not of set this box to write corrections to parity  as its default...can i run a non corecting parity check then a correcting parity check .... or perhaps i need to do something else?

Screenshot 2022-06-20 at 08-42-40 main_Main.png

Screenshot 2022-06-20 at 08-49-52 main_Main.png

Edited by dsharp9000
add file
Link to comment

im going to run a non correcting parity check just to be on the safe side..... should i keep this set at non correcting from now on?... Also, if i run a correcting check "after" the non correcting check will the 5 errors still show up in the correcting parity check?... im just curious if the errors will always be there everytime i run a future correcting parity check "if needed"..... its just a bit confusing to me; please forgive my lack of knowledge regarding this.   I appreciate the help on this.

Link to comment

The scheduled check should be non-correcting as you do not want a dtive that is playing up potentially corrupting parity.   Normally you only run correcting checks when you are reasonably certain you have no outstanding hardware issues.

 

Once you have run a correcting checks then subsequent checks (of either type) should show 0 errors.   You then want to keep a watch on the server to see if you ever get any parity check reporting a non-zero value when not expected.

 

 

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.

×
×
  • Create New...