Reset S.M.A.R.T. Reallocated Sector Count

LynxKepler

Honorable
Nov 2, 2013
7
0
10,510
Hi,
Question: how do I erase/reset/reflash S.M.A.R.T.'s data on bad sectors?

The story so far:
I have a 4-year old Toshiba MK3255GSX Hard Drive with some ~50 bad blocks pending reallocation. These are mostly located in the first 75 gigabytes (sectors ~250~18000000-something). My idea is to repartition the HDD, leaving the first 75 gigabytes unallocated and allocate a new NTFS partition in the remaining "good" parts of the disk. This was already done. I have no data to recover.

The problem is S.M.A.R.T.'s "Reallocated_Sector_Ct" && "Current_Pending_Sector". I know the drive does automatically reallocate bad sectors and can only reallocate so many of these. But since it has already reallocated all it could reallocate, any new bad blocks on the new NTFS partition will be left un-reallocated, which is unacceptable.

But since I intend to leave the bad sectors in an non-partitioned part of the disk (the first 75 gb), I don't want S.M.A.R.T. to bother with these.

So, I want some guidance to run a procedure, be it reflashing the HDD, or any clever S.M.A.R.T. (re-)configuration or something else (I don't know how to accomplish this) to reset/free the reallocated sectors and start over with the remaining parts of the disk.

Do you know how can it be done?
Which tools are likely to be useful to reset SMART?
Is it likely that SMART will dumbly spent all reallocation space reallocating again the bad blocks from the non-partitioned space, leaving the partitioned space vulnerable to bad blocks once again?

Thanks for your consideration and input.

P.S.: smartctl -a /dev/sda output:
Code:
smartctl -a /dev/sda
smartctl 5.43 2012-06-30 r3573 [i686-linux-3.6.10-4.fc18.i686] (local build)
Copyright (C) 2002-12 by Bruce Allen, [url=http://smartmontools.sourceforge.net]http://smartmontools.sourceforge.net[/url]

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 2.5" HDD MK..55GSX
Device Model:     TOSHIBA MK3255GSX
Serial Number:    69TKC0BKT
LU WWN Device Id: 5 000039 1d3c8165a
Firmware Version: FG011M
User Capacity:    320,072,933,376 bytes [320 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Sun Nov  3 14:34:30 2013 EST
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:      ( 112)	The previous self-test completed having
					the read element of the test failed.
Total time to complete Offline 
data collection: 		(  120) 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: 	 ( 146) minutes.
SCT capabilities: 	       (0x0039)	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   100   098   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail  Always       -       1226
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       3391
  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail  Always       -       4
  7 Seek_Error_Rate         0x000b   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   073   073   000    Old_age   Always       -       10857
 10 Spin_Retry_Count        0x0033   167   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       3291
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       3075
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       62
193 Load_Cycle_Count        0x0032   098   098   000    Old_age   Always       -       28096
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       44 (Min/Max 20/57)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       4
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       33
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       34
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       8327
222 Loaded_Hours            0x0032   078   078   000    Old_age   Always       -       8827
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
224 Load_Friction           0x0022   100   100   000    Old_age   Always       -       0
226 Load-in_Time            0x0026   100   100   000    Old_age   Always       -       331
240 Head_Flying_Hours       0x0001   100   100   001    Pre-fail  Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 27665 (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 27665 occurred at disk power-on lifetime: 10856 hours (452 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 41 02 10 c9 83 68  Error: UNC at LBA = 0x0883c910 = 142854416

  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 00 10 c9 83 40 08      17:51:17.977  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      17:51:17.977  SET FEATURES [Reserved for Serial ATA]
  27 00 00 00 00 00 e0 00      17:51:17.977  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      17:51:17.976  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      17:51:17.976  SET FEATURES [Set transfer mode]

Error 27664 occurred at disk power-on lifetime: 10856 hours (452 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 41 02 10 c9 83 68  Error: UNC at LBA = 0x0883c910 = 142854416

  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 00 10 c9 83 40 08      17:51:14.132  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      17:51:14.132  SET FEATURES [Reserved for Serial ATA]
  27 00 00 00 00 00 e0 00      17:51:14.132  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      17:51:14.131  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      17:51:14.131  SET FEATURES [Set transfer mode]

Error 27663 occurred at disk power-on lifetime: 10856 hours (452 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 41 02 10 c9 83 68  Error: UNC at LBA = 0x0883c910 = 142854416

  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 00 10 c9 83 40 08      17:51:10.288  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      17:51:10.287  SET FEATURES [Reserved for Serial ATA]
  27 00 00 00 00 00 e0 00      17:51:10.287  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      17:51:10.287  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      17:51:10.287  SET FEATURES [Set transfer mode]

Error 27662 occurred at disk power-on lifetime: 10856 hours (452 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 41 02 10 c9 83 68  Error: UNC at LBA = 0x0883c910 = 142854416

  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 00 10 c9 83 40 08      17:51:06.482  READ FPDMA QUEUED
  60 08 00 08 c9 83 40 08      17:51:06.482  READ FPDMA QUEUED
  60 08 00 00 c9 83 40 08      17:51:06.482  READ FPDMA QUEUED
  60 08 00 f8 c8 83 40 08      17:51:06.481  READ FPDMA QUEUED
  60 08 00 f0 c8 83 40 08      17:51:06.481  READ FPDMA QUEUED

Error 27661 occurred at disk power-on lifetime: 10856 hours (452 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 41 02 30 6d 83 68  Error: UNC at LBA = 0x08836d30 = 142830896

  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 00 30 6d 83 40 08      17:50:54.965  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      17:50:54.964  SET FEATURES [Reserved for Serial ATA]
  27 00 00 00 00 00 e0 00      17:50:54.964  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      17:50:54.964  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      17:50:54.964  SET FEATURES [Set transfer mode]

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       00%     10843         0
# 2  Short offline       Completed: read failure       00%     10838         2060
# 3  Short offline       Aborted by host               90%     10838         -
# 4  Extended captive    Interrupted (host reset)      90%     10807         -
# 5  Extended offline    Aborted by host               90%     10807         -
# 6  Extended offline    Interrupted (host reset)      90%     10764         -
# 7  Extended offline    Interrupted (host reset)      90%     10764         -
# 8  Extended offline    Interrupted (host reset)      90%     10746         -
# 9  Short offline       Completed without error       00%     10741         -
#10  Extended offline    Interrupted (host reset)      90%     10740         -

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.
 
Solution
With that many pending sectors it will just get worse FAST.

Cut your losses and replace the drive.

The drive will reallocate when it is next using those pending sectors in most cases(they may stay pending forever if the drive never has to go over that section, but this varies from drive to drive).

I would not risk anything on a drive in that state to be honest and I do not think users can edit the smart data on the drive.
With that many pending sectors it will just get worse FAST.

Cut your losses and replace the drive.

The drive will reallocate when it is next using those pending sectors in most cases(they may stay pending forever if the drive never has to go over that section, but this varies from drive to drive).

I would not risk anything on a drive in that state to be honest and I do not think users can edit the smart data on the drive.
 
Solution


This right here. With that many bad sectors already remapped it will most likely fail completely within the next 12 months.
 


This drive is only for non-critical applications, so it's not like somebody's life depend on it. I'm not an expert on SMART, but as I see it, on SMART data only 4 sectors were (sucessfully) reallocated, the rest is "pending reallocation", that means that either the HDD couldn't reallocate or didn't try to reallocate (because I've decided not to read or write data on these sectors). So, if I don't use the "bad areas" of the disk, am I likely to get away with it? Or do you see this SMART report as a death sentence?

Anyway, I wish I could just reset the SMART data to continue using the "good" parts of the disk, just to see how far it lasts. Any thoughts on this one?
 


The whole idea here is not to read from bad sectors in the first place. Avoid them, leave them in the non-partitioned space.

Reseting SMART was seen as a way of re-using the remap sectors.
Thanks for the input.
 


I did it with linux's "badblocks", so I found some bad sectors limited to the first ~75 gb. Usually these "bad sectors" are magnetic anomalies caused by overuse of the disk surface, like millions of reads and re-writes on a frequently used file, so I'm not inclined to assume of the bad blocks will be causing a head crash just by hovering over them.
 


Well, after spending the weekend, I decided to put set aside my (unsettled) feud with the SMART and just leave the first 75 GB unallocated. I'll keep posting if anything else happens. Windows 7 CHKDSK found no bad blocks so far:

Code:
Checking file system on C:
The type of the file system is NTFS.
Volume label is MK3255GSX.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  65792 file records processed.                                          File verification completed.
  73 large file records processed.                                      0 bad file records processed.                                        2 EA records processed.                                              44 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  87916 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  65792 file SDs/SIDs processed.                                         Cleaning up 151 unused index entries from index $SII of file 0x9.
Cleaning up 151 unused index entries from index $SDH of file 0x9.
Cleaning up 151 unused security descriptors.
Security descriptor verification completed.
  11063 data files processed.                                            CHKDSK is verifying Usn Journal...
  35196640 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  65776 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  55310537 free clusters processed.                                         Free space verification is complete.
Windows has checked the file system and found no problems.

 235088895 KB total disk space.
  13632596 KB in 53157 files.
     40044 KB in 11064 indexes.
         0 KB in bad sectors.
    174103 KB in use by the system.
     65536 KB occupied by the log file.
 221242152 KB available on disk.

      4096 bytes in each allocation unit.
  58772223 total allocation units on disk.
  55310538 allocation units available on disk.

Internal Info:
00 01 01 00 e8 fa 00 00 fa fa 01 00 00 00 00 00  ................
49 00 00 00 2c 00 00 00 00 00 00 00 00 00 00 00  I...,...........
f8 89 32 00 50 01 31 00 b8 18 31 00 00 00 31 00  ..2.P.1...1...1.

Windows has finished checking your disk.
Please wait while your computer restarts.

If I can indulge in some conspiracy thinking, I might add that I consider this (very) limited "realloc" table a big Planned Obsolescence scam from the manufacturers. It costs next to nothing to reserve 1GB on the platter or even add a 1GB flash memory to remap bad sectors to. I hope that the new Hybrid SSHD drives do exactly this and keep operating even with thousands of bad blocks.
 


My test says Current:1 Worst:1 Threshold:50 is that a need to replace mine as well?


----------------------------------------------------------------------------
CrystalDiskInfo 6.1.10 (C) 2008-2014 hiyohiyo
Crystal Dew World : http://crystalmark.info/
----------------------------------------------------------------------------

OS : Windows 8.1 Pro [6.3 Build 9600] (x64)
Date : 2014/04/09 12:30:06

-- Controller Map ----------------------------------------------------------
+ Standard SATA AHCI Controller [ATA]
- TOSHIBA MK5065GSX
- TSSTcorp CDDVDW TS-L633F
- Microsoft Storage Spaces Controller [SCSI]

-- Disk List ---------------------------------------------------------------
(1) TOSHIBA MK5065GSX : 500.1 GB [0/0/0, pd1]

----------------------------------------------------------------------------
(1) TOSHIBA MK5065GSX
----------------------------------------------------------------------------
Model : TOSHIBA MK5065GSX
Firmware : GJ003M
Serial Number : *********
Disk Size : 500.1 GB (8.4/137.4/500.1/500.1)
Buffer Size : 8192 KB
Queue Depth : 32
# of Sectors : 976773168
Rotation Rate : 5400 RPM
Interface : Serial ATA
Major Version : ATA8-ACS
Minor Version : ----
Transfer Mode : SATA/300 | SATA/300
Power On Hours : 395 hours
Power On Count : 301 count
Temperature : 36 C (96 F)
Health Status : Bad
Features : S.M.A.R.T., APM, 48bit LBA, NCQ
APM Level : 0080h [ON]
AAM Level : ----

-- S.M.A.R.T. --------------------------------------------------------------
ID Cur Wor Thr RawValues(6) Attribute Name
01 100 100 _50 000000000000 Read Error Rate
02 100 100 _50 000000000000 Throughput Performance
03 100 100 __1 00000000084F Spin-Up Time
04 100 100 __0 00000000013E Start/Stop Count
05 __1 __1 _50 0000000007FF Reallocated Sectors Count
07 100 100 _50 000000000000 Seek Error Rate
08 100 100 _50 000000000000 Seek Time Performance
09 100 100 __0 00000000018B Power-On Hours
0A 106 100 _30 000000000000 Spin Retry Count
0C 100 100 __0 00000000012D Power Cycle Count
BF 100 100 __0 000000000002 G-Sense Error Rate
C0 100 100 __0 000000000016 Power-off Retract Count
C1 100 100 __0 0000000010F4 Load/Unload Cycle Count
C2 100 100 __0 002A00100024 Temperature
C4 100 100 __0 000000000193 Reallocation Event Count
C5 100 100 __0 000000000000 Current Pending Sector Count
C6 100 100 __0 000000000000 Uncorrectable Sector Count
C7 200 200 __0 000000000000 UltraDMA CRC Error Count
DC 100 100 __0 00000000002D Disk Shift
DE 100 100 __0 00000000014A Loaded Hours
DF 100 100 __0 000000000000 Load/Unload Retry Count
E0 100 100 __0 000000000000 Load Friction
E2 100 100 __0 000000000150 Load 'In'-time
F0 100 100 __1 000000000000 Head Flying Hours

-- IDENTIFY_DEVICE ---------------------------------------------------------
0 1 2 3 4 5 6 7 8 9
000: 0040 3FFF C837 0010 0000 0000 003F 0000 0000 0000 .@?..7.......?......
010: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 4D42 ..................MB
020: 0000 4000 0000 474A 3030 334D 2020 544F 5348 4942 ..@...GJ003M TOSHIB
030: 4120 4D4B 3530 3635 4753 5820 2020 2020 2020 2020 A MK5065GSX
040: 2020 2020 2020 2020 2020 2020 2020 8010 0000 2F00 ..../.
050: 4000 0200 0000 0007 3FFF 0010 003F FC10 00FB 0110 @.......?....?......
060: FFFF 0FFF 0007 0407 0003 0078 0078 0078 0078 0000 ...........x.x.x.x..
070: 0000 0000 0000 0000 0000 001F 0F06 0004 004C 0040 .................L.@
080: 01F8 0000 746B 7D09 6163 7469 BC09 6163 003F 0052 ....tk}.acti..ac.?.R
090: 0052 0080 FFFE 0000 0000 0000 0000 0000 0000 0000 .R..................
100: 6030 3A38 0000 0000 0000 0000 4000 0000 5000 0392 `0:8........@...P...
110: B928 6DDA 0000 0000 0000 0000 0000 0000 0000 4018 .(m...............@.
120: 4018 0000 0000 0000 0000 0000 0000 0000 0029 0000 @................)..
130: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 ....................
140: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 ....................
150: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 ....................
160: 0000 0000 0000 0000 0000 0000 0000 0000 0003 0000 ....................
170: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 ....................
180: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 ....................
190: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 ....................
200: 0000 0000 0000 0000 0000 0000 003D 0000 0000 0000 .............=......
210: 0000 0000 0000 0000 0000 0000 0000 1518 0000 0000 ....................
220: 0000 0000 101F 0000 0000 0000 0000 0000 0000 0000 ....................
230: 0000 0000 0000 0000 0001 0080 0000 0000 0000 0000 ....................
240: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 ....................
250: 0000 0000 0000 0000 0000 05A5 ............

-- SMART_READ_DATA ---------------------------------------------------------
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
000: 10 00 01 0B 00 64 64 00 00 00 00 00 00 00 02 05 .....dd.........
010: 00 64 64 00 00 00 00 00 00 00 03 27 00 64 64 4F .dd........'.ddO
020: 08 00 00 00 00 00 04 32 00 64 64 3E 01 00 00 00 .......2.dd>....
030: 00 00 05 33 00 01 01 FF 07 00 00 00 00 00 07 0B ...3............
040: 00 64 64 00 00 00 00 00 00 00 08 05 00 64 64 00 .dd..........dd.
050: 00 00 00 00 00 00 09 32 00 64 64 8B 01 00 00 00 .......2.dd.....
060: 00 00 0A 33 00 6A 64 00 00 00 00 00 00 00 0C 32 ...3.jd........2
070: 00 64 64 2D 01 00 00 00 00 00 BF 32 00 64 64 02 .dd-.......2.dd.
080: 00 00 00 00 00 00 C0 32 00 64 64 16 00 00 00 00 .......2.dd.....
090: 00 00 C1 32 00 64 64 F4 10 00 00 00 00 00 C2 22 ...2.dd........"
0A0: 00 64 64 24 00 10 00 2A 00 00 C4 32 00 64 64 93 .dd$...*...2.dd.
0B0: 01 00 00 00 00 00 C5 32 00 64 64 00 00 00 00 00 .......2.dd.....
0C0: 00 00 C6 30 00 64 64 00 00 00 00 00 00 00 C7 32 ...0.dd........2
0D0: 00 C8 C8 00 00 00 00 00 00 00 DC 02 00 64 64 2D .............dd-
0E0: 00 00 00 00 00 00 DE 32 00 64 64 4A 01 00 00 00 .......2.ddJ....
0F0: 00 00 DF 32 00 64 64 00 00 00 00 00 00 00 E0 22 ...2.dd........"
100: 00 64 64 00 00 00 00 00 00 00 E2 26 00 64 64 50 .dd........&.ddP
110: 01 00 00 00 00 00 F0 01 00 64 64 00 00 00 00 00 .........dd.....
120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
160: 00 00 00 00 00 00 00 00 00 00 00 00 78 00 00 5B ............x..[
170: 03 00 01 00 02 AF 00 00 00 00 00 00 00 00 00 00 ................
180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
1C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 63 ...............c

-- SMART_READ_THRESHOLD ----------------------------------------------------
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
000: 10 00 01 32 00 00 00 00 00 00 00 00 00 00 02 32 ...2...........2
010: 00 00 00 00 00 00 00 00 00 00 03 01 00 00 00 00 ................
020: 00 00 00 00 00 00 04 00 00 00 00 00 00 00 00 00 ................
030: 00 00 05 32 00 00 00 00 00 00 00 00 00 00 07 32 ...2...........2
040: 00 00 00 00 00 00 00 00 00 00 08 32 00 00 00 00 ...........2....
050: 00 00 00 00 00 00 09 00 00 00 00 00 00 00 00 00 ................
060: 00 00 0A 1E 00 00 00 00 00 00 00 00 00 00 0C 00 ................
070: 00 00 00 00 00 00 00 00 00 00 BF 00 00 00 00 00 ................
080: 00 00 00 00 00 00 C0 00 00 00 00 00 00 00 00 00 ................
090: 00 00 C1 00 00 00 00 00 00 00 00 00 00 00 C2 00 ................
0A0: 00 00 00 00 00 00 00 00 00 00 C4 00 00 00 00 00 ................
0B0: 00 00 00 00 00 00 C5 00 00 00 00 00 00 00 00 00 ................
0C0: 00 00 C6 00 00 00 00 00 00 00 00 00 00 00 C7 00 ................
0D0: 00 00 00 00 00 00 00 00 00 00 DC 00 00 00 00 00 ................
0E0: 00 00 00 00 00 00 DE 00 00 00 00 00 00 00 00 00 ................
0F0: 00 00 DF 00 00 00 00 00 00 00 00 00 00 00 E0 00 ................
100: 00 00 00 00 00 00 00 00 00 00 E2 00 00 00 00 00 ................
110: 00 00 00 00 00 00 F0 01 00 00 00 00 00 00 00 00 ................
120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
1C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 36 ...............6



 
Your re-allocated seems to be at 2047 so yes you should backup your files(external drive/optical/usb) ASAP and get the drive replaced.

By this point your system should be warning you to replace the drive as well.

You also have logged 2 g-sense events(this is honestly not high compared to my sensitive western digital drive. upto 501 of those in a DESKTOP[worst it should see is some music vibration]. They offered to RMA over it, but a quick search shows those drives to just have a hair trigger.) At some point the system may have been subjected to some form of shock while operating.

For future Reference, You should post a new thread for this type of question because this one has become rather old and people may come and reply to the first post and not even notice yours.
 


Thank You so much for the timely response. And the pointers, I just bought this drive so I guess I shall send it back. Curious how long do you think it'll last me? Oh and yes the system is notifying me hence my checking it.
=(
 
Most hard drives last at least a few years(many will last more I still have 2 Western Digital Black(640gigabyte) that are used quite a bit. It was 3, but one did actually start to fail, but I got plenty of warning to backup and get it replaced under warranty.).

I still have a laptop drive that is 60 gigabytes, but it is not used much these days.

The real kicker is an old Maxtor 15 gigabyte IDE that is still working. It also sees very little use now days.

Unfortunately with hard drives, it is kind of a luck game(I honestly have so many drives that I retire just because they are too small for my needs so in general they last while.).
 


Oh those were the days eh. They seemed to have worked longer back then lol. I contacted the seller and he's willing to replace it so I don't have to worry after all. Here's hoping that he uses the diagnostic tool prior to this shipment... Thanks so so much for your help I much appreciate it. :)

 


Sorry to bother you again nuke, the dealer is asking me what is acceptable bad sectors assuming used 2.5 sata hhd like the last one? I don't know much about this and would love your feedback. Thanks in advance.
 
I would say as low as possible. I do not use drives with any bad sectors personally.

Generally, by the time you start to get some many more will follow.

The driver makers have a point that they will warn you. The threshold for the drive is 50, but I am not sure how many actual remapped sectors triggers how many of that 50.

For example. I have an SSD and it has 23 full write cycles, but that has not yet become enough to trigger even a single percentage number of its rated lifetime. Only the drive makers know for sure and I do not think they disclose it.

In general even a used drive should not have any actual signs of future failure(so no values should be triggered and I would not even give away a drive with pending or reallocated sectors.) to avoid issues in the short term.
 


So the values should be Current:0 Worst:0 Threshold:0? Or can I ask him to send me the results and have you look at them? I thought I had seen private messaging on here or am I mistaken? I'd hate to fill this thread up with my none understanding heheh... Sorry, I'm trying to understand this stuff lol.
 
Get them to show you the current status.

The threshold is the number that the drive will start to warn the computer it is failing at(it varies from drive to drive).

Current is what it is at right now(for some attributes this number resets with the system).

Worst is the lowest recorded number(stays even after a reboot.).

RAW is a hex number that keeps track of all changes, it does not always make human sense. This is all down the drive makers firmware.

The ones you want to see no raw value in are re-allocated, pending sector.

Example Image.
f1z6ok.png
 


With 4 remapped sectors and 33 pending, that drive was in bad shape. I'll bet it got a lot worse within 12 weeks, not months.

It's now been 13 months. Am I right, LynxKepler? How long was it before you ended up scrapping that drive?