Jump to content

Parity Check always returns 5 errors


Recommended Posts

Hi,

 

Since about 3/4 months every time my monthly Parity-Check runs it returns exactly 5 errors. I have parity corrections enabled so I don't think they should be the same errors (though i have no idea how to check that) but it still seems like an odd coincidence.

I never had a problem with parity check before which always returned 0 errors for over a year priori to that.

 

Not sure how to diagnose the potential problem or if i should even be worried about it.

 

System diagnostics are below.

unraid-diagnostics-20240601-0941.zip

Link to comment
18 hours ago, Ceco said:

Is this something that can be safely ignored or is there something i can/should do about it ?

Depends. If the errors are always in the same addresses, and those addresses aren't critical to any of the files or filesystems, then you can ignore them.

If not, then you need to replace parts until the parity check is always clean.

 

Another consideration is normalizing parity errors. Typically you would alert on any parity errors, currently you have to examine the logs every time to see if all the errors are "expected" or you have new ones which need attention.

 

Personally I wouldn't feel comfortable running like that.

Link to comment
19 minutes ago, JonathanM said:

If the errors are always in the same addresses, and those addresses aren't critical to any of the files or filesystems, then you can ignore them.

Pardon the noob question but how can i check that ? I might not be looking in the right place but i can't find anything in the documenation for the parity or diagnostics tool explaining how to read logs or get more information about the parity errors. Not even sure what log i should be reading...

 

I went for a SATA Card with the Asmedia chip cause many users reported it running well in Unraid. Looking back, the start of the errors do coincide with the card's installation so is this kind of errors commonplace with such cards or could i possibly have a faulty one ?

Link to comment

Parity error addresses are in the syslog, but there is no easy way to correlate them to files or what they might corrupt. Determining whether you can safely ignore them is a very technical process, I gave the 10,000ft overview. If you aren't comfortable with that explanation, no, you can't safely ignore them.

 

It's not the Asmedia chip that seems to be the issue, more the implementation on the specific model of card. I would start by replacing the card with a different brand version of the same chip.

Link to comment

That's a bummer, I specifically went for a SilverStone card hoping it would be more reliable than generic alternatives as it had positive feedback.

Anyway, i'll find a cheap replacement card and see what happens.

 

Thanks for the help.

Link to comment
33 minutes ago, Ceco said:

That's a bummer, I specifically went for a SilverStone card hoping it would be more reliable than generic alternatives as it had positive feedback.

Anyway, i'll find a cheap replacement card and see what happens.

 

Thanks for the help.

Have you checked to see if there is an update available for the card? IIRC silverstone is one of the few vendors that offer updated firmware for their cards.

Link to comment

They do ! Unfortunately I already updated the firmware when i received the card and checking their website there hasn't been an update, so it doesn't look like this will be my solution.

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...