Strange SMART status

Iskander · Oct 28, 2015

Hi All,

I'm new in FreeNAS.

I catch a problem with my Seagate 3Tb disks. So, I have 2 massive first with 2 Saegate 2Tbx2 disks and second with Seagate 3TBx2 disks. All 3Tb disk marked as end_of_life. I've replace these to another server and recheck with BIOS, Raid Controller BIOS and Seagate tools - All tools show me that disks has good state. But FreeNAS all time marked there as end_of_life.

Code:

[root@HFPHFNL001] ~# smartctl -H /dev/ada1
smartctl 6.3 2014-07-26 r3976 [FreeBSD 9.3-RELEASE-p26 amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
Please note the following marginal Attributes:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
184 End-to-End_Error        0x0032   099   099   099    Old_age   Always   FAILING_NOW 1

Code:

[root@HFPHFNL001] ~#  smartctl -a /dev/ada1
smartctl 6.3 2014-07-26 r3976 [FreeBSD 9.3-RELEASE-p26 amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST3000DM001-1CH166
Serial Number:    W1F3FYE5
LU WWN Device Id: 5 000c50 06a3ab655
Firmware Version: CC27
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Thu Oct 29 00:08:08 2015 MSK
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:  (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:                (  584) 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:        ( 336) 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   119   099   006    Pre-fail  Always       -       218351032
  3 Spin_Up_Time            0x0003   094   094   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       229
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       8
  7 Seek_Error_Rate         0x000f   072   060   030    Pre-fail  Always       -       12938741892
  9 Power_On_Hours          0x0032   097   097   000    Old_age   Always       -       3226
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       99
183 Runtime_Bad_Block       0x0032   094   094   000    Old_age   Always       -       6
184 End-to-End_Error        0x0032   099   099   099    Old_age   Always   FAILING_NOW 1
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       1 9 16
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   066   051   045    Old_age   Always       -       34 (Min/Max 34/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       -       226
193 Load_Cycle_Count        0x0032   097   097   000    Old_age   Always       -       7785
194 Temperature_Celsius     0x0022   034   049   000    Old_age   Always       -       34 (0 16 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   187   000    Old_age   Always       -       92
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       2129h+12m+23.358s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       6568419503
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       71675417910

SMART Error Log Version: 1
ATA Error Count: 16 (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 16 occurred at disk power-on lifetime: 1495 hours (62 days + 7 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 9f a8 46 00  Error: UNC at LBA = 0x0046a89f = 4630687

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 00 9f a8 46 40 00      00:01:49.056  READ VERIFY SECTOR(S) EXT
  42 00 01 9e a8 46 40 00      00:01:48.659  READ VERIFY SECTOR(S) EXT
  61 00 01 9e a8 46 40 00      00:01:48.659  WRITE FPDMA QUEUED
  42 00 00 9e a8 46 40 00      00:01:48.322  READ VERIFY SECTOR(S) EXT
  42 00 01 9d a8 46 40 00      00:01:47.919  READ VERIFY SECTOR(S) EXT

Error 15 occurred at disk power-on lifetime: 1495 hours (62 days + 7 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 9f a8 46 00  Error: UNC at LBA = 0x0046a89f = 4630687

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 00 9f a8 46 40 00      00:01:49.056  READ VERIFY SECTOR(S) EXT
  42 00 01 9e a8 46 40 00      00:01:48.659  READ VERIFY SECTOR(S) EXT
  61 00 01 9e a8 46 40 00      00:01:48.659  WRITE FPDMA QUEUED
  42 00 00 9e a8 46 40 00      00:01:48.322  READ VERIFY SECTOR(S) EXT
  42 00 01 9d a8 46 40 00      00:01:47.919  READ VERIFY SECTOR(S) EXT

Error 14 occurred at disk power-on lifetime: 1495 hours (62 days + 7 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 9e a8 46 00  Error: UNC at LBA = 0x0046a89e = 4630686

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 00 9e a8 46 40 00      00:01:48.322  READ VERIFY SECTOR(S) EXT
  42 00 01 9d a8 46 40 00      00:01:47.919  READ VERIFY SECTOR(S) EXT
  61 00 01 9d a8 46 40 00      00:01:47.918  WRITE FPDMA QUEUED
  42 00 00 9d a8 46 40 00      00:01:47.589  READ VERIFY SECTOR(S) EXT
  42 00 01 9c a8 46 40 00      00:01:47.182  READ VERIFY SECTOR(S) EXT

Error 13 occurred at disk power-on lifetime: 1495 hours (62 days + 7 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 9e a8 46 00  Error: UNC at LBA = 0x0046a89e = 4630686

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 00 9e a8 46 40 00      00:01:48.322  READ VERIFY SECTOR(S) EXT
  42 00 01 9d a8 46 40 00      00:01:47.919  READ VERIFY SECTOR(S) EXT
  61 00 01 9d a8 46 40 00      00:01:47.918  WRITE FPDMA QUEUED
  42 00 00 9d a8 46 40 00      00:01:47.589  READ VERIFY SECTOR(S) EXT
  42 00 01 9c a8 46 40 00      00:01:47.182  READ VERIFY SECTOR(S) EXT

Error 12 occurred at disk power-on lifetime: 1495 hours (62 days + 7 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 9d a8 46 00  Error: UNC at LBA = 0x0046a89d = 4630685

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 00 9d a8 46 40 00      00:01:47.589  READ VERIFY SECTOR(S) EXT
  42 00 01 9c a8 46 40 00      00:01:47.182  READ VERIFY SECTOR(S) EXT
  61 00 01 9c a8 46 40 00      00:01:47.182  WRITE FPDMA QUEUED
  42 00 00 9c a8 46 40 00      00:01:46.855  READ VERIFY SECTOR(S) EXT
  42 00 01 9b a8 46 40 00      00:01:46.454  READ VERIFY SECTOR(S) EXT

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%      3225         -
# 2  Extended offline    Aborted by host               90%      3225         -
# 3  Extended offline    Aborted by host               90%      3225         -

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.

So, How can I resolve this problem? Which tools I must trust?

PS: At the moment I've started long self-test. After continue I'll post results.

Kind Regards

SweetAndLow · Oct 28, 2015

Disk looks bad to me. What did seagate tools tell you? Did you run a smart test with it?

jgreco · Oct 28, 2015

Seagate tools can run a long test as well, but unless you did that, it's unlikely to say anything except the disk is good.

Robert Trevellyan · Oct 28, 2015

Iskander said:
SMART overall-health self-assessment test result: PASSED

Iskander said:
184 End-to-End_Error 0x0032 099 099 099 Old_age Always FAILING_NOW 1

Seems pretty clear to me.

The first is saying that technically, the self-test passed.

The second is saying that the disk is at risk of failing at any moment, and you have an opportunity to replace it before it dies.

EDIT: the description of #184 on Wikipedia suggests that having it reach threshold may indicate "imminent electromechanical failure."

Iskander · Oct 29, 2015

Hm.. Very strange. But I think that disk health because I can copy to this disk 2,2 Tb and after copy from this disk without any issue or errors.
Also I found this on sourceforge - link

It's very hard to know because Seagate does not document their SMART
attributes. However, the fact that they would set the threshold so
high (100 is best, 99 already fails) indicates that it's a very
important attribute.

smartmontools 5.39 labels this attribute as "End-to-End_Error" --
however, this comes from Hewlett-Packard's documentation and only
refers to HP's drives. The two HP drives that I have list this
attribute as "184 Unknown_Attribute 0x0033 100 100 003
Pre-fail Always - 0"https://forums.freenas.org/index.php?threads/strange-smart-status.38935/

Notice that this threshold is 3 instead of 99, and has type "Pre-fail"
instead of "Old_age" -- so HP's description probably does not apply to
Seagate drives.

Only newer Seagate drives seem to have this attribute; all 9 of my
drives that have this attribute have the same flags as your laptop's
(old-age and threshold at 99). Although these are Seagate Barracuda
drives. I haven't seen this attribute failing yet.

This response probably wasn't terribly useful to you, but that's all I
know about this attribute. You should certainly back up all your
important data on this drive and see how it behaves in the future.
Maybe even reclaim your warranty because the disk identifies itself as
failing.

Robert Trevellyan · Oct 29, 2015

Iskander said:
I think that disk health because I can copy to this disk 2,2 Tb and after copy from this disk without any issue or errors.

I don't believe that being able to copy data to and from the drive today means it won't fail tomorrow. On the contrary, the number of errors in the SMART log and the state of the other SMART attributes seem like red flags to me. In particular, regardless of what #184 means for a Seagate drive, it has reached threshold. Aside from this, the ST3000DM001 model is known for early failure, as you will see if you do a search for that identifier.

Iskander · Oct 29, 2015

I mean that this is new FreenAS install. I don't use FreeNAS before.

jgreco · Oct 29, 2015

Being able to copy data to and from a disk is not an indication of the disk's health. I can copy data to and from a disk that's been heated to 60'C, but the disk is going to have a short life.

Important Announcement for the TrueNAS Community.

Strange SMART status

Iskander

Cadet

SweetAndLow

Sweet'NASty

jgreco

Resident Grinch

Robert Trevellyan

Pony Wrangler

Iskander

Cadet

Robert Trevellyan

Pony Wrangler

Iskander

Cadet

jgreco

Resident Grinch

Similar threads