Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a seagate 3TB external hard drive with GPT. I accidentally pulled out the power cord and upon reboot was faced with a Raw Partition message in Windows Explorer re: You need to format your drive before you use it.

I didn't do that but instead opened the drive in MiniTool Partition Wizard 7. The following was displayed:

enter image description here

So great news my partition still seems to be there. Not 1337-R-BAK but the other unallocated space. This is the correct size and I can access data on 1337-R-BAK as well.

So I use the partition recovery feature of this application it finds my partition as below.

enter image description here

So great i follow through the wizard and within Partition Magic I get this:

enter image description here

I can use partition explorer within Partition Magic and can see all my files. Whew! But there is no option to open them using this tool. Im pretty sure it's just reading the NTFS file table which hopefully means that the NTFS file table is in tact and my files are not corrupted.

Note tho that these Disk 2 partitions were originally GPT partitions as per Disk 3, but now they are Logical Primary.

Now if I go to Computer Manager the larger than 2GB partition, 1337-F-BAK, is not recognised as a whole partition and instead Windows splits it into a couple of partitions.

enter image description here

So I've got a bit of a chicken and egg problem. I need the disk initialised to GPT before I recover the partition but if I do that I'm pretty sure it will wipe the partition table and then I wont be able to recover the files on the partition. However by not initializing first I can't access the data in windows although at least I can take comfort that my data is still "there".

What is the process I should follow to dig myself out of this one?

share|improve this question
I do not have an answer, but if you can Read_Only recover at any stage, why not? then GPT it and read-only recover again, then fix. – Psycogeek Apr 7 '13 at 7:28
Try installing my [GPT fdisk (gdisk) software.][1] This is a command-line partitioning tool that examines and manipulates the partition table only (that is, it ignores the underlying filesystems). It's got a verification feature (v) that reports disk problems. Post the results of using that feature, as well as of viewing the partition table (p). [1]: – Rod Smith Apr 7 '13 at 18:04
up vote 0 down vote accepted

Ok so in the end I installed WinHex 17.0. This allowed me to go beneath the file system and partition tables to the raw disk and pull file according to file header signatures.

Since this was a newish disk that hadn't been filled this worked really well as the disk had never reached capacity and had never been defragmented therefore the clusters were all nicely sequential.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .