Jump to content

Errors on parity drive, Offline Uncorrectable..


heffe2001

Recommended Posts

I noticed today that my parity drive has had some errors during a parity check after moving my unraid system to a new case.  Before the move, it showed 0 errors, now the main page shows 59 errors, and smart statistics shows 10 Offline Uncorrectable errors.  I hadn't run parity since around the 19th of last month (I know, shame on me, should have it set up to do it at least once a week), but haven't seen anything wrong just checking the main page until today.

 

I'm going to go ahead and order a new parity drive, but I'm not sure about the existing drive.  I'm attaching the smart report so you guys can see what it's showing.

 

Statistics for /dev/sdk WDC_WD1001FALS-75J7B0_WD-WMATV2005555

smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD1001FALS-75J7B0
Serial Number:    WD-WMATV2005555
Firmware Version: 05.00K05
User Capacity:    1,000,204,886,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Thu Sep  3 08:28:03 2009 GMT+5
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82)	Offline data collection activity
				was completed without error.
				Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
				without error or no self-test has ever 
				been run.
Total time to complete Offline 
data collection: 		 (19200) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
				Auto Offline data collection on/off support.
				Suspend Offline collection upon new
				command.
				Offline surface scan supported.
				Self-test supported.
				Conveyance Self-test supported.
				Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
				power-saving mode.
				Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
				General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 221) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x303f)	SCT Status supported.
				SCT Feature Control supported.
				SCT Data Table supported.

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   217   216   021    Pre-fail  Always       -       9125
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       47
  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   100   100   000    Old_age   Always       -       553
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       -       13
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       4
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       47
194 Temperature_Celsius     0x0022   123   106   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       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       10
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
240 Head_Flying_Hours       0x0032   100   100   000    Old_age   Always       -       134
241 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       6994348246
242 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       10181683774

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  Short offline       Completed without error       00%         6         -

SMART Selective self-test log data structure revision number 1
SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

 

Does it look like the drive is in a pre-failure spiral, or should I just use it as a data drive once the new parity comes in, and monitor the offline uncorrectable errors to see if they continue to grow?

 

 

Link to comment

I noticed today that my parity drive has had some errors during a parity check after moving my unraid system to a new case.  Before the move, it showed 0 errors, now the main page shows 59 errors, and smart statistics shows 10 Offline Uncorrectable errors.  I hadn't run parity since around the 19th of last month (I know, shame on me, should have it set up to do it at least once a week), but haven't seen anything wrong just checking the main page until today.

 

I'm going to go ahead and order a new parity drive, but I'm not sure about the existing drive.  I'm attaching the smart report so you guys can see what it's showing.

 

Statistics for /dev/sdk WDC_WD1001FALS-75J7B0_WD-WMATV2005555

smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD1001FALS-75J7B0
Serial Number:    WD-WMATV2005555
Firmware Version: 05.00K05
User Capacity:    1,000,204,886,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Thu Sep  3 08:28:03 2009 GMT+5
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82)	Offline data collection activity
				was completed without error.
				Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
				without error or no self-test has ever 
				been run.
Total time to complete Offline 
data collection: 		 (19200) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
				Auto Offline data collection on/off support.
				Suspend Offline collection upon new
				command.
				Offline surface scan supported.
				Self-test supported.
				Conveyance Self-test supported.
				Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
				power-saving mode.
				Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
				General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 221) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x303f)	SCT Status supported.
				SCT Feature Control supported.
				SCT Data Table supported.

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   217   216   021    Pre-fail  Always       -       9125
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       47
  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   100   100   000    Old_age   Always       -       553
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       -       13
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       4
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       47
194 Temperature_Celsius     0x0022   123   106   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       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       10
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
240 Head_Flying_Hours       0x0032   100   100   000    Old_age   Always       -       134
241 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       6994348246
242 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       10181683774

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  Short offline       Completed without error       00%         6         -

SMART Selective self-test log data structure revision number 1
SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

 

Does it look like the drive is in a pre-failure spiral, or should I just use it as a data drive once the new parity comes in, and monitor the offline uncorrectable errors to see if they continue to grow?

 

 

You have apparently performed one smart "Short" test.  That is done "Offline" and is probably when the "Offline Uncorrectable errors" occurred.   They are similar to Re-allocated sectors.   Unless you run more smart tests, odds are the off-line uncorrectable errors will remain as they are. 

 

See here on a short description on how to interpret the SMART report: http://www.z-a-recovery.com/man-smart.htm

 

Your drive looks pretty healthy actually...

Link to comment

My real concern is the 59 errors that Unraid shows on the main page, although I don't see anything in the smart statistics that show that many.  I may clear the stats, and run a parity check again to see if more crop up.

 

Are those "parity" errors associated with the parity drive itself on the line showing the parity drive statistics,, or does it show those at the bottom of the screen near the "Check" button?

 

There are two different types of errors.  Those at the bottom are where the parity as calculated is not identical to the data drives.  A small number of errors is not uncommon if you power down the array without a clean stop first.    Only way to know what happened would be if you had captured a syslog after they occurred and before you re-booted.

 

Errors on the "parity drive" itself would be where  a "read" of it failed.  Since your "SMART" results don't show anything major, I'd press the "Clear Statistics" button, then press the "Check" button to re-check parity.

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...