Smart errors

Status
Not open for further replies.

Crustacean

Dabbler
Joined
Jan 31, 2014
Messages
22
I'm not sure if there is a guide on understanding the output of a smart test, but after reading a few threads I still don't know what I'm looking at.
I'm getting the following email:

Code:
Device: /dev/ada6, 65528 Offline uncorrectable sectors


I've received it twice now in the span of 15 days. The number actually went down to 65520 in the last email. Is that number the count of bad sectors? That's quite a few.

Here's the output of smartctl -a /dev/ada6

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:    ST1000DM003-9YN162
Serial Number:    S1D261TQ
LU WWN Device Id: 5 000c50 04b630d4b
Firmware Version: CC4B
User Capacity:    1,000,204,886,016 bytes [1.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: 6.0 Gb/s)
Local Time is:    Thu Jun 19 12:38:39 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
 
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:                (  575) 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:        (  1) minutes.
Extended self-test routine
recommended polling time:        ( 112) 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  114  068  006    Pre-fail  Always      -      82908488
  3 Spin_Up_Time            0x0003  097  097  000    Pre-fail  Always      -      0
  4 Start_Stop_Count        0x0032  100  100  020    Old_age  Always      -      145
  5 Reallocated_Sector_Ct  0x0033  085  051  036    Pre-fail  Always      -      20032
  7 Seek_Error_Rate        0x000f  088  060  030    Pre-fail  Always      -      5032305264
  9 Power_On_Hours          0x0032  087  087  000    Old_age  Always      -      11819
10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -      0
12 Power_Cycle_Count      0x0032  100  100  020    Old_age  Always      -      144
183 Runtime_Bad_Block      0x0032  100  100  000    Old_age  Always      -      0
184 End-to-End_Error        0x0032  100  100  099    Old_age  Always      -      0
187 Reported_Uncorrect      0x0032  001  001  000    Old_age  Always      -      3588
188 Command_Timeout        0x0032  100  095  000    Old_age  Always      -      1 1 10
189 High_Fly_Writes        0x003a  085  085  000    Old_age  Always      -      15
190 Airflow_Temperature_Cel 0x0022  071  050  045    Old_age  Always      -      29 (Min/Max 25/35)
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      -      128
193 Load_Cycle_Count        0x0032  100  100  000    Old_age  Always      -      219
194 Temperature_Celsius    0x0022  029  050  000    Old_age  Always      -      29 (0 17 0 0 0)
197 Current_Pending_Sector  0x0012  100  001  000    Old_age  Always      -      0
198 Offline_Uncorrectable  0x0010  100  001  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      -      11562h+55m+33.664s
241 Total_LBAs_Written      0x0000  100  253  000    Old_age  Offline      -      160718803930890
242 Total_LBAs_Read        0x0000  100  253  000    Old_age  Offline      -      186223854901614
 
