dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1686
share rss forum feed

o770

join:2002-06-12

[hard drive] SMART 197, pending sectors

Hello there. Smartmontools had this report for me that hasn't changed after a few of my procedures to remedy issue 197.

smartctl 5.43 2012-06-30 r3573 [i686-w64-mingw32-xp-sp3] (sf-5.43-1)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
 
=== START OF INFORMATION SECTION ===
Model Family:     Hitachi Travelstar 5K80
Device Model:     HTS548020M9AT00
Serial Number:    -
Firmware Version: MG1OA50A
User Capacity:    20.003.880.960 bytes [20,0 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   6
ATA Standard is:  ATA/ATAPI-6 T13 1410D revision 3a
Local Time is:    Fri Nov 23 16:31:19 2012 
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:      (   0)The previous self-test routine completed
without error or no self-test has ever 
been run.
Total time to complete Offline 
data collection: (  645) 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:  (  17) minutes.
 
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   100   100   062    Pre-fail  Always       -       65536
  2 Throughput_Performance  0x0005   100   100   040    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   186   186   033    Pre-fail  Always       -       1
  4 Start_Stop_Count        0x0012   098   098   000    Old_age   Always       -       4028
  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   100   100   040    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   082   082   000    Old_age   Always       -       8271
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   098   098   000    Old_age   Always       -       3897
191 G-Sense_Error_Rate      0x000a   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   098   098   000    Old_age   Always       -       471
193 Load_Cycle_Count        0x0012   083   083   000    Old_age   Always       -       178874
194 Temperature_Celsius     0x0002   110   110   000    Old_age   Always       -       50 (Min/Max 14/59)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       118
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       26
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: 4296 (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 4296 occurred at disk power-on lifetime: 8112 hours (338 days + 0 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
  -- -- -- -- -- -- --
  10 51 40 80 29 54 e2  Error: IDNF 64 sectors at LBA = 0x02542980 = 39070080
 
  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 40 80 29 54 e2 00      00:08:51.300  READ DMA
  ca 00 30 c7 90 5f e0 00      00:08:51.300  WRITE DMA
  c8 00 40 80 29 54 e2 00      00:08:51.200  READ DMA
  ca 00 04 07 07 01 e0 00      00:08:51.200  WRITE DMA
  ca 00 04 07 07 01 e0 00      00:08:51.200  WRITE DMA
 
Error 4295 occurred at disk power-on lifetime: 8112 hours (338 days + 0 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
  -- -- -- -- -- -- --
  10 51 40 80 29 54 e2  Error: IDNF 64 sectors at LBA = 0x02542980 = 39070080
 
  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 40 80 29 54 e2 00      00:08:51.200  READ DMA
  ca 00 04 07 07 01 e0 00      00:08:51.200  WRITE DMA
  ca 00 04 07 07 01 e0 00      00:08:51.200  WRITE DMA
  c8 00 40 80 29 54 e2 00      00:08:50.500  READ DMA
  c8 00 40 00 00 00 e0 00      00:08:50.500  READ DMA
 
Error 4294 occurred at disk power-on lifetime: 8112 hours (338 days + 0 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
  -- -- -- -- -- -- --
  10 51 40 80 29 54 e2  Error: IDNF 64 sectors at LBA = 0x02542980 = 39070080
 
  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 40 80 29 54 e2 00      00:08:50.500  READ DMA
  c8 00 40 00 00 00 e0 00      00:08:50.500  READ DMA
  c8 00 04 3f 00 00 e0 00      00:08:50.500  READ DMA
  c8 00 01 00 00 00 e0 00      00:08:50.500  READ DMA
  c8 00 01 00 00 00 e0 00      00:08:50.500  READ DMA
 
Error 4293 occurred at disk power-on lifetime: 8109 hours (337 days + 21 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
  -- -- -- -- -- -- --
  10 51 40 80 29 54 e2  Error: IDNF 64 sectors at LBA = 0x02542980 = 39070080
 
  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 40 80 29 54 e2 00      00:08:52.700  READ DMA
  c8 00 40 80 29 54 e2 00      00:08:52.700  READ DMA
  c8 00 40 80 29 54 e2 00      00:08:52.600  READ DMA
  c8 00 40 00 00 00 e0 00      00:08:52.600  READ DMA
  c8 00 04 3f 00 00 e0 00      00:08:52.600  READ DMA
 
Error 4292 occurred at disk power-on lifetime: 8109 hours (337 days + 21 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
  -- -- -- -- -- -- --
  10 51 40 80 29 54 e2  Error: IDNF 64 sectors at LBA = 0x02542980 = 39070080
 
  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 40 80 29 54 e2 00      00:08:52.700  READ DMA
  c8 00 40 80 29 54 e2 00      00:08:52.600  READ DMA
  c8 00 40 00 00 00 e0 00      00:08:52.600  READ DMA
  c8 00 04 3f 00 00 e0 00      00:08:52.600  READ DMA
  c8 00 08 91 23 04 e0 00      00:08:52.600  READ DMA
 
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%      8271         -
# 2  Extended offline    Completed without error       00%      8271         -
# 3  Short offline       Completed without error       00%      8054         -
# 4  Extended offline    Completed without error       00%      8053         -
# 5  Short offline       Completed without error       00%      5959         -
 
Warning! SMART Selective Self-Test Log Structure error: invalid SMART checksum.
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 I wanted the Pending Sectors remapped and did many things: CHKDSK /R, extended and short DST, DISKPART CLEAN ALL and finally Hitachi DFT ERASE DISK or zero-write followed by an automated 'sequential read of the entire disk to verify that all sectors have been initialised'.
Both attributes 196 and 197 remain the same. Both DST complete without error so does Hitachi tool.

How bad is that?
What else can I try?
Did I miss any other problem in the report?
Thanks!


koitsu
Premium,MVM
join:2002-07-16
Mountain View, CA
kudos:23
This drive needs to be replaced. It isn't in good shape, even remotely. I don't care what automated tools (DST, etc.) tell you -- the drive is heading downhill. RMA it ASAP, and restore your data from backups (since at this point potentially 118*512 + 26*512 = 73728 bytes of data are either potentially lost or are definitely lost).

The last error encountered by the drive was at 8112 power-on hours, which is roughly 150 hours ago. But despite that fact, my above statement stands.

SMART attribute 197 indicates, by the way, there are 26 "suspect" LBAs on the drive. The only way to get the drive to re-analyse those (to determine if they're bad or good) is to issue a write to them. Whether the remap happens or not, the data you write obviously overwrites the existing data.

But given the health of the drive at this point (and for such a short lifetime), RMA it. The situation is going to get worse as time goes on. There's nothing else for you to do, honestly -- RMA it, or if you can't RMA it, replace it.
--
Making life hard for others since 1977.
I speak for myself and not my employer/affiliates of my employer.

o770

join:2002-06-12

1 edit
All right, thanks a lot koitsu! I'm getting a new one.