Weird smartmontools results

Ozy de Jong <[email protected]> Fri, 15 Apr 2016 18:42:45 +0200
Newsgroups gmane.linux.utilities.smartmontools
Message-ID <zarafa.57111a05.81a7.08236325135aca8a@kloud-server-39812>
Hello,



I use to fix some current pending sectors by running a smart extended test to get the LBA of the first bad sector, and then run a script like hdparm --write-sector.

I have some weird results here with an old velociraptor disk:



smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net <http://smartmontools.sourceforge.net> 

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD740HLFS-01G6U1
Serial Number:    WD-WXE0C79S9428
LU WWN Device Id: 5 0014ee 05738a981
Firmware Version: 04.04V02
User Capacity:    74 355 769 344 bytes [74,3 GB]
Sector Size:      512 bytes logical/physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Fri Apr 15 18:34:14 2016 CEST
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: ( 1200) 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: (  19) 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   188   188   051    Pre-fail  Always       -       374087
  3 Spin_Up_Time            0x0003   189   186   021    Pre-fail  Always       -       1516
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       206
  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   034   034   000    Old_age   Always       -       48629
 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       -       206
192 Power-Off_Retract_Count 0x0032   094   094   000    Old_age   Always       -       80109
193 Load_Cycle_Count        0x0032   174   174   000    Old_age   Always       -       80124
194 Temperature_Celsius     0x0022   115   101   000    Old_age   Always       -       28
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0012   138   138   000    Old_age   Always       -       753
198 Offline_Uncorrectable   0x0010   200   138   000    Old_age   Offline      -       0
200 Multi_Zone_Error_Rate   0x0008   200   188   000    Old_age   Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 48 (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 48 occurred at disk power-on lifetime: 48608 hours (2025 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
  -- -- -- -- -- -- --
  04 41 08 b7 f7 01 e0  Error: ABRT 8 sectors at LBA = 0x0001f7b7 = 128951

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 b7 f7 01 00 08  16d+00:48:07.703  READ DMA
  27 00 00 00 00 00 00 08  16d+00:48:07.703  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 00 08  16d+00:48:07.702  IDENTIFY DEVICE
  ef 03 42 00 00 00 00 08  16d+00:48:07.702  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 00 08  16d+00:48:07.701  READ NATIVE MAX ADDRESS EXT

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%     48628         -
# 2  Extended offline    Completed without error       00%     48623         -
# 3  Short offline       Completed without error       00%     48619         -
# 4  Short offline       Completed without error       00%     48595         -
# 5  Short offline       Completed without error       00%     48571         -
# 6  Short offline       Completed without error       00%     48547         -
# 7  Short offline       Completed without error       00%     48523         -
# 8  Short offline       Completed without error       00%     48499         -
# 9  Short offline       Completed without error       00%     48475         -
#10  Extended offline    Completed without error       00%     48456         -
#11  Short offline       Completed without error       00%     48452         -
#12  Short offline       Completed without error       00%     48428         -
#13  Short offline       Completed without error       00%     48404         -
#14  Short offline       Completed without error       00%     48380         -
#15  Short offline       Completed without error       00%     48356         -
#16  Short offline       Completed without error       00%     48332         -
#17  Short offline       Completed without error       00%     48308         -
#18  Extended offline    Completed without error       00%     48288         -
#19  Short offline       Completed without error       00%     48284         -
#20  Short offline       Completed without error       00%     48260         -
#21  Short offline       Completed without error       00%     48236         -

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.


First of all I know this is some archeology, as smartmontools v5.42 is stoneage, but I don't have anything better on CentOS 5 (yes, an old system still in production).
Well, the problem seems that there are 753 current pending sectors, but the extended test succeeds. Is that a normal behavior ? Honestly it is the first time since I use smartmontools since I see this kind of behavior.
Also, badblocks command doesn't find bad blocks either.
Is there a way to get a list of the bad sectors ?

Regards,



Orsiris de Jong

[email protected] - http://www.netpower.fr <http://www.netpower.fr> 

Tel: 06 75 40 48 41

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z

_______________________________________________
Smartmontools-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/smartmontools-support