SMART Error Log Version: 1
ATA Error Count: 3226 (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 3226 occurred at disk power-on lifetime: 11377 hours (474 days + 1 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 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
 
  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 00 ff ff ff 4f 00  16d+14:57:37.362  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  16d+14:57:36.412  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  16d+14:57:36.412  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  16d+14:57:35.294  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  16d+14:57:34.686  READ FPDMA QUEUED
 
Error 3225 occurred at disk power-on lifetime: 9373 hours (390 days + 13 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 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
 
  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 00 ff ff ff 4f 00  19d+18:11:15.788  READ FPDMA QUEUED
  60 00 80 ff ff ff 4f 00  19d+18:11:15.788  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00  19d+18:11:15.700  READ LOG EXT
  60 00 00 ff ff ff 4f 00  19d+18:11:12.248  READ FPDMA QUEUED
  60 00 80 ff ff ff 4f 00  19d+18:11:12.247  READ FPDMA QUEUED
 
Error 3224 occurred at disk power-on lifetime: 9373 hours (390 days + 13 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 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
 
  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 00 ff ff ff 4f 00  19d+18:11:12.248  READ FPDMA QUEUED
  60 00 80 ff ff ff 4f 00  19d+18:11:12.247  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00  19d+18:11:12.216  READ LOG EXT
  60 00 00 ff ff ff 4f 00  19d+18:11:09.036  READ FPDMA QUEUED
  60 00 80 ff ff ff 4f 00  19d+18:11:09.036  READ FPDMA QUEUED
 
Error 3223 occurred at disk power-on lifetime: 9373 hours (390 days + 13 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 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
 
  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 00 ff ff ff 4f 00  19d+18:11:09.036  READ FPDMA QUEUED
  60 00 80 ff ff ff 4f 00  19d+18:11:09.036  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00  19d+18:11:09.033  READ LOG EXT
  60 00 00 ff ff ff 4f 00  19d+18:11:05.829  READ FPDMA QUEUED
  60 00 80 ff ff ff 4f 00  19d+18:11:05.828  READ FPDMA QUEUED
 
Error 3222 occurred at disk power-on lifetime: 9373 hours (390 days + 13 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 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
 
  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 00 ff ff ff 4f 00  19d+18:11:05.829  READ FPDMA QUEUED
  60 00 80 ff ff ff 4f 00  19d+18:11:05.828  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00  19d+18:11:05.702  READ LOG EXT
  60 00 00 ff ff ff 4f 00  19d+18:10:58.813  READ FPDMA QUEUED
  60 00 80 ff ff ff 4f 00  19d+18:10:58.670  READ FPDMA QUEUED
 
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%    11801        -
# 2  Short offline      Completed without error      00%    11777        -
# 3  Short offline      Completed without error      00%    11753        -
# 4  Short offline      Completed without error      00%    11729        -
# 5  Short offline      Completed without error      00%    11705        -
# 6  Short offline      Completed without error      00%    11681        -
# 7  Short offline      Completed without error      00%    11657        -
# 8  Short offline      Completed without error      00%    11633        -
# 9  Short offline      Completed without error      00%    11609        -
#10  Short offline      Completed without error      00%    11585        -
#11  Short offline      Completed without error      00%    11561        -
#12  Short offline      Completed without error      00%    11537        -
#13  Short offline      Completed: read failure      90%    11513        1712505728
#14  Extended offline    Completed: read failure      10%    11507        1850342456
#15  Short offline      Completed without error      00%    11489        -
#16  Short offline      Completed without error      00%    11465        -
#17  Short offline      Completed without error      00%    11441        -
#18  Short offline      Completed without error      00%    11417        -
#19  Short offline      Completed without error      00%    10954        -
#20  Short offline      Completed without error      00%    10931        -
#21  Short offline      Completed without error      00%    10930        -
 
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.


I already have a replacement on the way, but does this drive need to be replaced? Is it dying?
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
You've got (at least) 20032 bad sectors that have been remapped and 3588 "Reported Uncorrect" errors. Yes, the drive is bad.

Eyeballing the Raw Read Error Rate also gives me the feeling it's non-zero (It's recorded as some sort of inverse log scale, so higher numbers are better, because they tend toward zero).
 

Crustacean

Dabbler
Joined
Jan 31, 2014
Messages
22
You've got (at least) 20032 bad sectors that have been remapped and 3588 "Reported Uncorrect" errors. Yes, the drive is bad.

Eyeballing the Raw Read Error Rate also gives me the feeling it's non-zero (It's recorded as some sort of inverse log scale, so higher numbers are better, because they tend toward zero).


Glad my pool is Z2. The drive should still be under warranty, so its no big deal. Thanks for the reply!
 

DrKK

FreeNAS Generalissimo
Joined
Oct 15, 2013
Messages
3,630
Just as a point of knowledge, the "Raw Read Error Rate" means many different things to many different manufacturers. Sometimes it's linear, sometimes it's logarithmic, sometimes higher is better, sometimes lower, it's really a damn nightmare.

It's at the point where you ignore attribute #1, at least as far as I understand.

As for the OP's question, it's amazing this drive still is working and online. Replace it immediately. You have several troubling SMART attributes here...including the bad sectors, the seek errors, and so on.
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Just as a point of knowledge, the "Raw Read Error Rate" means many different things to many different manufacturers. Sometimes it's linear, sometimes it's logarithmic, sometimes higher is better, sometimes lower, it's really a damn nightmare.

It's at the point where you ignore attribute #1, at least as far as I understand.

As for the OP's question, it's amazing this drive still is working and online. Replace it immediately. You have several troubling SMART attributes here...including the bad sectors, the seek errors, and so on.

The seek error rate, like the raw read error rate, is encoded as an inverse log scale on Seagate drives... Higher is better, but it's hard to tell if it's at 0 or not.
My calculator tells me that within its precision (which I assume is FP64) both 2^*that number* and e^*that number* are 0.
 

Hyperion

Dabbler
Joined
Apr 3, 2014
Messages
44
Yes I would backup as much as u can.
That drive is in a fail state.
If it’s a WD and if its under 2 years old, u can get a replacement.
Just email that stuff, and they are kinda cool about it.
 
Status
Not open for further replies.
Top