2 TB sata external HD usb broke off

[Slartybart]

Since your USB connector broke off there might have been some electrical shock to the drive.

Testdisk can identify the drive, but there's a piece on it that cannot be analysed.

You'll need to make sure that the jumpers and BIOS are correct for that drive. You said that the jumper placement was on the drive itself, so double check it and then see what BIOS knows.



You might have to write a new MBR and then analyse afterwards.

• Menu MBRcode
• Menu Analyse

This is going to take some time and there are no guarantees. Take your time and read about Testdisk, it has much better data recovery than photorec (in the same zip file you already downloaded and extracted). But that data recovery doesn't do much good if Testdisk can't see the partition.


even more information on MBR

Bill
.

 

[Slartybart]

I'm out for the night, but will check back tomorrow.

Please keep folks on this side of your monitor up to date with any acitons you take.

Thanks,

Bill
.

 

[injmalk]

Same result as last time

 

[jumanji]

Hi Slartybart, (earlier I was typing startyybart - blame it on my poor eyesight )

I was focussed on another OP's problem which cropped up again and so did not get into this thread. Just now I gave it a look, but I am yet to fully comprehend what has gone on.

Test Disk seems to identify the hard disk.

Reading through I do not understand why one should deviate from Analyse to File Utilities. ( your post no.47.) ( The OP is advised to read Part two of my guide.)

What happens if one hits analyse?

How many partitions did the OP have on that external disk and in what format?

Was it formatted by anything prior to Vista?

Regarding the jumpers, let the OP tell us the exact model of his Hard disk. Then you can look into the manufacturer's website and guide him what it should be. ( I am leaving station tom morning and my return to desk here is open.No internet during this absence because of the festival + 2G not available. So my datacard will be useless in a village.)

The other point I would like to make is that in the case of an external disk, there is no need to write the boot MBR. That is applicable only in case internal boot drives, as I understand. So no write MBR. Only write partiton table if it finds.

Finally, I would say if ANALYSE does not find the partition or gives any error message, we have hit a road block.(I have to admit that apart from conducting the trial wherein I actually deleted the partitions using the same Test Disk making it unallocated and using the Test Disk to successfully find and rewrite it, I haven't had any situation requiring recovery) So we will only be using the learn and guide philosophy to the best extent possible.

That said, I would have personally preferred maintaining near-identical conditions for the hard disk by putting into another external casing. Think, we wouldn't run into jumper jumps. But then it involves cost which may look heavy if the efforts turns futile. We will carry the cross.

 

[Slartybart]

No, something has changed. Let me read over this thread again.

Could you PUBLISH a Speccy report (file menu publish) and post the URL it returns?

Thanks

 

[injmalk]

http://speccy.piriform.com/results/EPEHdQJpNl3VlIroFm58pJ4

only one partition and wasnt formated on anything prior to vista

 

[Slartybart]

Post 22 - 1st attempt, before jumpers

---

​

Post 30: Connected to Sata | Jumpers on 7 & 8 - as stated on sticker.
Note: OP beleives it is slave jumpering. Now that I'm writing the recap
- confirm needed. No such thing as slave Sata???????
- rejumper as master???????​

Post 36: Disk Management​

---

Post 30: Jumpers on 7 & 8 - as stated on sticker.
Post 38: Testdisk 43% - invalid boot sector

---

​

Post 30: Jumpers on 7 & 8 - as stated on sticker.
post 40: We're going to try Recover a FAT32 boot sector​

Based on FAT invalid boot sector

post 43: testdisk - disk selection
(just showing the correct drive is selected for recover fat32 boot attempt)​

---

​

---

 

[Slartybart]

I raised my own question in the recap and jumanji asked "What drive make and model"

injmalk, please look at this page and post a link to the correct model. Since the drive is connected as Sata, the system specs picked up the internal model.
I'll start with that information, but want to be sure.

I found the jumper settings for WD20EAR(S & X jumpers are the same). The drive default jumper is NONE.

---

edit: the drive was not jumpred originally. after i raised the question, injmalk jumpered 7 & 8 per the drive sticker. After verifying WD internal WD20EARS jumpers - the jumper should be removed.

 

[Slartybart]

so let's try this and see what Testdisk tells us.

Remove the jumper from the drive and reconnect
Reboot, check BIOS - what does BIOS think is connected?

Fire up testdisk, post screen two (drive identification/selection)

Then we'll return to jumanji's tutorial and see if results improve after removing the jumper. Or are the results no better?

I'll defer to jumanji's judgement since he is familiar with the tesdisk application. I purchased a commercial application 20 years ago, so the functionality is familair, just the operation is different. Testdisk is a great find - I paid 200 USD.

I'll be out for a while, but will check in for a status update and offer as much guidance as I can based on what you post.

Bill
.

 

[Slartybart]

The drive information in Speccy looks good, only minor retry counts
WDC WD20EARS-00MVWB0
Manufacturer: Western Digital
Heads: 16
Cylinders: 16383
SATA type: SATA-II 3.0Gb/s
Device type: Fixed
ATA Standard: ATA8-ACS
LBA Size: 48-bit LBA
Power On Count: 233 times
Power On Time: 23.9 days
Features: S.M.A.R.T., AAM, NCQ
Transfer Mode: SATA II
Interface: SATA
Capacity: 1863GB
Real size: 2,000,398,934,016 bytes
RAID Type: None

S.M.A.R.T
01 Read Error Rate: 200 (200 worst)
Data 0000000001
03 Spin-Up Time: 207 (189)
Data 0000001208
04 Start/Stop Count: 100 (100)
Data 000000011A
05 Reallocated Sectors Count: 200 (200)
Data 0000000001
07 Seek Error Rate: 200 (188)
Data 0000000000
09 Power-On Hours (POH): 100 (100)
Data 000000023E
0A Spin Retry Count: 100 (100)
Data 0000000000
0B Recalibration Retries: 100 (100)
Data 0000000000
0C Device Power Cycle Count: 100 (100)
Data 00000000E9
C0 Power-off Retract Count: 200 (200)
Data 0000000015
C1 Load/Unload Cycle Count: 200 (200)
Data 00000007CB
C2 Temperature: 127 (085)
Data 0000000017
C4 Reallocation Event Count: 199 (199)
Data 0000000001
C5 Current Pending Sector Count: 200 (200)
Data 0000000005
C6 Uncorrectable Sector Count: 200 (200)
Data 0000000000
C7 UltraDMA CRC Error Count: 200 (200)
Data 0000000000
C8 Write Error Rate / Multi-Zone Error Rate: 200 (200)
Data 0000000000

Temperature: 25 °C
Temperature Range: ok (less than 50 °C)
Status: Good

 

[Slartybart]

jumanji also suggests putting the drive in a replacement enclosure - great idea and not too expensive. As he said, that eliminates the jumper and BIOS questions.

Google shopping results: external drive enclosure

 

[Slartybart]

Don't sweat the name, just call me Bill. Other folks have typo'd Slartybrat which made me laugh.

I appreciate your oversight no matter what you call me.

Hi Slartybart, (earlier I was typing startyybart - blame it on my poor eyesight )

 

[injmalk]

What about a usb dock?

 

[Slartybart]

Pretty much the same thing, but some leave your drive exposed. All are more expensive (higher functionality). Your choice, the point of the exercise would be to "restore" the drive to be a USB connected device. A cable would work too, but exposes the drive even more.

What about a usb dock?

 

[injmalk]

So the drive was not recognized in the dock by the computer or in the disk management or testdisk.

 

[Slartybart]

I have three follow up questions before I "kiss the baby goodnight"

1) Did you remove the jumper?
2) Did you try Testdisk then, still connected to mobo?
3) Do you have a "spare" drive you could put in the dock to make sure it isn't the dock?
Ok I said 3, just thought of two more
3a) What does not recognized mean - Computer, Disk Management?
3b) What does Testdisk show when you get to the select drive step?
3c) Do you want to continue troublehsoting the dock or go back to connecting it to the mobo? (answer to Q2 might answer part of this.

Basically, if Testdisk doesn't see the drive, we're done. It did see the drive when connected internally, so there's a chance.

Bill
.

 

[injmalk]

1) Yes
2)the original troubleshooting was connected to the mobo without the jumper
3) yea it works with other drives
4) yea nothing comes up in disk management
5)teskdisk doesnt give the option for the 2TB drive
6) yea ill connect it to the mobo again and go from there that seemed to give the best options

