Parity check consistant error count.


27 posts in this topic Last Reply

Recommended Posts

Does anyone know how i can identify the drive causing the parity check errors? i get 5 every time. Is there a way to make Unraid remember the values on each disk at these error spots and then after a another parity check compare to see what drive is changing these spots? and have ability rerun at these spots to see if its fixed? i have 11 drivers many different sizes maybe i can get a notification when error happens so i can at least narrow it down if it gets passed some smaller drives without errors.

 

or am i limited to having to take a drive out one at a time with a new one rebuild the data and then check with a party check that takes like 20hours? each time?
 

Edited by EMKO
Link to post
25 minutes ago, EMKO said:

i get 5 every time.

Are you doing a correcting parity check?

 

But, other than that Marvel based controllers will on (depending upon the drives which are installed) consistently cause 5 errors every time a parity check is done.  Marvel is not a recommended controller for this and other reasons.

Link to post
  • 1 month later...

I used to use a SASLP-MV8 in my array, for about 7 years.  I would occasionally get 5 parity errors as you have done.  I replaced that controller with an LSI SAS2008 (PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) ) and have had good service from it.  However, just yesterday I had a parity check complete, and I have 5 errors. 

 

Since this pattern has been related to the SAS controller, does anyone think I have something to worry about with this one?  I think I will run a second parity check.  In the past, when I did this, the same 5 errors would show up, and a third check would show no errors, as if they had been corrected.

 

Any ideas?

Link to post
5 minutes ago, PeteAron said:

However, just yesterday I had a parity check complete, and I have 5 errors. 

If it is the first time with the LSI it's likely not controller related, still important to try and find the cause, any unclean shutdowns?

Link to post

No, Jorge, It has been fine.  The one unusual issue i have had is an st800dm drive has been throwing crc errors- enough that i am going to return it.  I dont see others, so i assumed that isnt the issue.  

 

How do i find where the errors are?  Maybe its time to replace my 2 year old sas to sata cables?

Link to post

Well I am running a second parity check and, as expected, I see these 5 errors again.  Hopefully this means they are corrected; but is it possible they are scrambled?  I am writing corrections to parity; I dislike doing this because eventually I need to replace a disk, and i worry about the potential for these errors to corrupt my rebuild.

 

Is it possible this is a memory-related error?  I will replace my sas-sata breakout cables this weekend and run a third parity check.  Any input here is welcome.

Link to post
10 hours ago, PeteAron said:

I see these 5 errors again.  Hopefully this means they are corrected

If the first check was non correct this is expected.

Link to post

Update.  Last night i replaced both breakout cables from my LSI card to the disks, and started a new parity check.  I have the same 5 errors again. 

I am attaching a diagnostic in case anyone can identify something to help track down the issue.  I have the option of swapping hardware but obviously would not like to do that.

 

thanks for your help.

repository-diagnostics-20210413-2252.zip

Link to post
19 hours ago, PeteAron said:

No, both checks were correcting. 

Diags posted show first a non correcting check, then a correcting one, so errors on the 2nd check were expected.

Link to post

Jorge, sorry, I wasnt clear.  That log is from right before shutting down last night to replace the breakout cables.  I restarted and began a parity check - which is not in that diagnostic.  The currently running parity check again shows 5 errors, so they are being corrected a second time.  I will upload another diagnostic tonight when the check finishes. 

Link to post
3 minutes ago, PeteAron said:

The currently running parity check again shows 5 errors

Are they the same 5 blocks? You're still using a Marvell controller for one disk, can you connect it to a different one?

Link to post

OK that answer was incomplete...Im slow.  This is a supermicro C7P67 with 6 onboard SATA controllers, and I have an LSI SAS2008 for 8 more.  All 8 of the LSI ports are used, and 5 of the onboard.  I see in the log where it says I have scsi host1 and scsi host 2 using Marvell - these must be on the motherboard, right?  how can i change that?  Why would only two have marvell controllers?

Link to post

Ah, yes, you are right - not enough coffee.  I will try that tonight.  

 

Is there no way to replace that marvell controller?  I suppose i need to avoid both of those, limiting my array to 12 disks?

Link to post
28 minutes ago, PeteAron said:

Is it possible to use my cache drive on the marvell controller without issue? 

Difficult to say for sure, Marvell controllers in general should be avoided with Unraid, though some are not so bad as others.

Link to post

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.