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-Sync finished (6779 errors)

Featured Replies

Just did a parity disk upgrade from a 22TB to a 28TB. Followed the procedure of swapping it out and left it to run. It took over 2 days to complete but I found that one disk has been throwing up errors. I believe this could be a data cable issue and I will try to re seat the cables and check.

Now, I was gonna use the ex parity 22TB and swap it out with a much smaller array HDD but is it safe to do so now? Do I now have to re run the parity check all over again before doing any array HDD swaps?

Is there a way to check if these errors will show up before running a parity check in the future? As I think taking the rail out of the enclose (I have an N1) may have disturbed the data cable.

By the description, the errors were reported by a data disk during the sync. Unraid could not read those sectors, so parity was not calculated correctly for them. Until that is fixed, the new parity cannot be fully trusted, so don't do any data disk replacement yet. A rebuild now could be corrupt in the areas that failed to read.

For the same reason, leave the old 22TB parity disk untouched for now, don't reuse it or clear it. It is your fallback until the new parity is confirmed good.

Please post the diagnostics (Tools > Diagnostics), ideally before rebooting, so we can see the actual errors in the syslog. They will also show the disk's SMART report, which tells us if this is a cable problem (UDMA CRC errors) or a disk problem (pending or reallocated sectors).

If it turns out to be a connection issue, reseat or replace the cable, then run a correcting parity check. It should finish without any errors on the disks. Only after that is it safe to swap a data disk using the old parity disk.

As for catching this earlier: after any hardware work, start the array and check the Main page for errors on any disk. Also make sure notifications are enabled, since Unraid alerts you when a disk's SMART CRC count increases. A parity check is still the only full read test of all disks, so if you have moved disks around, it is a good idea to run a non-correcting check before doing any disk replacement.

  • Author
2 hours ago, JorgeB said:

By the description, the errors were reported by a data disk during the sync. Unraid could not read those sectors, so parity was not calculated correctly for them. Until that is fixed, the new parity cannot be fully trusted, so don't do any data disk replacement yet. A rebuild now could be corrupt in the areas that failed to read.

For the same reason, leave the old 22TB parity disk untouched for now, don't reuse it or clear it. It is your fallback until the new parity is confirmed good.

Please post the diagnostics (Tools > Diagnostics), ideally before rebooting, so we can see the actual errors in the syslog. They will also show the disk's SMART report, which tells us if this is a cable problem (UDMA CRC errors) or a disk problem (pending or reallocated sectors).

If it turns out to be a connection issue, reseat or replace the cable, then run a correcting parity check. It should finish without any errors on the disks. Only after that is it safe to swap a data disk using the old parity disk.

As for catching this earlier: after any hardware work, start the array and check the Main page for errors on any disk. Also make sure notifications are enabled, since Unraid alerts you when a disk's SMART CRC count increases. A parity check is still the only full read test of all disks, so if you have moved disks around, it is a good idea to run a non-correcting check before doing any disk replacement.

Thanks for the heads up, I thought it's best to wait before doing any more. Hope it's nothing serious.

unraid-diagnostics-20261115-1158.zip

Thanks for the diagnostics. They confirm it's a connection problem, not a disk problem.

All 6779 errors came from disk4 (the WD 10TB). A few minutes after the sync started, it began logging ATA bus/CRC errors, and the link speed was lowered several times. Its SMART report shows 3490 UDMA CRC errors and no reallocated or pending sectors, so the disk itself is fine, and so is the data on it. But Unraid could not read those sectors during the sync, so parity is wrong for those areas. The new parity disk looks good.

What to do:

1. Power down, reseat disk4 in its bay, and replace the SATA cable that goes from the N1 backplane to the controller for that slot. If you have a spare bay, you can also use it to rule out the backplane.

2. Boot, start the array, and run a correcting parity check. It should find and correct sync errors where the reads failed, but there must be no new errors on any disk on the Main page. If you want extra confirmation, a non-correcting check afterwards should finish with 0 errors.

3. The CRC count will never go back to zero. That is normal, only a new increase matters. Acknowledge the SMART warning on the Dashboard so you get a notification if it goes up again.

Until that check finishes cleanly, keep the old 22TB parity disk as it is. Once it has, you can safely use it to replace the smaller data disk.

If you see errors on disk4 again after the cable change, post new diagnostics.

  • Author
4 hours ago, JorgeB said:

Thanks for the diagnostics. They confirm it's a connection problem, not a disk problem.

All 6779 errors came from disk4 (the WD 10TB). A few minutes after the sync started, it began logging ATA bus/CRC errors, and the link speed was lowered several times. Its SMART report shows 3490 UDMA CRC errors and no reallocated or pending sectors, so the disk itself is fine, and so is the data on it. But Unraid could not read those sectors during the sync, so parity is wrong for those areas. The new parity disk looks good.

What to do:

1. Power down, reseat disk4 in its bay, and replace the SATA cable that goes from the N1 backplane to the controller for that slot. If you have a spare bay, you can also use it to rule out the backplane.

2. Boot, start the array, and run a correcting parity check. It should find and correct sync errors where the reads failed, but there must be no new errors on any disk on the Main page. If you want extra confirmation, a non-correcting check afterwards should finish with 0 errors.

3. The CRC count will never go back to zero. That is normal, only a new increase matters. Acknowledge the SMART warning on the Dashboard so you get a notification if it goes up again.

Until that check finishes cleanly, keep the old 22TB parity disk as it is. Once it has, you can safely use it to replace the smaller data disk.

If you see errors on disk4 again after the cable change, post new diagnostics.

Wow, thank you for confirming.

Okay I will try that.

Before I do, when you say "run a correcting parity check" is that basically doing the full 2 day party check again?

  • Author
On 11/16/2026 at 7:25 AM, JorgeB said:

Yep

Cool, I will do that then.

PS I tried to like the replies but it won't let me.

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.