smartctl results interpreter please

JKman

JKman

Explorer
Joined
Mar 23, 2014
Messages
52
below are my smartctl results on a drive. i assume this means the drive is likely to fail soon and i need to replace. can someone confirm please? if there is a way to correct these issues as well i am all ears.

Code:
smartctl 6.5 2016-05-07 r4318 [FreeBSD 10.3-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 3.5" DT01ACA... Desktop HDD
Device Model:     TOSHIBA DT01ACA300
Serial Number:    93845KJKS
LU WWN Device Id: 5 000039 ff4cffde1
Firmware Version: MX6OABB0
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:   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:    Wed Mar 18 02:00:01 2020 MST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Power mode is:    ACTIVE or IDLE

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

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     0x000b   085   085   016    Pre-fail  Always       -       10027130
  2 Throughput_Performance  0x0005   140   140   054    Pre-fail  Offline      -       68
  3 Spin_Up_Time            0x0007   130   130   024    Pre-fail  Always       -       440 (Average 441)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       50
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   117   117   020    Pre-fail  Offline      -       36
  9 Power_On_Hours          0x0012   094   094   000    Old_age   Always       -       47426
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       50
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       210
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       210
194 Temperature_Celsius     0x0002   171   171   000    Old_age   Always       -       35 (Min/Max 22/81)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       8
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 25 (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 25 occurred at disk power-on lifetime: 47394 hours (1974 days + 18 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 08 38 3e bb 07  Error: UNC at LBA = 0x07bb3e38 = 129711672

  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 28 80 00 45 77 40 00   3d+06:43:56.473  READ FPDMA QUEUED
  60 08 78 38 3e bb 40 00   3d+06:43:56.473  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   3d+06:43:56.469  READ LOG EXT
  61 50 68 58 9c b3 40 00   3d+06:43:54.008  WRITE FPDMA QUEUED
  61 50 60 00 9c b3 40 00   3d+06:43:54.005  WRITE FPDMA QUEUED

Error 24 occurred at disk power-on lifetime: 47394 hours (1974 days + 18 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 08 38 3e bb 07  Error: WP at LBA = 0x07bb3e38 = 129711672

  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 50 68 58 9c b3 40 00   3d+06:43:54.008  WRITE FPDMA QUEUED
  61 50 60 00 9c b3 40 00   3d+06:43:54.005  WRITE FPDMA QUEUED
  61 50 58 48 9b b3 40 00   3d+06:43:54.001  WRITE FPDMA QUEUED
  61 50 50 40 9a b3 40 00   3d+06:43:53.997  WRITE FPDMA QUEUED
  61 58 48 30 98 b3 40 00   3d+06:43:53.993  WRITE FPDMA QUEUED

Error 23 occurred at disk power-on lifetime: 47394 hours (1974 days + 18 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 08 38 3e bb 07  Error: UNC at LBA = 0x07bb3e38 = 129711672

  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 28 00 00 45 77 40 00   3d+06:43:49.485  READ FPDMA QUEUED
  60 08 f8 38 3e bb 40 00   3d+06:43:49.485  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   3d+06:43:49.481  READ LOG EXT
  60 28 e8 00 45 77 40 00   3d+06:43:45.974  READ FPDMA QUEUED
  60 08 e0 38 3e bb 40 00   3d+06:43:45.974  READ FPDMA QUEUED

Error 22 occurred at disk power-on lifetime: 47394 hours (1974 days + 18 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 08 38 3e bb 07  Error: UNC at LBA = 0x07bb3e38 = 129711672

  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 28 e8 00 45 77 40 00   3d+06:43:45.974  READ FPDMA QUEUED
  60 08 e0 38 3e bb 40 00   3d+06:43:45.974  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   3d+06:43:45.970  READ LOG EXT
  60 28 d0 00 45 77 40 00   3d+06:43:42.422  READ FPDMA QUEUED
  60 08 c8 00 41 77 40 00   3d+06:43:42.422  READ FPDMA QUEUED

Error 21 occurred at disk power-on lifetime: 47394 hours (1974 days + 18 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 08 38 3e bb 07  Error: UNC at LBA = 0x07bb3e38 = 129711672

  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 28 d0 00 45 77 40 00   3d+06:43:42.422  READ FPDMA QUEUED
  60 08 c8 00 41 77 40 00   3d+06:43:42.422  READ FPDMA QUEUED
  60 08 c0 d8 84 bb 40 00   3d+06:43:42.402  READ FPDMA QUEUED
  60 08 b8 38 3e bb 40 00   3d+06:43:42.391  READ FPDMA QUEUED
  60 18 b0 e8 40 77 40 00   3d+06:43:42.388  READ FPDMA QUEUED
 
P

Pitfrr

Wizard
Joined
Feb 10, 2014
Messages
1,531
From what I can tell, the biggest issue is your 197 Current_Pending_Sector at 8, meaning you have 8 pending sectors.

In the details below you have several Error: UNC at LBA = 0x0....., meaning uncorrectable errors.
Given the disk's lifetime, I would replace it. I wouldn't even bother to monitor the #197 counter to see if it rises.
Also an other detail that is bothering me, the line
194 Temperature_Celsius 0x0002 171 171 000 Old_age Always - 35 (Min/Max 22/81)

The maximum temperature was at 81°C!?!
That is very very hot for a hard disk...

If your disk is in a server that is actively used, then I would change it as soon as possible.
 
JKman

JKman

Explorer
Joined
Mar 23, 2014
Messages
52
that high temp reading happened once at the beginning of the build for a very time period. no other issues the entire life of the drive. thanks for the advice, i will replace it!
 
P

Pitfrr

Wizard
Joined
Feb 10, 2014
Messages
1,531
Ok, so it was not a "normal" operating temperature! :smile:
Do you also have regular SMART tests (short and long) planned (they don't show up in the output you pasted)?
 
JKman

JKman

Explorer
Joined
Mar 23, 2014
Messages
52
i thought i did, but either not getting the output mailed to me or i haven't set it up. how do i do this?
 
P

Pitfrr

Wizard
Joined
Feb 10, 2014
Messages
1,531
JKman said:
how do i do this?
Click to expand...
You mean to get the output? smartctl -a /dev/da1
To get the mail: it is not native in FreeNAS (at least not in 9.10.x I'm using, maybe in 11.x but I don't know which one you're using) so you have to install a script to get email SMART reports.
To set it up: in FreeNAS (still 9.10.x, under tasks/SMART tests) you have to configure the SMART tests manually (it is not configured automatically).
 
T

tfran1990

Patron
Joined
Oct 18, 2017
Messages
294
Desktop HDD powered up 50 times, ran for almost 50k hours...... not bad for a Desktop drive.
 
JKman

JKman

Explorer
Joined
Mar 23, 2014
Messages
52
just ordered 4x 8TB WD Red's as replacements for this pool!

1 other drive has started showing similar errors..... crossing fingers.
 
T

tfran1990

Patron
Joined
Oct 18, 2017
Messages
294
whats your pool setup raidz* ?
 
P

Pitfrr

Wizard
Joined
Feb 10, 2014
Messages
1,531
For your information, it is advised to avoid RAIDz1 with "big" drives (i.e. about >1TB) to avoid any unrecoverable read error (due to the size of the disk).
 
JKman

JKman

Explorer
Joined
Mar 23, 2014
Messages
52
full smartctl -a output for both drives with issues:

Code:
smartctl 6.5 2016-05-07 r4318 [FreeBSD 10.3-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 3.5" DT01ACA... Desktop HDD
Device Model:     TOSHIBA DT01ACA300
Serial Number:    93845KJKS
LU WWN Device Id: 5 000039 ff4cffde1
Firmware Version: MX6OABB0
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:   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:    Thu Mar 19 09:48:01 2020 MST
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:  (0x84)    Offline data collection activity
                    was suspended by an interrupting command from host.
                    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:         (22222) seconds.
Offline data collection
capabilities:              (0x5b) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    Offline surface scan supported.
                    Self-test supported.
                    No 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:      ( 371) minutes.
SCT capabilities:            (0x003d)    SCT Status supported.
                    SCT Error Recovery Control 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     0x000b   087   087   016    Pre-fail  Always       -       99
  2 Throughput_Performance  0x0005   140   140   054    Pre-fail  Offline      -       68
  3 Spin_Up_Time            0x0007   130   130   024    Pre-fail  Always       -       440 (Average 441)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       50
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   117   117   020    Pre-fail  Offline      -       36
  9 Power_On_Hours          0x0012   094   094   000    Old_age   Always       -       47458
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       50
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       210
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       210
194 Temperature_Celsius     0x0002   166   166   000    Old_age   Always       -       36 (Min/Max 22/81)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 25 (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 25 occurred at disk power-on lifetime: 47394 hours (1974 days + 18 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 08 38 3e bb 07  Error: UNC at LBA = 0x07bb3e38 = 129711672

  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 28 80 00 45 77 40 00   3d+06:43:56.473  READ FPDMA QUEUED
  60 08 78 38 3e bb 40 00   3d+06:43:56.473  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   3d+06:43:56.469  READ LOG EXT
  61 50 68 58 9c b3 40 00   3d+06:43:54.008  WRITE FPDMA QUEUED
  61 50 60 00 9c b3 40 00   3d+06:43:54.005  WRITE FPDMA QUEUED

Error 24 occurred at disk power-on lifetime: 47394 hours (1974 days + 18 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 08 38 3e bb 07  Error: WP at LBA = 0x07bb3e38 = 129711672

  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 50 68 58 9c b3 40 00   3d+06:43:54.008  WRITE FPDMA QUEUED
  61 50 60 00 9c b3 40 00   3d+06:43:54.005  WRITE FPDMA QUEUED
  61 50 58 48 9b b3 40 00   3d+06:43:54.001  WRITE FPDMA QUEUED
  61 50 50 40 9a b3 40 00   3d+06:43:53.997  WRITE FPDMA QUEUED
  61 58 48 30 98 b3 40 00   3d+06:43:53.993  WRITE FPDMA QUEUED

Error 23 occurred at disk power-on lifetime: 47394 hours (1974 days + 18 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 08 38 3e bb 07  Error: UNC at LBA = 0x07bb3e38 = 129711672

  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 28 00 00 45 77 40 00   3d+06:43:49.485  READ FPDMA QUEUED
  60 08 f8 38 3e bb 40 00   3d+06:43:49.485  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   3d+06:43:49.481  READ LOG EXT
  60 28 e8 00 45 77 40 00   3d+06:43:45.974  READ FPDMA QUEUED
  60 08 e0 38 3e bb 40 00   3d+06:43:45.974  READ FPDMA QUEUED

Error 22 occurred at disk power-on lifetime: 47394 hours (1974 days + 18 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 08 38 3e bb 07  Error: UNC at LBA = 0x07bb3e38 = 129711672

  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 28 e8 00 45 77 40 00   3d+06:43:45.974  READ FPDMA QUEUED
  60 08 e0 38 3e bb 40 00   3d+06:43:45.974  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   3d+06:43:45.970  READ LOG EXT
  60 28 d0 00 45 77 40 00   3d+06:43:42.422  READ FPDMA QUEUED
  60 08 c8 00 41 77 40 00   3d+06:43:42.422  READ FPDMA QUEUED

Error 21 occurred at disk power-on lifetime: 47394 hours (1974 days + 18 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 08 38 3e bb 07  Error: UNC at LBA = 0x07bb3e38 = 129711672

  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 28 d0 00 45 77 40 00   3d+06:43:42.422  READ FPDMA QUEUED
  60 08 c8 00 41 77 40 00   3d+06:43:42.422  READ FPDMA QUEUED
  60 08 c0 d8 84 bb 40 00   3d+06:43:42.402  READ FPDMA QUEUED
  60 08 b8 38 3e bb 40 00   3d+06:43:42.391  READ FPDMA QUEUED
  60 18 b0 e8 40 77 40 00   3d+06:43:42.388  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%     17479         -
# 2  Short offline       Completed without error       00%     17311         -
# 3  Extended offline    Completed without error       00%     17223         -
# 4  Short offline       Completed without error       00%     17143         -
# 5  Short offline       Completed without error       00%     16903         -
# 6  Extended offline    Completed without error       00%     16816         -
# 7  Short offline       Completed without error       00%     16743         -
# 8  Short offline       Completed without error       00%     16575         -
# 9  Extended offline    Completed without error       00%     16489         -
#10  Short offline       Completed without error       00%     16407         -
#11  Short offline       Completed without error       00%     16191         -
#12  Extended offline    Completed without error       00%     16105         -
#13  Short offline       Completed without error       00%     16023         -
#14  Short offline       Completed without error       00%     15855         -
#15  Extended offline    Completed without error       00%     15768         -
#16  Short offline       Completed without error       00%     15687         -
#17  Short offline       Completed without error       00%     15447         -
#18  Extended offline    Completed without error       00%     15361         -
#19  Short offline       Completed without error       00%     15279         -
#20  Short offline       Completed without error       00%     15112         -
#21  Extended offline    Completed without error       00%     15030         -

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.


Code:
smartctl 6.5 2016-05-07 r4318 [FreeBSD 10.3-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 3.5" DT01ACA... Desktop HDD
Device Model:     TOSHIBA DT01ACA300
Serial Number:    9383APVKS
LU WWN Device Id: 5 000039 ff4cf9ccd
Firmware Version: MX6OABB0
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:   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:    Thu Mar 19 09:50:43 2020 MST
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:  (0x84)    Offline data collection activity
                    was suspended by an interrupting command from host.
                    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:         (22365) seconds.
Offline data collection
capabilities:              (0x5b) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    Offline surface scan supported.
                    Self-test supported.
                    No 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:      ( 373) minutes.
SCT capabilities:            (0x003d)    SCT Status supported.
                    SCT Error Recovery Control 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     0x000b   094   094   016    Pre-fail  Always       -       21
  2 Throughput_Performance  0x0005   139   139   054    Pre-fail  Offline      -       70
  3 Spin_Up_Time            0x0007   133   133   024    Pre-fail  Always       -       430 (Average 431)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       11
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   117   117   020    Pre-fail  Offline      -       36
  9 Power_On_Hours          0x0012   099   099   000    Old_age   Always       -       9708
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       11
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       18
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       18
194 Temperature_Celsius     0x0002   171   171   000    Old_age   Always       -       35 (Min/Max 23/43)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       8
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 15 (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 15 occurred at disk power-on lifetime: 9608 hours (400 days + 8 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 08 40 4c ae 06  Error: UNC at LBA = 0x06ae4c40 = 112086080

  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 10 d0 08 52 ae 40 00   1d+19:31:28.628  READ FPDMA QUEUED
  60 08 c8 40 4c ae 40 00   1d+19:31:28.628  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   1d+19:31:28.624  READ LOG EXT
  60 10 b8 08 52 ae 40 00   1d+19:31:24.984  READ FPDMA QUEUED
  60 08 b0 40 4c ae 40 00   1d+19:31:24.984  READ FPDMA QUEUED

Error 14 occurred at disk power-on lifetime: 9608 hours (400 days + 8 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 08 40 4c ae 06  Error: UNC at LBA = 0x06ae4c40 = 112086080

  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 10 b8 08 52 ae 40 00   1d+19:31:24.984  READ FPDMA QUEUED
  60 08 b0 40 4c ae 40 00   1d+19:31:24.984  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   1d+19:31:24.980  READ LOG EXT
  60 10 a0 08 52 ae 40 00   1d+19:31:21.299  READ FPDMA QUEUED
  60 08 98 40 4c ae 40 00   1d+19:31:21.299  READ FPDMA QUEUED

Error 13 occurred at disk power-on lifetime: 9608 hours (400 days + 8 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 08 40 4c ae 06  Error: UNC at LBA = 0x06ae4c40 = 112086080

  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 10 a0 08 52 ae 40 00   1d+19:31:21.299  READ FPDMA QUEUED
  60 08 98 40 4c ae 40 00   1d+19:31:21.299  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   1d+19:31:21.295  READ LOG EXT
  60 10 88 08 52 ae 40 00   1d+19:31:17.602  READ FPDMA QUEUED
  60 08 80 40 4c ae 40 00   1d+19:31:17.589  READ FPDMA QUEUED

Error 12 occurred at disk power-on lifetime: 9608 hours (400 days + 8 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 08 40 4c ae 06  Error: UNC at LBA = 0x06ae4c40 = 112086080

  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 10 88 08 52 ae 40 00   1d+19:31:17.602  READ FPDMA QUEUED
  60 08 80 40 4c ae 40 00   1d+19:31:17.589  READ FPDMA QUEUED
  60 08 78 48 2f ae 40 00   1d+19:31:17.589  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   1d+19:31:17.585  READ LOG EXT
  60 08 68 40 4c ae 40 00   1d+19:31:13.969  READ FPDMA QUEUED

Error 11 occurred at disk power-on lifetime: 9608 hours (400 days + 8 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 08 40 4c ae 06  Error: UNC at LBA = 0x06ae4c40 = 112086080

  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 08 68 40 4c ae 40 00   1d+19:31:13.969  READ FPDMA QUEUED
  60 08 60 48 2f ae 40 00   1d+19:31:13.969  READ FPDMA QUEUED
  60 20 58 70 fd ad 40 00   1d+19:31:13.969  READ FPDMA QUEUED
  60 08 50 10 fd ad 40 00   1d+19:31:13.969  READ FPDMA QUEUED
  60 08 48 a8 fc ad 40 00   1d+19:31:13.969  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

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.
 
P

Pitfrr

Wizard
Joined
Feb 10, 2014
Messages
1,531
Oh, no SMART tests since 17479 hours and now it is over 47k hours... that's a long stretch... :smile:


In your first message, the drive (SN xxxKJKS) had 8 pending sectors (#197) with 47426 hours power on (#9) and in your latest SMART output, the same drive has 0 pending sectors with 47458 hours power on (#9).
What happened in the meantime? Did you do something?
Might be worth to start a long SMART test... see how it turns out. They might have been cleared... But I'd be cautious.

The other drive (SN xxxPVKS) is showing 8 pending sectors (#197) and has no SMART tests logged so far.
It only has around 9k hours so it might still be under warranty? Worth to check and eventually see if an RMA is possible.
But I would also run a long SMART test and see what comes out.

Both disks show UNC errors so read errors... that's troubling indeed and I would check it out.
If these disks are part of a same pool, I would consider replacing them (and first make a backup if not done already). Especially if you have a RAIDz1 pool... That can be dangerous.
If they are used as backup disks or such then you might be more "tolerant" and not replace them at once but keep them under close monitoring. But this is really depending on how your backups are and it's also kind of a personal choice I'd say depending on your tolerance level.
 
JKman

JKman

Explorer
Joined
Mar 23, 2014
Messages
52
i dont know! perhaps was in the middle of a cron scheduled scrub or something...
 
You must log in or register to reply here.

Similar threads

angelus249
  • Locked
Not sure how to interpret SMART, please confirm
Replies
9
Views
3K
angelus249
angelus249
Q
Keep getting ATA errors, SMART seems fine
Replies
0
Views
726
quik
Q
E
SOLVED New WD Gold 12TBs in Lenovo SA120: ATA error count increased
Replies
18
Views
4K
eroji
E
R
  • Locked
ATA error count keeps increasing
Replies
5
Views
2K
Mr_N
Mr_N
N
  • Locked
Disk Failure?
Replies
5
Views
1K
nick3333
N
Top