I am trying to recover some JPEG files which are from a hdd which was accidentally formatted. No further data has been written to the drive.

I am able to recover with GetDataBack and R-Studio and the directory structure and filenames are perfect but I'm unable to open any of the files. In R-Studio I get a lot of errors such as:

'[FileID: 29437] MFT record child's claimed parent mismatch, aborting.'

Do I have chance of recovering the files?

1. Are you working from a clone of the drive?
2. Are you scanning the clone with data recovery tools while it is connected as a slave or via USB to another system with the programs installed?
3. When you recover the files out, are you copying them to a drive other than the clone or original drive from which you are trying to recover?
4. How full was the drive prior to the format?
5. How full is the drive now?
6. Are you sure you are getting the full story?

_________________
Luke
Recovery Force Data Recovery

Is very strange that you get this msg, if you only format the drive, and no data added to the drive.

are you sure that you only fomat drive, without data write?

In case of yes, this may want to say that you have a serious damage on your HDD.
maybe bad heads, media problems.

Please report us about HDD identification data?
and what tool do you have for test it?

Hello DistortedVision,

try http://www.powerdatarecovery.com/
Rstudio is good tool.
Do you have drive connected directly to PC or mounted via some HW tool?

To answer the questions below:

1. No
2. Its connected to another Windows 2008 Server R2 machine
3. Yes
4. About 70% full
5. No data has been written to the drive at all since formatting

I should point out I've recovered data from 3 other drives which were accidentally formatted at the same time using GetDataBack without any loss of data or any issues.

I will test using Seagate SeaTools unless you have any other suggestions and I'll report back.

Drive is connected directly to motherboard.

If you know, which file system was prior format on the drive in R-Studio select only that file system(default are selected all FS)
Try also MiniTool Power Data Recovery 6.8
Otherwise something is missing in this story.
Check terminal

MiniTool Power Data Recovery gave the same results - recovered the files with filenames and directory structure but with corrupt files.

Not sure what you meant by 'Check terminal'?

I'm going to try and recover using PhotoRec. Anyone got any other suggestions. I'm not really sure what has happened here.

What condition are the files in if you recover them in raw format?

You could try using Dmde. Make an image of the whole drive then mount the image and try to recover a few selected files.

Sorry, how do I recover them in raw format?

That would be in the manual.
In R-studio it would be in 'extra found files'

Also you mention 'server' so is there are chance you have a raid configured drive?
Try recovering some small files. Maybe less than 256K then less than 128k and lastly 64K. Are any of them ok?

I think 'server' in inverted commas is appropriate. It wasn't running any server roles it was just convenience for using terminal services etc. The partition wasn't RAID just standard NTFS.

could you try to connect drive to some winxp or win7 PC and try to recover.
If you try MiniTool Power Data Recovery there was options:
undelete recovery
damaged partition recovery
lost partition recovery
...

play with each of it

r-studio show you more alo extra files found. Check also this.

Try to image drive to another drive and play with it.

@DistortedVision, are we to understand that the patient drive is your own, and that it was formatted in the same machine and under the same OS that you are using for the recovery? Does the drive's capacity exceed 2TB?

_________________
A backup a day keeps DR away.

does that drive have some kind of file level encryption "Bitlock"?

I'm trying to recover in another HP ProLiant N54L which is also running Windows 2008 R2 but I can recover in the original machine.

Yes the HDD is 3Tb. Will try all the suggestions above and report back. May take me a while.

Thanks for everyone's help so far!

The reason I asked my questions was that people sometimes encounter file system corruption when they move a drive from a 48-bit LBA environment to one that has a 32-bit LBA limitation. You must ensure that the current SATA driver is not affected by such a limit.

Typically, the user will write data without issue until they attempt to exceed the 2TiB capacity point, at which time the data will wrap around to sector 0 and trash the file system.

_________________
A backup a day keeps DR away.