Trust this drive?

[danb35]

I had this drive installed in my FreeNAS 9.2.1.5 server until recently, when it dropped offline and threw a SMART error. I replaced it with another drive, but subsequent testing doesn't seem to confirm a problem. Here's the output of smartctl -a. Thoughts?

Code:

smartctl 6.2 2013-07-26 r3841 [FreeBSD 9.2-RELEASE-p4 amd64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
 
=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST2000DM001-1CH164
Serial Number:    Z1E32QMB
LU WWN Device Id: 5 000c50 04fde4254
Firmware Version: CC26
User Capacity:    2,000,397,852,160 bytes [2.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Sun May 25 07:10:14 2014 EDT
 
==> WARNING: A firmware update for this drive may be available,
see the following Seagate web pages:
http://knowledge.seagate.com/articles/en_US/FAQ/207931en
http://knowledge.seagate.com/articles/en_US/FAQ/223651en
 
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
See vendor-specific Attribute list for marginal Attributes.
 
General SMART Values:
Offline data collection status:  (0x00)Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
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:(  592) seconds.
Offline data collection
capabilities:(0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No 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:(   1) minutes.
Extended self-test routine
recommended polling time:( 222) minutes.
Conveyance self-test routine
recommended polling time:(   2) minutes.
SCT capabilities:      (0x3085)SCT Status supported.
 
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   116   099   006    Pre-fail  Always       -       111808400
  3 Spin_Up_Time            0x0003   096   096   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       27
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   072   060   030    Pre-fail  Always       -       19959198
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       640
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       27
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   063   063   099    Old_age   Always   FAILING_NOW 37
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       0 0 1
189 High_Fly_Writes         0x003a   099   099   000    Old_age   Always       -       1
190 Airflow_Temperature_Cel 0x0022   076   046   045    Old_age   Always       -       24 (Min/Max 24/24)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       24
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       90
194 Temperature_Celsius     0x0022   024   054   000    Old_age   Always       -       24 (0 18 0 0 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       629h+47m+41.422s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       4423418122
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       8458257324
 
SMART Error Log Version: 1
ATA Error Count: 9 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
 
Error 9 occurred at disk power-on lifetime: 599 hours (24 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0
 
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 80 ff ff ff 4f 00      00:07:11.039  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00      00:07:10.944  READ LOG EXT
  60 00 00 ff ff ff 4f 00      00:07:10.944  READ FPDMA QUEUED
  60 00 80 ff ff ff 4f 00      00:07:10.944  READ FPDMA QUEUED
  60 00 80 ff ff ff 4f 00      00:07:10.939  READ FPDMA QUEUED
 
Error 8 occurred at disk power-on lifetime: 599 hours (24 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0
 
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 80 ff ff ff 4f 00      00:07:10.939  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00      00:07:10.842  READ LOG EXT
  60 00 00 ff ff ff 4f 00      00:07:10.842  READ FPDMA QUEUED
  60 00 80 ff ff ff 4f 00      00:07:10.841  READ FPDMA QUEUED
  60 00 80 ff ff ff 4f 00      00:07:10.837  READ FPDMA QUEUED
 
Error 7 occurred at disk power-on lifetime: 599 hours (24 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0
 
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 80 ff ff ff 4f 00      00:07:10.837  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00      00:07:10.687  READ LOG EXT
  61 00 80 ff ff ff 4f 00      00:07:10.646  WRITE FPDMA QUEUED
  61 00 10 90 02 40 40 00      00:07:10.645  WRITE FPDMA QUEUED
  61 00 10 ff ff ff 4f 00      00:07:10.645  WRITE FPDMA QUEUED
 
Error 6 occurred at disk power-on lifetime: 599 hours (24 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 00 00 00 00  Error: WP at LBA = 0x00000000 = 0
 
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 80 ff ff ff 4f 00      00:07:10.646  WRITE FPDMA QUEUED
  61 00 10 90 02 40 40 00      00:07:10.645  WRITE FPDMA QUEUED
  61 00 10 ff ff ff 4f 00      00:07:10.645  WRITE FPDMA QUEUED
  61 00 10 ff ff ff 4f 00      00:07:10.645  WRITE FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      00:07:10.645  READ FPDMA QUEUED
 
Error 5 occurred at disk power-on lifetime: 599 hours (24 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0
 
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 80 ff ff ff 4f 00      00:07:09.264  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00      00:07:09.194  READ LOG EXT
  61 00 80 ff ff ff 4f 00      00:07:09.194  WRITE FPDMA QUEUED
  60 00 80 ff ff ff 4f 00      00:07:09.194  READ FPDMA QUEUED
  60 00 80 ff ff ff 4f 00      00:07:09.194  READ FPDMA QUEUED
 
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%       629         -
# 2  Conveyance offline  Completed without error       00%       626         -
# 3  Short offline       Completed without error       00%       625         -
 
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.

 

[joeschmuck]

In a RAIDZ2 system, sure you can while you wait on the other 3TB drives to show up. ID's 5, 197, and 198 are indicators of a pending hard drive failure. I have no idea what ID 184 is but maybe a little research will shine a light on it. The only thing I could come up with is:

This attribute is a part of Hewlett-Packard's SMART IV technology, as well as part of other vendors' IO Error Detection and Correction schemas, and it contains a count of parity errors which occur in the data path to the media via the drive's cache RAM.

 

[Ericloewe]

The stupid log scale they use for some values really makes it hard to read them...

In any case, RMA it. It says "Failing Now" and it should still be under warranty. Whatever the "End-to-end errors" are, they can't be good.

 

[Yatti420]

Make sure you burn in all remaining drives with badblocks or hdat2.. something thats going to stress them a bit..

 

[danb35]

RMA'd the drive. Not sure how it passed all the SMART tests while (1) it threw all these errors not long ago at all, and (2) it's still failing the end-to-end test. It's still under warranty, but just barely--it was a warranty replacement for another drive that was starting to throw "offline (uncorrectable) sector" messages in the logs. Warranty expires next month. Hoping the third drive is better, because if it lasts as long as this one (25 days), the warranty will be expired by the time it fails.

I seem to be having back luck with drives lately--three defective within about a week. Fortunately, the other two were just destined for a system upgrade, rather than being existing data drives, so nothing is lost.

 

[cyberjock]

End-to-End errors are basically saying that data is being corrupted on the disk controller and/or disk and the controller knows something is very very wrong but doesn't know anything else. Normally End-to-End errors are not a particularly useful metric because if the controller is in that bad of a condition the hard drive usually just stops working entirely.

Anyway, definitely replace that hard drive. ;)

 

[joeschmuck]

End-to-End errors are basically saying that data is being corrupted on the disk controller and/or disk and the controller knows something is very very wrong but doesn't know anything else. Normally End-to-End errors are not a particularly useful metric because if the controller is in that bad of a condition the hard drive usually just stops working entirely.

Anyway, definitely replace that hard drive. ;)

Thanks for that explanation. I only used the Wiki and didn't find that detailed an explanation. Did you just know that or is there a good website to visit with all the details? TIA

 

[cyberjock]

I just know from all of the reading I've done in the past. I have a personal passion for SMART stuff since hard drives failing are too common of a problem to not become an expert in. ;)