Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Bad sectors disappeared after low level wipe


  • Please log in to reply
7 replies to this topic

#1 Shasoosh

Shasoosh

  • Members
  • 37 posts
  • OFFLINE
  •  
  • Local time:11:47 AM

Posted 27 June 2017 - 02:55 PM

My Windows 10 refused to copy some files to my WD Black 3TB drive. After scanning it with the "Data Lifeguard Diagnostic" software, I got a message saying "Too many bad sectors detected".
I did a full low level wipe, preparing it for RMA.
Now, after running the test above I get no errors.
I added a CrystalInfo before and after picture. The after picture contains no errors or info regarding previous errors. 
 
My question is, how is it possible that there's no evidence for the bad sectors that were found on the drive?
 
smartctl 6.5 2016-05-07 r4318 [x86_64-w64-mingw32-win10] (sf-6.5-1)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Black
Device Model:     WDC WD3003FZEX-00Z4SA0
Serial Number:    WD-WCC130713221
LU WWN Device Id: 5 0014ee 2b3486d20
Firmware Version: 01.01A01
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Tue Jun 27 22:53:44 2017 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:  (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: 		(32640) 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: 	 ( 354) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x7035)	SCT Status 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   200   196   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   216   138   021    Pre-fail  Always       -       8175
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       85
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   075   075   000    Old_age   Always       -       18294
 10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       68
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       45
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       39
194 Temperature_Celsius     0x0022   104   092   000    Old_age   Always       -       48
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test

Attached Files


Edited by Shasoosh, 27 June 2017 - 02:57 PM.


BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,629 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:47 AM

Posted 27 June 2017 - 03:03 PM

The bad sectors are still there but they were remapped. They were identified and the hd will no longer write to them and they should no longer be an issue.



#3 jwoods301

jwoods301

  • Members
  • 1,489 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:07:47 AM

Posted 27 June 2017 - 03:05 PM

Depends on whether they were soft sector (logical) or hard sector (physical) errors.

 

Soft sector errors are repairable.



#4 Shasoosh

Shasoosh
  • Topic Starter

  • Members
  • 37 posts
  • OFFLINE
  •  
  • Local time:11:47 AM

Posted 27 June 2017 - 03:10 PM

The bad sectors are still there but they were remapped. They were identified and the hd will no longer write to them and they should no longer be an issue.

 

Thanks, I understand this but if that's the case why the Reallocated sector count is still on zero?

 

 

Depends on whether they were soft sector (logical) or hard sector (physical) errors.

 

Soft sector errors are repairable.

 

I never heard that term. "Soft sector errors". Does that means the I can still trust the drive and shouldn't RMA it?



#5 JohnC_21

JohnC_21

  • Members
  • 24,434 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:47 AM

Posted 27 June 2017 - 03:13 PM

49 degrees Celsius is getting on the toasty side. The drive is rated to 55C though.

 

Hard vs Soft errors

 

https://www.howtogeek.com/173463/bad-sectors-explained-why-hard-drives-get-bad-sectors-and-what-you-can-do-about-it/


Edited by JohnC_21, 27 June 2017 - 03:14 PM.


#6 jwoods301

jwoods301

  • Members
  • 1,489 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:07:47 AM

Posted 27 June 2017 - 03:16 PM

I never heard that term. "Soft sector errors". Does that means the I can still trust the drive and shouldn't RMA it?
 

https://www.howtogeek.com/173463/bad-sectors-explained-why-hard-drives-get-bad-sectors-and-what-you-can-do-about-it/



#7 Shasoosh

Shasoosh
  • Topic Starter

  • Members
  • 37 posts
  • OFFLINE
  •  
  • Local time:11:47 AM

Posted 28 June 2017 - 01:42 PM

The drive was ok for half a day and then the Current Pending Sector warning returned.. I guess it wasn't that soft after all 



#8 jwoods301

jwoods301

  • Members
  • 1,489 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:07:47 AM

Posted 28 June 2017 - 02:00 PM

The drive was ok for half a day and then the Current Pending Sector warning returned.. I guess it wasn't that soft after all 

 

Do a full disk image of the hard drive.

 

Open a Command prompt and run chkdsk /r

 

If the numbers don't change, RMA it.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users