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

WD 'Caviar' External Hard Drive Woes


  • Please log in to reply
5 replies to this topic

#1 TroutBum

TroutBum

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Colorado
  • Local time:02:09 AM

Posted 11 April 2013 - 03:31 PM

Hello,

 

I am new to the forum, but I have been following other posts to try and resolve my problems, but I finally decided to start a post.  

 

I am having some interesting problems with my WD External HDD, its a 500GB drive and its a few years old.  I'm running Vista Ultimate on a Dell Laptop (specs available if you need them).  I would like to attempt to recover the data before I go ahead and wipe the device and start over.

 

A while back I allowed a friend of mine to plugged my drive in to their MacBook and it's been all downhill from there.  Apparently, the drive has been reformatted and it can no longer be read by the Mac or by PCs (I've tried it with XP and Vista).  I wound up finding another friend who has an identical case for the drive, so we took them both apart and used the case that was working, but that didn't help.  I now have a USB to SATA/IDE cable that I've been using to connect the drive and it does function higher than it does in the standard case.

 

From there I've tried running diagnostics and things and an interesting problem has popped up: the drive only shows up as ~24 GB of 'unallocated', blank space (black line) in the Computer Management > Disk Management section of 'computer'.  Interesting as the drive should be somewhere around 500GB.  The same holds when I ran PartedMagic and GSmartControl -it only showed as a 24 GB drive.  I'm assuming that my data (if its still there) somewhere on the portion of the drive that isn't being read.  I don't believe the drive was partitioned when I got it, but it is possible being that I didn't format it when I got it (I'm fairly certain that it was in FAT32 when I got it).  In the future I will certainly wipe all the junk off of a external HDD before I use it out of the box.

 

The drive does not make any grinding or physically unpleasant noises, so I am fairly certain that this is some kind of partition/software/formatting issue.  I would really like to recover the data from the drive if at all possible and I'm just wondering where to go from here.

 

Any and all help is much appreciated!


Thanks!! 

       

            - Buck

 

PS. I've got PartedMagic annd GSmartControl ready to run, I can upload the diagnostics from those areas any time if that helps.  



BC AdBot (Login to Remove)

 


#2 James Litten

James Litten

    Ԁǝǝ˥q


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

Posted 13 April 2013 - 07:03 PM

Hi Buck

 

Post the results of GSmartControl and I'll let you know if I have any suggestions.

 

James



#3 TroutBum

TroutBum
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Colorado
  • Local time:02:09 AM

Posted 14 April 2013 - 03:03 PM

Here are the results from GSmart:

 

 

smartctl 5.43 2012-06-30 r3573 [i686-w64-mingw32-vista-sp2] (sf-5.43-1)
Copyright © 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
 
=== START OF INFORMATION SECTION ===
Device Model:     WDC ROM MODEL-SPIDER--
Serial Number:    WDC-ROM SN# XYZ----
LU WWN Device Id: 5 0014ee 100f9397c
Firmware Version: 01.01B01
User Capacity:    24,079,491,584 bytes [24.0 GB]  ---------> Should be ~500 GB
Sector Size:      512 bytes logical/physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Thu Apr 11 14:11:18 2013 MDT
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:  (0x80) Offline data collection activity
was never started.
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: (12360) 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: ( 145) 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   100   253   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0003   170   163   021    Pre-fail  Always       -       4500
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       42
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000e   100   253   051    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       407
 10 Spin_Retry_Count        0x0012   100   253   051    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0012   100   253   051    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       37
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       29
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       42
194 Temperature_Celsius     0x0022   115   097   000    Old_age   Always       -       32
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0012   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   051    Old_age   Offline      -       0
 
