Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Parity Errors 500+

Featured Replies

I seem to be having issues with errors when i do a Parity check,   I had a couple issues with unraid crashing and had to do a hard shutdown, So i get there could be errors but i have done the party check 3 times with corrections turned on but still high errors.

 

I only have plex docker running i have switched everything else of so i am running out of ideas.  Any help would be great.

 

Should i just stop the array and format the parity drives ( if this can be done)

 

Thanks

 

Mat

unraid-diagnostics-20210310-0823.zip

  • Community Expert

Start by running memtest.

Which drive(s) is/are the read errors on? I only see a few that are drive level (on disk 2 and 4), which makes me think you may have a bad cable and/or card if they're occurring continually. Try reseating your card and if you have spare cables for drives 2 and 4, replacing those and running parity again.

 

Also you may want to run it without corrections first; opinions vary on that, and realistically since you've run it a few time with it checked it makes little sense to bother now, but in future, so if it is just a bad cable or something similar, you aren't altering parity. Personally I run my monthly checks without, that way if there are errors I can determine the cause and run again before writing corrections.

  • Author
15 minutes ago, JorgeB said:

Start by running memtest.

24 hours of being off.  yay! lol

 

I did add 32gb ram and a GPU but i had issues with VM's but maybe a memory issue.  (Good Shout)

  • Author
11 minutes ago, greyday said:

Which drive(s) is/are the read errors on? I only see a few that are drive level (on disk 2 and 4), which makes me think you may have a bad cable and/or card if they're occurring continually. Try reseating your card and if you have spare cables for drives 2 and 4, replacing those and running parity again.

 

Also you may want to run it without corrections first; opinions vary on that, and realistically since you've run it a few time with it checked it makes little sense to bother now, but in future, so if it is just a bad cable or something similar, you aren't altering parity. Personally I run my monthly checks without, that way if there are errors I can determine the cause and run again before writing corrections.

 

Ok i will take card out and put back in too.

 

I didn't know any of the drives had issues as the gui is not reporting anything.

 

I do also run Parity checks on a monthly basis but where i had to button it a couple times

1 minute ago, Mat1987 said:

 

Ok i will take card out and put back in too.

 

I didn't know any of the drives had issues as the gui is not reporting anything.

 

I do also run Parity checks on a monthly basis but where i had to button it a couple times

The SMART reports in your zip file show a small number of read errors. Not enough to worry about IMO unless you keep getting them on those drives.

  • Author
1 minute ago, greyday said:

The SMART reports in your zip file show a small number of read errors. Not enough to worry about IMO unless you keep getting them on those drives.

image.thumb.png.9c418f3578c4292d46ff0c7a2f1837fe.png 

 

This is the GUI annoying it doesn't say any errors lol.

25 minutes ago, Mat1987 said:

image.thumb.png.9c418f3578c4292d46ff0c7a2f1837fe.png 

 

This is the GUI annoying it doesn't say any errors lol.

SMART reports cover the history of the drive; the UnRAID gui errors are reset when the array is rebooted.

(also UnRAID read errors aren't often on the drive level, so any read errors on the drive are usually lower)

Edited by greyday

  • Author
6 minutes ago, greyday said:

SMART reports cover the history of the drive; the UnRAID gui errors are reset when the array is rebooted.

(also UnRAID read errors aren't often on the drive level, so any read errors on the drive are usually lower)

Ok good to know.  I will do a memory test and check all connections.

  • Author

Does a memory test last 24 hours or can you do say 12?

 

Mat

 

18 minutes ago, Mat1987 said:

Does a memory test last 24 hours or can you do say 12?

 

Mat

 

 

I have 128gb of RAM and memtest takes about 12 hours per pass.

  • Author
14 minutes ago, greyday said:

 

I have 128gb of RAM and memtest takes about 12 hours per pass.

ok cool i have 64gb so should be ok.

 

Thanks

 

Mat

  • Author

when i run the mem test it just says Loading /memtest.... ok 

 

Is this normal or should i see more lol

  • Community Expert

Make sure you're booting using legacy BIOS/CSM, memtest doesn't support UEFI boot.

  • Author
14 minutes ago, JorgeB said:

Make sure you're booting using legacy BIOS/CSM, memtest doesn't support UEFI boot.

My bios has UEFI or legacy and UEFI which is on but still hags :/

  • Author

ok downloaded mem test and put on separate memory stick so its running lets see what happens.

  • Author

Any other ideas if the memory comes back fine?

  • Author

so first memory test is fine.  now to do the 64gb all together.

  • Author

Low and behold i got an error within 20 minutes with 64gb ram in.  I am now testing the 32gb ram i got the other day on its own.  Hopefully in a way it errors so i can send it back.

 

Mat

  • Author

Just an update.  Tested both 2 x 16gb on there own no issue..  Had a friend of mine said to increase voltage on memory.

 

WIll test again tomorrow see if i get the issue then up the voltage and try again.

 

Fingers crossed.

  • Author

So i found out that the new memory that was sent was a different speed and because i was using XMP i think that why i was getting memory issues.

 

After setting voltage to 1.35 and memory speed to the lower 2666 seem to have no issues there.

 

However when i did a parity check with corrects i still got 400 errors.  When i ran it with no corrections it  reported no errors :/


Any ideas?

  • Community Expert

It's normal for the first check after the issue is fixed to still find errors, next ones should not find any.

  • Author

i know but i ran a few times.  Ill see what happens when it runs at the end of the month

  • Community Expert
2 minutes ago, Mat1987 said:

i know but i ran a few times.

 

5 minutes ago, Mat1987 said:

However when i did a parity check with corrects i still got 400 errors.  When i ran it with no corrections it  reported no errors :/

Which is it?

  • Author
2 minutes ago, JorgeB said:

 

Which is it?

The beginning i ran the corrections about 4 times and still got errors. Now i seem to have fixed memory issue so maybe that will sort it.

 

If honest lost count the amount of parity checks i did. was loads and lots of time.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.