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

HDD not recognized...


  • Please log in to reply
5 replies to this topic

#1 Blackstar57

Blackstar57

  • Members
  • 269 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Canada
  • Local time:01:06 PM

Posted 12 January 2014 - 09:23 AM

Hello. I have a friend's computer here that was full of adware and spyware with a couple possible viruses thrown in. I have this taken care of but my problem now concerns a second drive he has in his computer.

 

Computer is an Acer Aspire M3410. It has a HDD docking bay in the front panel with a 750G drive in it. He said the drive would sometimes show up and other times not.

I removed the drive an put it in a docking station connected to my own computer and it says "You need to format the disk in drive G: before you can use it. Do you want to format it? "

Now I realize that formatting a disk erases everything on it but is this what this is telling me? Will it erase the disk or just make it available on my computer?

There is a lot of personal things, pics, files etc on this drive that he wants to keep.

 

I tried my own HDD in his computer both in the docking slot and hardwired directly to the mobo and it was recognized easily.

 

Any ideas on how I can open this drive and save everything on it?

 

Glenn



BC AdBot (Login to Remove)

 


#2 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:06 AM

Posted 12 January 2014 - 10:37 AM

Hi Glenn

 

I have a blog post at

http://html5.litten.com/how-to-fix-external-disk-drive-suddenly-became-raw/

that may help.

 

First you need to make sure that the problem is not being caused by physical damage. If it is, then you should send it to a professional data recovery lab since anything you do could make it worse.

 

If you'd like, I can help you determine if there is physical damage.

 

Here's how...

Plug in the drive.

Get a copy of GSmartControl for Windows
http://prdownload.berlios.de/gsmartcontrol/gsmartcontrol-0.8.7-win32.zip?download
Unzip it and run gsmartcontrol.exe

Double-click your bad drive and click the VIEW OUTPUT button and copy and paste the resulting report in your reply so we can look at it.
 

If the drive is not listed then try shutting down the computer and then turn it on with the drive already plugged in and see if that makes it available in GSmartControl.

 

Let us know if you have any difficulty doing this.

 

-=[ James ]=-



#3 Blackstar57

Blackstar57
  • Topic Starter

  • Members
  • 269 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Canada
  • Local time:01:06 PM

Posted 13 January 2014 - 11:30 AM

Hey James...

 

Thank you for the help and my apologies for the delay in answering.

 

I installed gsmart and it did find the drive. Listed it as Unknown Model. This is the report...

 

smartctl 5.43 2012-06-30 r3573 [i686-w64-mingw32-win7(64)-sp1] (sf-5.43-1)

Copyright © 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

 

Smartctl open device: pd3 failed: \\.\PhysicalDrive3: Open failed, Error=2



#4 Blackstar57

Blackstar57
  • Topic Starter

  • Members
  • 269 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Canada
  • Local time:01:06 PM

Posted 13 January 2014 - 11:45 AM

