What does this SMART error report tells?


Recommended Posts

Can somebody tells me what this means? What should I do?

 

Its an external drive mount with unassigned device

 

smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.4.30-unRAID] (local build)

Copyright © 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

 

=== START OF INFORMATION SECTION ===

Model Family:    Seagate Samsung SpinPoint M8 (AF)

Device Model:    ST1000LM024 HN-M101MBB

Serial Number:    S2ZPJ9BD326991

LU WWN Device Id: 5 0004cf 209e489b8

Firmware Version: 2AR20002

User Capacity:    1,000,204,886,016 bytes [1.00 TB]

Sector Sizes:    512 bytes logical, 4096 bytes physical

Rotation Rate:    5400 rpm

Form Factor:      2.5 inches

Device is:        In smartctl database [for details use: -P show]

ATA Version is:  ATA8-ACS T13/1699-D revision 6

SATA Version is:  SATA 3.0, 3.0 Gb/s (current: 3.0 Gb/s)

Local Time is:    Fri Dec 30 21:40:58 2016 SGT

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:  (0x00) Offline data collection activity

was never started.

Auto Offline Data Collection: Disabled.

Self-test execution status:      ( 121) The previous self-test completed having

the read element of the test failed.

Total time to complete Offline

data collection: (12600) 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: (  2) minutes.

Extended self-test routine

recommended polling time: ( 210) minutes.

SCT capabilities:       (0x003f) 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    0x002f  100  100  051    Pre-fail  Always      -      96819

  2 Throughput_Performance  0x0026  252  252  000    Old_age  Always      -      0

  3 Spin_Up_Time            0x0023  086  085  025    Pre-fail  Always      -      4467

  4 Start_Stop_Count        0x0032  098  098  000    Old_age  Always      -      2538

  5 Reallocated_Sector_Ct  0x0033  252  252  010    Pre-fail  Always      -      0

  7 Seek_Error_Rate        0x002e  252  252  051    Old_age  Always      -      0

  8 Seek_Time_Performance  0x0024  252  252  015    Old_age  Offline      -      0

  9 Power_On_Hours          0x0032  100  100  000    Old_age  Always      -      18207

10 Spin_Retry_Count        0x0032  252  252  051    Old_age  Always      -      0

11 Calibration_Retry_Count 0x0032  100  100  000    Old_age  Always      -      16

12 Power_Cycle_Count      0x0032  099  099  000    Old_age  Always      -      1084

191 G-Sense_Error_Rate      0x0022  100  100  000    Old_age  Always      -      3

192 Power-Off_Retract_Count 0x0022  252  252  000    Old_age  Always      -      0

194 Temperature_Celsius    0x0002  058  046  000    Old_age  Always      -      42 (Min/Max 21/59)

195 Hardware_ECC_Recovered  0x003a  100  100  000    Old_age  Always      -      0

196 Reallocated_Event_Count 0x0032  252  252  000    Old_age  Always      -      0

197 Current_Pending_Sector  0x0032  100  100  000    Old_age  Always      -      77

198 Offline_Uncorrectable  0x0030  252  252  000    Old_age  Offline      -      0

199 UDMA_CRC_Error_Count    0x0036  200  200  000    Old_age  Always      -      0

200 Multi_Zone_Error_Rate  0x002a  100  100  000    Old_age  Always      -      14896

223 Load_Retry_Count        0x0032  100  100  000    Old_age  Always      -      16

225 Load_Cycle_Count        0x0032  090  090  000    Old_age  Always      -      101083

 

SMART Error Log Version: 1

No Errors Logged

 

SMART Self-test log structure revision number 1

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error

# 1  Short offline      Completed: read failure      90%    17978        5960440

# 2  Short offline      Completed: read failure      10%    17347        1081298632

 

SMART Selective self-test log data structure revision number 0

Note: revision number not 1 implies that no selective self-test has ever been run

SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS

    1        0        0  Completed_read_failure [90% left] (0-65535)

    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.

 

Link to comment

You could run three preclear cycles on it.  After the first pass, the Pending Sectors count should be zero and stay there during the next two cycles.  At the same time, the Relocated Sector count should go to 77  after the first cycle and be unchanged in the next two cycles. 

 

If this scenario is what happens, you could consider using it depending on your tolerance for risk.  Hard disk manufacturers provide for a pool of spare sectors for those that becoming difficult to read.  When a sector is so marked (i.e., 'Pending'), the next time it is to be written to, a new sector will be seamlessly swapped in for it.  (Some folks here have had very satisfactory service from drives with this type of problem.  Others will swap out any drive as soon as it shows any problem.  The choice is yours...)  What you have to realize is that unRAID must be able to read every sector on every drive when it is rebuilding  a failed drive.  In most other uses, if theses type of sectors are unused for actual storage, they never will cause a problem.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.