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 Question

Featured Replies

Hello all,

I have a drive that's reporting SMART errors. I do have a replacement on the way however the server hung up not too long ago and I had to perform a hard reboot. It did perform a party check after the crash and found an error which corrected. I am performing another correcting parity check and it appears that it found probably that same error which corrected. Now I am aware that the drive causing the SMART errors is probably causing this Parity errors to occur, which I do plan on getting replaced soon hopefully today (I'm at the mercy of the courier), however should I run a final non correcting check prior to replacing the drive?

I do have file integrity plugin installed, and it found 1 corruption on the drive, however it's just a recent Plex docker backup that I'm not 100% concerned about as last week's backup still exists (I am still running the hash check so hopefully it remains the same).

Update:

File hash found another corrupted file, however it's just a Proxmox backup that I'm not too worried about, as that also gets backed up to Cloud.

bigboi-diagnostics-20260407-0730.zip

Edited by sp33dy905

  • Community Expert

To be honest, I would not have been running correcting parity checks until after a disk rebuild. Unraid doesn't know if the parity data is valid or the array data is valid and you've been force updating the parity data based on the array data which may or may not have been problematic. For all we know now is that the data on the bad disk is malformed and potentially could have been saved when rebuilding for parity assuming parity was still valid.

Im not an expert on parity rebuilds or sync errors so take what I say with a grain of salt but this is what my first thought is.

I see no value in running a parity check at this point. I would say, re-evaluate the data once the rebuild is finished. If it looks good no further may be action required.

  • Author
23 minutes ago, MowMdown said:

To be honest, I would not have been running correcting parity checks until after a disk rebuild. Unraid doesn't know if the parity data is valid or the array data is valid and you've been force updating the parity data based on the array data which may or may not have been problematic. For all we know now is that the data on the bad disk is malformed and potentially could have been saved when rebuilding for parity assuming parity was still valid.

Im not an expert on parity rebuilds or sync errors so take what I say with a grain of salt but this is what my first thought is.

I see no value in running a parity check at this point. I would say, re-evaluate the data once the rebuild is finished. If it looks good no further may be action required.

Hmm okay, the only reason why I've ran the 2nd check was that I remember seeing threads that another one should be ran until parity is properly synced up (no errors). Maybe I'm misremembering.

This current check I'm running is almost completed (95%), I'll let that finish.

The replacement drive is out for delivery though, so I'll get that swapped once I can, it is bigger than the failed drive, I was able to grab it practically the same price.

Help me understand this though, since Unraid hasn't disabled the drive yet (thankfully), I should be able to just follow the upgrading capacity steps from Unraid's documentation (https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/) or should I just perform the "Preparing drive replacement" steps? My gut tells me it's the latter due to the SMART errors.

  • Author

Scratch that, looks like there a SpaceInvaderOne video for this situation, I will refer to it once its time for the replacement.

  • Community Expert
6 hours ago, sp33dy905 said:

elp me understand this though, since Unraid hasn't disabled the drive yet (thankfully), I should be able to just follow the upgrading capacity steps from Unraid's documentation (https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/) or should I just perform the "Preparing drive replacement" steps? My gut tells me it's the latter due to the SMART errors.

https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/

You will want to follow these procedures. Videos can be out of date the docs should always be current.

Edited by MowMdown

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.