Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
smartmontools - new errors after successful self-test
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
kai.scorpio
n00b
n00b


Joined: 01 Sep 2011
Posts: 46

PostPosted: Wed Sep 03, 2014 5:22 pm    Post subject: smartmontools - new errors after successful self-test Reply with quote

Hi all,

I would like some help interpreting the output of smartmontools (below).

I ran a short self-test followed by a long self-test. Both say they completed without errors, but before the short self-test the error log count was 4 (or maybe 5), and after it was around 50. After the long self-test it reported 72 errors (as below). I'm confused as to how this can happen when the tests complete successfully.

Code:

smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-32-generic] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital VelociRaptor
Device Model:     WDC WD1500HLFS-01G6U0
Serial Number:    WD-WXL209032471
LU WWN Device Id: 5 0014ee 0abfbf5c1
Firmware Version: 04.04V01
User Capacity:    150,039,945,216 bytes [150 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    10000 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.5, 3.0 Gb/s
Local Time is:    Wed Sep  3 17:56:35 2014 BST
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:       ( 2400) 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:     (  32) minutes.
Conveyance self-test routine
recommended polling time:     (   5) minutes.
SCT capabilities:           (0x303f)   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     0x000f   200   200   051    Pre-fail  Always       -       3905
  3 Spin_Up_Time            0x0003   205   199   021    Pre-fail  Always       -       2741
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       362
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   058   058   000    Old_age   Always       -       30860
 10 Spin_Retry_Count        0x0012   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0012   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       320
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       49
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       414
194 Temperature_Celsius     0x0022   113   107   000    Old_age   Always       -       34
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0012   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   200   200   000    Old_age   Offline      -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 72 (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 72 occurred at disk power-on lifetime: 30856 hours (1285 days + 16 hours)
  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 78 42 47 40  Error: UNC at LBA = 0x00474278 = 4670072

  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 b0 78 42 47 02 08  46d+17:12:25.980  READ FPDMA QUEUED
  60 38 a8 18 43 47 02 08  46d+17:12:25.975  READ FPDMA QUEUED
  60 18 a0 80 42 47 02 08  46d+17:12:25.968  READ FPDMA QUEUED
  60 18 98 c0 42 47 02 08  46d+17:12:25.967  READ FPDMA QUEUED
  60 08 90 98 42 47 02 08  46d+17:12:25.962  READ FPDMA QUEUED

Error 71 occurred at disk power-on lifetime: 30856 hours (1285 days + 16 hours)
  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 80 97 ca 40  Error: UNC at LBA = 0x00ca9780 = 13277056

  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 40 18 80 97 ca 01 08  46d+17:12:18.884  READ FPDMA QUEUED
  60 08 10 10 5d ca 01 08  46d+17:12:18.870  READ FPDMA QUEUED
  60 58 08 80 5d ca 01 08  46d+17:12:18.869  READ FPDMA QUEUED
  60 18 00 00 d8 c8 01 08  46d+17:12:18.861  READ FPDMA QUEUED
  60 08 e8 28 a6 cb 01 08  46d+17:12:18.860  READ FPDMA QUEUED

Error 70 occurred at disk power-on lifetime: 30856 hours (1285 days + 16 hours)
  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 00 73 11 40  Error: UNC at LBA = 0x00117300 = 1143552

  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 20 60 00 73 11 0f 08  46d+17:12:11.756  READ FPDMA QUEUED
  60 38 58 00 88 c7 01 08  46d+17:12:11.747  READ FPDMA QUEUED
  60 08 50 88 65 cb 01 08  46d+17:12:11.744  READ FPDMA QUEUED
  60 10 48 70 a6 cb 01 08  46d+17:12:11.742  READ FPDMA QUEUED
  60 28 40 60 9f cb 01 08  46d+17:12:11.738  READ FPDMA QUEUED

Error 69 occurred at disk power-on lifetime: 30856 hours (1285 days + 16 hours)
  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 28 4d cb 40  Error: UNC at LBA = 0x00cb4d28 = 13323560

  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 a0 28 4d cb 01 08  46d+17:12:04.602  READ FPDMA QUEUED
  60 50 98 00 9f cb 01 08  46d+17:12:04.597  READ FPDMA QUEUED
  60 10 90 90 65 cb 01 08  46d+17:12:04.589  READ FPDMA QUEUED
  60 18 88 58 a6 cb 01 08  46d+17:12:04.588  READ FPDMA QUEUED
  60 10 80 90 9f cb 01 08  46d+17:12:04.586  READ FPDMA QUEUED

Error 68 occurred at disk power-on lifetime: 30856 hours (1285 days + 16 hours)
  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 18 02 c4 40  Error: UNC at LBA = 0x00c40218 = 12845592

  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 10 18 02 c4 01 08  46d+17:11:57.314  READ FPDMA QUEUED
  60 10 08 20 56 28 03 08  46d+17:11:57.297  READ FPDMA QUEUED
  60 10 00 e0 74 c7 01 08  46d+17:11:57.288  READ FPDMA QUEUED
  60 20 f0 e0 5a c7 01 08  46d+17:11:57.267  READ FPDMA QUEUED
  60 08 e8 48 ea ca 01 08  46d+17:11:57.264  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%     30856         -
# 2  Short offline       Completed without error       00%     30855         -

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.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43383
Location: 56N 3W

PostPosted: Wed Sep 03, 2014 6:32 pm    Post subject: Reply with quote

kai.scorpio,

The long self test is like reading the entire drive to /dev/null
The errors indicate the the drive needed retries to read some sectors, possibly as many as 72.

However,
Code:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0012   200   200   000    Old_age   Always       -       0
shows that nothing has been reallocated yet and the drive does not want to reallocate anything either.

With 30860 hours on and 70 iffy sectors, I would not keep anything I could not afford to loose on that drive.

You may be able to force sector relocation by writing to the entire drive. This will destroy all the data on it.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
pa1983
Tux's lil' helper
Tux's lil' helper


Joined: 09 Jan 2004
Posts: 100

PostPosted: Sat Sep 06, 2014 1:33 am    Post subject: Reply with quote

I usually see those errors on drives with bad or pending sectors.
Never seen them otherwise. I would say its not normal.
If your lucky maybe its a bad sata cable. That can mess stuff up to.
Should be as simple as trying another on and rerun the test.
SMART can predict failures in about 2/3 of the cases so otherwise good SMART data is no guarantee theres no faults with the drive.

But 30K hours is 3.5 years of 24/7 running so it might just be dying. hard drives start to loose reliability after 3 years or so from the tests I have read that google and some other server owners did.
_________________
WS: i7 3930K@4Ghz, 32Gb ram, 256Gb NVME & 128Gb sata SSD, GTX780 3Gb & RX 460 2Gb
NAS: i3 4360 3.7Ghz, 20Gb ram, 256Gb SSD, 42Tb HDD, NIC: Intel 2x1Gbit
ROUTER: J1900 2Ghz, 8Gb ram, 128Gb SSD, NIC: 2x1Gbit, WIFI: Atheros AR9462 and AR5005G
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43383
Location: 56N 3W

PostPosted: Sat Sep 06, 2014 8:39 am    Post subject: Reply with quote

pa1983,

The SMART long test is entirely within the drive, so other that sending the command and retrieving the results, the SATA data cable is not used.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum