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.

Drive Errors During Parity Check

Featured Replies

Last night, I ran a parity check on my array. My array consists of 4 2TB data drives and a 2TB parity drive. THe parity check completed just fine with no errors, but drive 3 of the array is currently showing 2679 errors. The drive status still shows green and the array itself seems just fine. The SMART report on the drive shows the following statistics:

 

 

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   197   185   051    Pre-fail  Always       -       1479
  3 Spin_Up_Time            0x0027   161   160   021    Pre-fail  Always       -       6950
  4 Start_Stop_Count        0x0032   097   097   000    Old_age   Always       -       3089
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   073   073   000    Old_age   Always       -       20124
10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       109
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       15
193 Load_Cycle_Count        0x0032   189   189   000    Old_age   Always       -       35204
194 Temperature_Celsius     0x0022   128   116   000    Old_age   Always       -       22
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       135
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   195   000    Old_age   Offline      -       3

SMART Error Log Version: 1
No Errors Logged

 

It seems like the drive may be on its way to failure due to the number of pending sectors...

 

My question is this: I have a new 3TB drive that I had intended on swapping in place for my current parity drive. Would it be safe to perform the swap of the parity drive even with the current error status of drive 3? I could then just take the old parity drive and replace drive 3 with it leaving existing drive 3 as spare. I am just trying to gauge the severity of the errors on this drive so I can come up with a course of action.

 

Thanks!

It is not safe to replace the parity drive at this point.  You must deal with the drive with the pending sectors first.

 

Note: you MUST be running unRAID 5.0beta8 or newer to be able to use the 3TB drive.

 

The only post you made where you mentioned the unRAID release you were running says you are running 5.0beta6. 

THIS IS NOT ABLE TO HANDLE 3TB DRIVES.

 

You must upgrade to a newer unRAID before doing anything. 

( find newest here http://lime-technology.com/download/cat_view/49-unraid-server )

 

It is 5.0rc10 .

 

Joe L.

  • Author

Thanks for the quick reply....

 

I am actually currently running 5.0-rc8a... I was planning on upgrading to rc10 right after the parity check, but these errors popped up.

Thanks for the quick reply....

 

I am actually currently running 5.0-rc8a... I was planning on upgrading to rc10 right after the parity check, but these errors popped up.

I would upgrade to rc10 first.  rc9 fixed a bug where the unRAID GUI would hang on a swap-disabled process.

 

From the release notes:

- webGui: copying parity prior to a "swap disable" will not hang webGui

Basically, I think what it is saying is on earlier versions, (prior ro rc9) during the initial copy of parity to the new larger parity disk, the web-interface will be completely un-responsive.

  • Author

ok.... I'll go ahead and move to rc10 immediately.

 

I read up on the swap-disable procedure, and it looks like that is what I need. Only question I have is could I simply just physically pull the failing drive out of the box and and put in what is going to be my new parity drive and then restart the array prior to setting up the swap-disable procedure?

Yes, that is exactly what you do. Then after booting, you assign the parity as the replaced data drive and assign the new drive to the parity slot. Read the screen to make sure it's properly describing what you want done and then start the array and let it work.

  • Author

So I upgraded to rc10, replaced the failing drive and then put the new 3TB drive in... When I try to assign the parity to the new 3TB drive and the old parity drive to the failed disk3, the GUI only gives me the message of having  "too many wrong/missing disks" ... what am I missing here?

  • Author

ok, never mind.... turns out I had to actually start and stop the array once to get the system to register the missing disk as gone. It is now swapping parity as intended...

 

thanks!

  • Author

How long does the copy of parity generally take? It's been about 12 hours now. Also, should there be any status info or indication of progress? The web GUI just states the array as being stopped with the statement "upgrading disk/swapping parity". Is there any indication that it is working?

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.