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

Hard Drive gone bad, is it fixable?


  • Please log in to reply
1 reply to this topic

#1 ImTHATGuy

ImTHATGuy

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:01:55 PM

Posted 10 October 2014 - 10:04 PM

Hey, everybody! My Hard Drive crashed a few weeks ago, so I put in a new hard drive and the old bad one wasn't even getting recognized on my computer. Almost like it wasn't even there. Anyways, I don't know what I was thinking, but I left the bad one plugged in and everything. Fast forward to today, I turned my computer on and it booted from the old hard drive. It still gives the "Hard drive going bad" error, but I was wondering if there was anyway to fix it. 

 

I read somewhere that I needed the Smartctl Output from GSmartControl, so here it is!: 

smartctl 5.43 2012-06-30 r3573 [i686-w64-mingw32-win7(64)-sp1] (sf-5.43-1)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital AV SATA
Device Model:     WDC WD3200AVJS-63WDA0
Serial Number:    WD-WCARW5233997
LU WWN Device Id: 5 0014ee 1563e642a
Firmware Version: 12.01B02
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:    Fri Oct 10 21:48:24 2014 CDT
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: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
See vendor-specific Attribute list for failed Attributes.

General SMART Values:
Offline data collection status:  (0x84)	Offline data collection activity
					was suspended by an interrupting command from host.
					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: 		( 8760) 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: 	 ( 104) 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   001   001   051    Pre-fail  Always   FAILING_NOW 153880
  3 Spin_Up_Time            0x0003   184   155   021    Pre-fail  Always       -       3775
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       287
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000e   200   200   051    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       653
 10 Spin_Retry_Count        0x0012   100   100   051    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0012   100   100   051    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       156
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       38
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       166
194 Temperature_Celsius     0x0022   108   101   000    Old_age   Always       -       39
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0012   200   200   000    Old_age   Always       -       15
198 Offline_Uncorrectable   0x0010   200   200   000    Old_age   Offline      -       8
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   001   001   051    Old_age   Offline  FAILING_NOW 91704

SMART Error Log Version: 1
ATA Error Count: 5
	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 5 occurred at disk power-on lifetime: 556 hours (23 days + 4 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
  -- -- -- -- -- -- --
  01 51 e0 c0 1c de e0  Error: AMNF 224 sectors at LBA = 0x00de1cc0 = 14556352

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 e0 c0 1c de 12 00   2d+05:16:58.917  READ DMA EXT
  35 00 30 50 6d 05 08 00   2d+05:16:58.917  WRITE DMA EXT
  25 00 30 50 3e 7e 04 00   2d+05:16:58.914  READ DMA EXT
  35 00 d0 80 6c 05 08 00   2d+05:16:58.914  WRITE DMA EXT
  25 00 d0 28 0e 7e 04 00   2d+05:16:58.898  READ DMA EXT

Error 4 occurred at disk power-on lifetime: 496 hours (20 days + 16 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
  -- -- -- -- -- -- --
  01 51 00 18 f5 e6 e0  Error: AMNF at LBA = 0x00e6f518 = 15136024

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 00 18 f5 e6 10 00      13:07:24.605  READ VERIFY SECTOR(S) EXT
  42 00 00 18 f4 e6 10 00      13:07:24.603  READ VERIFY SECTOR(S) EXT
  42 00 00 18 f3 e6 10 00      13:07:24.602  READ VERIFY SECTOR(S) EXT
  42 00 00 18 f2 e6 10 00      13:07:24.599  READ VERIFY SECTOR(S) EXT
  42 00 00 18 f1 e6 10 00      13:07:24.597  READ VERIFY SECTOR(S) EXT

Error 3 occurred at disk power-on lifetime: 487 hours (20 days + 7 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
  -- -- -- -- -- -- --
  01 51 80 00 5e c3 e0  Error: AMNF 128 sectors at LBA = 0x00c35e00 = 12803584

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 80 00 5e c3 12 00      03:53:32.290  READ DMA EXT
  25 00 80 80 5d c3 12 00      03:53:32.289  READ DMA EXT
  25 00 80 00 5d c3 12 00      03:53:32.289  READ DMA EXT
  25 00 80 80 5c c3 12 00      03:53:32.288  READ DMA EXT
  25 00 80 00 5c c3 12 00      03:53:32.287  READ DMA EXT

Error 2 occurred at disk power-on lifetime: 472 hours (19 days + 16 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
  -- -- -- -- -- -- --
  01 51 20 60 dd 5e e0  Error: AMNF 32 sectors at LBA = 0x005edd60 = 6217056

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 20 60 dd 5e 00 00      01:46:38.954  READ DMA EXT
  35 00 20 a0 ec 22 14 00      01:46:38.953  WRITE DMA EXT
  35 00 20 60 d3 22 14 00      01:46:38.953  WRITE DMA EXT
  25 00 08 38 f3 6b 00 00      01:46:38.953  READ DMA EXT
  35 00 08 88 dd 5e 00 00      01:46:38.953  WRITE DMA EXT

Error 1 occurred at disk power-on lifetime: 222 hours (9 days + 6 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 00 c0 5d 23 e0  Error: ABRT at LBA = 0x00235dc0 = 2317760

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 00 c0 5d 23 20 00      11:39:12.024  READ VERIFY SECTOR(S) EXT
  42 00 00 c0 5c 23 20 00      11:39:12.021  READ VERIFY SECTOR(S) EXT
  42 00 00 c0 5b 23 20 00      11:39:12.019  READ VERIFY SECTOR(S) EXT
  42 00 00 c0 5a 23 20 00      11:39:12.016  READ VERIFY SECTOR(S) EXT
  42 00 00 c0 59 23 20 00      11:39:12.013  READ VERIFY SECTOR(S) EXT

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


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.

Any help would be appreciated! Thank you very much!



BC AdBot (Login to Remove)

 


m

#2 ranchhand_

ranchhand_

  • Members
  • 1,494 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Midwest
  • Local time:12:55 PM

Posted 10 October 2014 - 10:13 PM

Probably not unless it is only the controller circuit board. HDs are so cheap now it's not worth the sweat and time. Just a suggestion, I wouldn't leave that drive installed, I have known failed hard drives to prevent normal booting. Why play with the possibility of a corrupted operating system? If you have data on it, possibly it can be retrieved.


Help Requests: If there is no reply after 3 days I remove the thread from my answer list. For further help PM me.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users