since programs like recuva need a partitioned drive to search would it accomplish anything if I just formated the drive to try to recover files that way or will this most likely not work and make things worse?

 

[Slartybart]

Sorry-I'm. Having machine trouble again

Fingers too fat----eyes too weak to use a phone for troubleshootig

Formatting might work or it might not

Your drive seems to be in sad shape

Testdisk is probably your best hope

Another member had success when they ran it offline
You could put it on an install usb windows install that is and launch a. Cmd prompt -
Or visit jumanji tutorial----one last note, OP ran 6.14
Jumanji knows testdisk - send him a PM, he is a very nice man

I won't have a machine until

​

next week--IF the repalcment parts solve the problem

 

[ICIT2LOL]

I'm outta here good luck fellas

 

[Slartybart]

@injmalk: I cobbled together a machine, so I can at least read and post stuff.

What's the status of the issue you're trying to resolve?

A few posts that might help:
Kado897 posted this as a possible solution in jumanji's guide

jumanji referenced a link:
How To Fix: External Disk Drive Suddenly Became RAW

There is certainly a lot to learn about disk recovery and every situation is just a litttttle bit different.There are some set steps for common recovery, the easiest is to physically be at the PC. I used to know this stuff inside out.

Read up - follow some of the examples on the Testdisk site. I don't know if Kado's solution saves the data - it might only make the drive usable again. It's a crap shoot - the one piece of data that is mission critical might get overwritten.... but you might be able to recover other data using Recuva or other software.

• TestDisk Step By Step
  
• Running the TestDisk Program
  
• Undelete files from NTFS
  
• Data Recovery Examples
  
• TestDisk Livecd

The "solution" for the OP was to run Testdisk offiline - the OP never qualified what boot was used, but any bootable USB with Testdisk on it should do the same thing. Note that the LiveCD references on the Testdisk site point to utility disks with older versions - also note that OP used the beta 6.14 version of Testdisk (meaning you might have to roll your own bootable with the beat Testdisk on it.)

There's a bootable USB tutorial in the SF tutorial section that might work.... you would have to add Testdisk to the USB, boot from it and run Testdisk.

Bill