Hello again James. I rebooted my computer with the HDD in question on and plugged in. Ran Gsmart and it did not show up in the scan. Turned power off HDD and back on and rescanned and I got a report...

 

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

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.10
Device Model:     ST3750640AS
Serial Number:    5QD06QD5
Firmware Version: 3.AAE
User Capacity:    750,156,374,016 bytes [750 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Mon Jan 13 12:39:41 2014 AST
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
See vendor-specific Attribute list for marginal Attributes.

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:   (  430) 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:   (   1) minutes.
Extended self-test routine
recommended polling time:   ( 202) minutes.

SMART Attributes Data Structure revision number: 10
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   117   075   006    Pre-fail  Always       -       127120930
  3 Spin_Up_Time            0x0003   094   093   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   097   097   020    Old_age   Always       -       3088
  5 Reallocated_Sector_Ct   0x0033   092   092   036    Pre-fail  Always       -       356
  7 Seek_Error_Rate         0x000f   076   060   030    Pre-fail  Always       -       21691498609
  9 Power_On_Hours          0x0032   087   087   000    Old_age   Always       -       12118
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   097   097   020    Old_age   Always       -       3096
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       37389
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   066   035   045    Old_age   Always   In_the_past 34 (Min/Max 34/34)
194 Temperature_Celsius     0x0022   034   065   000    Old_age   Always       -       34 (0 14 0 0 0)
195 Hardware_ECC_Recovered  0x001a   083   050   000    Old_age   Always       -       230171217
197 Current_Pending_Sector  0x0012   001   001   000    Old_age   Always       -       28583
198 Offline_Uncorrectable   0x0010   001   001   000    Old_age   Offline      -       28583
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       1
200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0
202 Data_Address_Mark_Errs  0x0032   100   253   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 25206 (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 25206 occurred at disk power-on lifetime: 12118 hours (504 days + 22 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 51 00 9e 89 aa e0  Error: UNC at LBA = 0x00aa899e = 11176350

  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 08 97 89 aa e0 00      00:01:19.614  READ DMA EXT
  25 00 08 8f 89 aa e0 00      00:01:19.614  READ DMA EXT
  25 00 08 87 89 aa e0 00      00:01:19.613  READ DMA EXT
  25 00 08 7f 89 aa e0 00      00:01:19.611  READ DMA EXT
  25 00 08 77 89 aa e0 00      00:01:19.610  READ DMA EXT

Error 25205 occurred at disk power-on lifetime: 12118 hours (504 days + 22 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 51 00 27 8a aa e0  Error: UNC at LBA = 0x00aa8a27 = 11176487

  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 27 8a aa e0 00      00:01:14.453  READ DMA EXT
  ef 03 46 00 00 00 a0 00      00:01:11.674  SET FEATURES [Set transfer mode]
  00 00 80 00 00 00 00 04      00:01:11.668  NOP [Abort queued commands]
  25 00 80 a7 89 aa e0 00      00:01:11.666  READ DMA EXT
  25 00 80 27 89 aa e0 00      00:01:11.664  READ DMA EXT

Error 25204 occurred at disk power-on lifetime: 12118 hours (504 days + 22 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 51 00 a8 89 aa e0  Error: UNC at LBA = 0x00aa89a8 = 11176360

  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 a7 89 aa e0 00      00:01:14.453  READ DMA EXT
  25 00 80 27 89 aa e0 00      00:01:11.674  READ DMA EXT
  25 00 80 a7 88 aa e0 00      00:01:11.668  READ DMA EXT
  25 00 80 27 88 aa e0 00      00:01:11.666  READ DMA EXT
  25 00 80 a7 87 aa e0 00      00:01:11.664  READ DMA EXT

Error 25203 occurred at disk power-on lifetime: 12118 hours (504 days + 22 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 51 00 9e 89 aa e0  Error: UNC at LBA = 0x00aa899e = 11176350

  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 27 89 aa e0 00      00:01:11.630  READ DMA EXT
  25 00 80 a7 88 aa e0 00      00:01:11.674  READ DMA EXT
  25 00 80 27 88 aa e0 00      00:01:11.668  READ DMA EXT
  25 00 80 a7 87 aa e0 00      00:01:11.666  READ DMA EXT
  25 00 80 27 87 aa e0 00      00:01:11.664  READ DMA EXT

Error 25202 occurred at disk power-on lifetime: 12118 hours (504 days + 22 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 51 00 9e 89 aa e0  Error: UNC at LBA = 0x00aa899e = 11176350

  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 08 97 89 aa e0 00      00:01:08.020  READ DMA EXT
  25 00 08 8f 89 aa e0 00      00:01:08.396  READ DMA EXT
  25 00 08 87 89 aa e0 00      00:01:08.313  READ DMA EXT
  25 00 08 7f 89 aa e0 00      00:01:08.279  READ DMA EXT
  25 00 08 77 89 aa e0 00      00:01:08.271  READ DMA EXT

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%         0         -

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.



#5 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:06 AM

Posted 13 January 2014 - 05:36 PM

Hi Glenn

 

That drive has a lot of damage. Specifically, thousands of bad sectors and over 300 that have been replaced from the reserve pool (which will run out soon).

 

If you need to recover the data from this drive you should take it to a professional data recovery lab. If that is not an option for you and you want to attempt recovery yourself, then at the least make an image of the bad drive and attempt the recovery from the image while saving the broken drive in case the opportunity to send it to a professional data recovery lab arises in the future.

 

My concern is that the drive is probably continuing to get worse with use and will become completely unresponsive soon. It currently is teetering on the edge of a SMART failure.

 

If you make an image, I recommend GNU ddrescue which is included on the Clonezilla LiveCD.

http://clonezilla.org/clonezilla-live.php

 

I do have a tutorial here but it uses a PartedMagic LiveCD which as of September of 2013 is no longer free.

http://html5.litten.com/windows-file-recovery-series-part-4-recover-files-from-a-bad-hard-drive/

 

After making an image, put the drive away and then run TestDisk on the image and if it is able to repair it then mount it in Linux or in Windows (using something like OSFMount) and copy the data off of it. If that does not work, you can attempt a raw recovery using PhotoRec.

 

I wish I had better news but the drive is in bad shape.

 

-=[ James ]=-



#6 Blackstar57

Blackstar57
  • Topic Starter

  • Members
  • 269 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Canada
  • Local time:01:06 PM

Posted 14 January 2014 - 01:17 PM

Thank you very much James. I spoke with my Buddy already about the possible failure of the hard drive. He was concerned and I told him about the option of having it professionally recovered.

There are a couple local computer shops in my area. I'll recommend one to him.

 

Again, thank you James. This is a great site and have received nothing but excellent advice and help here when needed.

 

Glenn






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users