Hello all,

I have been running unraid for about a year and a half now and just installed UnMenu and was checking out some of the features.

Anyway noticed that i was getting some error's on my parity drive from the the stock unraid interface and decided to run a smart test on the drive. I noticed that "5 Reallocated_Sector_Ct" said "failing now" and realized that couldn't be right.

the drive is only about 5months old.

can someone please take a look at my smart results and let me know if I am correct in saying that my drive is failing and should RMA it.

 

smartctl -a -d ata /dev/sda
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 WD2001FASS-00U0B0
Serial Number:    WD-WMAUR0171202
Firmware Version: 01.00101
User Capacity:    2,000,398,934,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:    Sat Dec  4 00:07:29 2010 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: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
See vendor-specific Attribute list for failed Attributes.

General SMART Values:
Offline data collection status:  (0x84)	Offline data collection activity
				was suspended by an interrupting command from host.
				Auto Offline Data Collection: Enabled.
Self-test execution status:      (  73)	The previous self-test completed having
				a test element that failed and the test
				element that failed is not known.
Total time to complete Offline 
data collection: 		 (32160) 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: 	 ( 255) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x3037)	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   199   199   051    Pre-fail  Always       -       38319
  3 Spin_Up_Time            0x0027   040   040   021    Pre-fail  Always       -       15000
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       257
  5 Reallocated_Sector_Ct   0x0033   084   084   140    Pre-fail  Always   FAILING_NOW 927
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   095   095   000    Old_age   Always       -       4019
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       -       7
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       2
193 Load_Cycle_Count        0x0032   198   198   000    Old_age   Always       -       6210
194 Temperature_Celsius     0x0022   122   102   000    Old_age   Always       -       30
196 Reallocated_Event_Count 0x0032   001   001   000    Old_age   Always       -       550
197 Current_Pending_Sector  0x0032   199   196   000    Old_age   Always       -       338
198 Offline_Uncorrectable   0x0030   200   198   000    Old_age   Offline      -       103
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   179   151   000    Old_age   Offline      -       4355

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: unknown failure    90%      4018         -
# 2  Short offline       Completed: unknown failure    90%      4018         -

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.

 

Thanks

That drive is, as you described, failing now.  There are  927 sectors that have been re-allocated and 338 more that are pending re-allocation.

 

It is WAY past the time to RMA it.  It does not matter the age of the drive.

 

Joe L.

 

 

This disk is a goner. I would not leave it powered on in the array. Better to pull it out and let unRaid simulate it. Or better yet, replace it with a new disk!

 

I wonder if this answers one of life's little mysteries about how many spare sectors a drive has available for remapping. Looks like 927 for this disk.

This disk is a goner. I would not leave it powered on in the array. Better to pull it out and let unRaid simulate it. Or better yet, replace it with a new disk!

 

I wonder if this answers one of life's little mysteries about how many spare sectors a drive has available for remapping. Looks like 927 for this disk.

It is the parity disk  there is nothing to "simulate"

 

It can't hurt to leave it in place as it "might" still help if another disk were to fail (as long as the files being re-constructed were not using those 1300 sectors it would still help)

 

Definitely get a replacement disk... as soon as possible...  It is not the time to wait for a bargain to go on sale.

Thanks guys, I figured as much after I did some searching as to what that error really meant and initiated an RMA last night. I'm thinking about getting another 2tb drive as well.

Joe, only reason I mentioned the age is because I was in shock that it would fail on me so soon being it was supposed to be a rock solid drive and it was the first drive to fail on me ever. ah well that will teach me to be so optimistic about hardware I guess and now I will need to be more vigilant in monitoring the health of my servers.

Thanks again

So as soon as my RMA drive get's here i'll be shipping the failing one back to WD.

Now would WD be able to read or recover what's on the drive if I don't clear the drive before I send it?

So as soon as my RMA drive get's here i'll be shipping the failing one back to WD.

Now would WD be able to read or recover what's on the drive if I don't clear the drive before I send it?

 

If this is your parity disk, there is nothing on the disk to recover.  Also nothing that anyone is going to be able to use (it is just parity information from across all the disks in your array).  The only exceptions are if there is only one data disk. In which case the parity is just a mirror of that one disk.  And if your disks are largely precleared and you only have data written to one - then there would be readable info on the disk.

 

If you have sensitive data on your array and it would help you sleep better at night, go ahead and try to preclear it.  I'd skip the pre and post reads.  Just try to to the writes.