Hi all,

 

I'm in a bit of a dilemma!

 

Running Unraid version: 4.5.4 with 18 discs. Last week after a parity check i discovered drive 4 with some read errors. I did a smart test and the disc came out with :

 

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   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   148   145   021    Pre-fail  Always       -       9566
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       81
  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   099   099   000    Old_age   Always       -       885
10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       77
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       15
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       1300
194 Temperature_Celsius     0x0022   125   098   000    Old_age   Always       -       27
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       10
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       1
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   199   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       90%       825         6093082

 

10 Pending Sectors show me i need to RMA the disc i guess. I'll ordered another one to swap this one.

In the meantime backuped some some more data to another disc. Then discovered that my parity drive showed errors in the webif. The syslog shows several:

 

Nov  2 19:24:24 SPACEHOG kernel: md: disk0 read error
Nov  2 19:24:24 SPACEHOG kernel: handle_stripe read error: 594018304/0, count: 1
Nov  2 19:35:49 SPACEHOG kernel: ata17.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov  2 19:35:49 SPACEHOG kernel: ata17.00: irq_stat 0x40000001
Nov  2 19:35:49 SPACEHOG kernel: ata17.00: failed command: READ DMA EXT
Nov  2 19:35:49 SPACEHOG kernel: ata17.00: cmd 25/00:08:3f:00:a0/00:00:24:00:00/e0 tag 0 dma 4096 in
Nov  2 19:35:49 SPACEHOG kernel:          res 51/40:00:42:00:a0/00:00:24:00:00/e0 Emask 0x9 (media error)
Nov  2 19:35:49 SPACEHOG kernel: ata17.00: status: { DRDY ERR }
Nov  2 19:35:49 SPACEHOG kernel: ata17.00: error: { UNC }
Nov  2 19:35:49 SPACEHOG kernel: ata17.00: configured for UDMA/133
Nov  2 19:35:49 SPACEHOG kernel: ata17: EH complete

 

I'll ran a smart test on the parity drive and came out with :

 

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   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   150   147   021    Pre-fail  Always       -       9500
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       111
  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   099   099   000    Old_age   Always       -       1121
10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       93
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       5
193 Load_Cycle_Count        0x0032   198   198   000    Old_age   Always       -       6435
194 Temperature_Celsius     0x0022   125   102   000    Old_age   Always       -       27
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   196   196   000    Old_age   Always       -       1463
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       1
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       90%      1111         430717335

 

Not to good either. The question now is how to get this fixed? As far as i understand it, if I'm going to change the parity disc and do a rebuild of the parity the errors of disc 4 would be integrated into the parity?! Swapping the data disc wouldn't get me any further since i guess a rebuild with the defective parity drive wouldn't recover my data drive properly?!

 

Any idea how to solve this? I could try to move the data from the bad data drive to an external drive and end up with an empty data disc. Then it wouldn't be a problem if the data drive isn't rebuild correct?! If i then swap the parity drive, rebuild the parity with the empty drive, swap the data disc, and copy my data back... would this be a proper approach?

 

 

Thanks guys!

 

 

syslog.zip

10 pending sectors on the one disk is nothing to be overly concerned about.  If that number suddenly goes up then you can start to worry.  If unRAID did not disable the drive with 10 pending then they were read errors and you should be fine.

 

The parity drive is another story.  It shows a lot of pending sectors and is probably due for an RMA.  You can run a smart long test on the drive (disable disk spindown first) to see what happens, but that drive is probably on its way out.

 

Check your cables and power connections just to make sure it is all there just to make sure.

I allready did a long smart test on the parity the report i added to my post was after the test. So you think its save just to swap the parity drive with a new one and rebuild the parity?

I allready did a long smart test on the parity the report i added to my post was after the test. So you think its save just to swap the parity drive with a new one and rebuild the parity?

that's what I would do.

I'll started a /NOCORRECT parity check this morning, and I have OVER 9000 read errors so far, I guess this one is foobared.

Let's hope the rest holds up the fort until I rebuild the parity on a new one.

 

Just to be absolutly sure, to swap the parity drive I :

 

1. Unasign the parity drive

2. Replace it

3. Reassign the new drive to the parity slot

4. 'initconfig' aka restore the array with the new parity drive

 

Correct?

I'll started a /NOCORRECT parity check this morning, and I have OVER 9000 read errors so far, I guess this one is foobared.

Let's hope the rest holds up the fort until I rebuild the parity on a new one.

 

Just to be absolutly sure, to swap the parity drive I :

 

1. Unasign the parity drive

2. Replace it

3. Reassign the new drive to the parity slot

4. 'initconfig' aka restore the array with the new parity drive

 

Correct?

NO... that is NOT correct. 

 

You power down,

Replace the old parity disk with the new

Power up

The array will notice you changed disks and not automatically start.  It will prompt you to press "Start" to begin calculating parity on the new disk (you might need to check the checkbox under Start to enable it)

Then press "Start"

That's it.  (other than waiting for the new parity calc to complete)

 

There is no need to use the Devices page, unRAID will see you replaced the parity disk and assign it for you (as long as it is connected to the same port on the disk controller as the old parity drive.  If it is on a different port, you will need to use the "Devices" page to assign it yourself)  There is no need to set a new configuration.  That is a VERY bad choice in most situations UNLESS you are removing a disk from the array and do not intend to replace it.    Initializing a new configuration is almost never needed otherwise.

Allright, thanks a lot for clarifying! I will try it a shot and report back...

Rebuild with a new parity drive succesed, everything looks fine ... even with the 'problematic' data disc.

 

Thanks for your help!

Carefully review the syslog for signs of errors from the data disk with the 10 pending sectors. Also run another smart report on that data disk to see if there is any worsening of attributes.

 

My experience has been that once you start seeing reallocation issues in the smart reports, they tend to get worse.