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 Check Sync Errors Corrected 13624

Featured Replies

Hello,

I am running Unraid 6.8.0 and i havent done a parity check in a long time. I have dual parity drives.

I ran a parity check and i got Sync Errors Corrected: 13624.

I had 1 drive in my array with a few bad sectors.

So does this mean that my parity will also be corrupt?

Will my other data on other disks get corrupted?

Or does this mean that parity fixed the data on the drive that was not readable due to bad sectors?

Thanks for the help. 

  • Community Expert

Please post the diagnostics: Tools -> Diagnostics

  • Community Expert
Apr 17 16:28:45 Tower emhttpd: unclean shutdown detected

 

A few sync errors are normal, even expected, after an unclean shutdown.

 

  • Author

Do you think that i should replace the disk with bad sectors?

Also just for my understanding, when parity checking fixes errors is it changing data in the parity drives or the data drives?

Also is it possible the parity checking with fixed errors can cause data to be corrupted?

  • Community Expert

These sync errors are unrelated to a disk problem.

 

Do you think that i should replace the disk with bad sectors?

Which disk is it? You have too many for me to look at all SMART reports.

 

Also just for my understanding, when parity checking fixes errors is it changing data in the parity drives or the data drives?

Sync errors are always corrected on parity, never on data drives.

 

Also is it possible the parity checking with fixed errors can cause data to be corrupted?

No, it is possible is some rare cases to corrupt parity if there are read errors on a disk during a correcting check, hence why it's recommended that parity checks should always be non correct unless errors are expected, like after an unclean shutdown.

 

 

  • Author

Disk number 14

 

Thanks for the help

  • Community Expert

Looks mostly fine, there a single Reported_Uncorrect error, unless it keeps increasing it's fine, but you should run regular parity checks, once a month is usually the recommendation, it will catch any issues since it does a complete surface scan on all disks, basically same as an extended SMART test.

  • Author

Ok, Thanks

  • 1 year later...

I have SYNC ERRORS CORRECTED 1096 and i now it is corrupted data because sum of my files (db) are malformed is there a way to now which files are corrupted?

tower-diagnostics-20211127-1151.zip

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

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.