SMART Error Log Version: 1
ATA Error Count: 61882 (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 61882 occurred at disk power-on lifetime: 407 hours (16 days + 23 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 51 01 00 00 00 e0  Error: ABRT 1 sectors at LBA = 0x00000000 = 0
 
  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 01 00 00 00 00 00      00:34:17.668  READ DMA EXT
  ef 03 46 00 00 00 00 00      00:34:16.658  SET FEATURES [Set transfer mode]
  25 00 01 00 00 00 00 00      00:34:16.540  READ DMA EXT
  e5 00 00 00 00 00 00 00      00:34:12.796  CHECK POWER MODE
  e5 00 00 00 00 00 00 00      00:34:04.626  CHECK POWER MODE
 
Error 61881 occurred at disk power-on lifetime: 407 hours (16 days + 23 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 51 01 00 00 00 e0  Error: ABRT 1 sectors at LBA = 0x00000000 = 0
 
  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 01 00 00 00 00 00      00:34:16.540  READ DMA EXT
  e5 00 00 00 00 00 00 00      00:34:12.796  CHECK POWER MODE
  e5 00 00 00 00 00 00 00      00:34:04.626  CHECK POWER MODE
  e5 00 00 00 00 00 00 00      00:33:56.457  CHECK POWER MODE
  e5 00 00 00 00 00 00 00      00:33:48.287  CHECK POWER MODE
 
Error 61880 occurred at disk power-on lifetime: 406 hours (16 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
  -- -- -- -- -- -- --
  04 51 01 00 00 00 e0  Error: ABRT 1 sectors at LBA = 0x00000000 = 0
 
  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 01 00 00 00 00 00      00:13:15.447  READ DMA EXT
  e5 00 00 00 00 00 00 00      00:13:13.607  CHECK POWER MODE
  e5 00 00 00 00 00 00 00      00:13:05.438  CHECK POWER MODE
  e5 00 00 00 00 00 00 00      00:12:57.269  CHECK POWER MODE
  e5 00 00 00 00 00 00 00      00:12:49.099  CHECK POWER MODE
 
Error 61879 occurred at disk power-on lifetime: 406 hours (16 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
  -- -- -- -- -- -- --
  04 51 01 00 00 00 e0  Error: ABRT 1 sectors at LBA = 0x00000000 = 0
 
  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 01 00 00 00 00 00      00:07:06.711  READ DMA EXT
  ef 03 46 00 00 00 00 00      00:07:05.649  SET FEATURES [Set transfer mode]
  25 00 01 00 00 00 00 00      00:07:05.533  READ DMA EXT
  e5 00 00 00 00 00 00 00      00:06:58.683  CHECK POWER MODE
  e5 00 00 00 00 00 00 00      00:06:50.513  CHECK POWER MODE
 
Error 61878 occurred at disk power-on lifetime: 406 hours (16 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
  -- -- -- -- -- -- --
  04 51 01 00 00 00 e0  Error: ABRT 1 sectors at LBA = 0x00000000 = 0
 
  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 01 00 00 00 00 00      00:07:05.533  READ DMA EXT
  e5 00 00 00 00 00 00 00      00:06:58.683  CHECK POWER MODE
  e5 00 00 00 00 00 00 00      00:06:50.513  CHECK POWER MODE
  e5 00 00 00 00 00 00 00      00:06:42.344  CHECK POWER MODE
  e5 00 00 00 00 00 00 00      00:06:34.174  CHECK POWER MODE
 
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.


#4 James Litten

James Litten

    Ԁǝǝ˥q


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

Posted 14 April 2013 - 03:31 PM

Hi

 

Check the IDE cable connection. Those errors are typical of a problem with the cable or connection. Especially make sure that you are using an 80 wire cable and not a 40 wire.

 

Otherwise, the drive looks good. If you are able to fix it by changing the way it is connected, let us know if there are further problems that need to be addressed (like the recovery of data).

 

James



#5 TroutBum

TroutBum
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Colorado
  • Local time:02:09 AM

Posted 14 April 2013 - 04:45 PM

James,


Thanks very much for your reply.  I am connecting the hard drive externally via a USB 2.0 to SATA/IDE connection.  Are you saying that I should connect the drive using a different method?  


Also, I was wondering about the weirdness of the drive only showing up as a 24 GB drive when it should be closer to 500 GB.  Do you using a different connection method would solve this issue?  Or is this perhaps a different problem all together?

 

Thanks again for your help. I really appreciate it.

 

- Buck 

 

On a side note: I mentioned above that I thought that the enclosure that the hard drive was in was the problem.  I tried connecting using an identical enclosure that was functional, but that didn't solve the problem.  So... that's why I went to the USB to SATA/IDE cable.


Edited by TroutBum, 14 April 2013 - 04:48 PM.


#6 James Litten

James Litten

    Ԁǝǝ˥q


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

Posted 14 April 2013 - 05:32 PM

Hi

 

If making sure that it is connected properly does not fix it then it is a problem that you'll need to have a professional recovery service repair/recover.

 

"ATA Error Count: 61882"

with the last 5 errors being all the same and occurring very recently ("Error 61882 occurred at disk power-on lifetime: 407 hours")

and the last 5 errors being the kind of error that you see when there is a physical connection problem.

 

If it is not an issue with the connection then my next guess would be the firmware on the drive has a problem. Of course, I could be wrong :)

 

I read your posts before answering. Some USB to IDE bridges use a cable and some plug in directly but you did not say which you had. It also was not clear if the problem you originally had before removing it from the enclosure was the same as the problem you had afterwards. So I had to make some assumptions.

 

Do you know if that model uses default encryption that employs chips on the original enclosure's circuit board? You may need to use the original enclosure to access the drive.

 

James






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users