TestDisk file recovery loop

Using PhotoRec to recover lost data
Forum rules
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
Posts: 2
Joined: 03 Aug 2016, 20:30

TestDisk file recovery loop

#1 Post by asta324 »

Hello, I would like to ask for an advice what to do with TestDisk that got into a loop (at least I think it is such case).
My Win7 computer HDD with one NTFS partition somehow got messed up, TestDisk output said that disk contains multiple overlaping FAT12, FAT16, HFS, HFS+, JFS, CramFS and NTFS partitions. After deeper scan I found original C: partition and begun to copy it to external HDD.
While copying one .iso file (linux distro) the copying got stuck, it always copies whole 3GB file and suddenly starts again with 0MB (it is stuch this way for more than 6 hours).
I'd like to thank you in advace for any recomendations what to do.

Sponsored links

User avatar
Site Admin
Posts: 5307
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France

Re: TestDisk file recovery loop

#2 Post by cgrenier »

Which version of TestDisk are you using ? (Please try to reproduce the problem with the latest 7.1-WIP version)
The source filesystem is NTFS. What is the destination filesystem ? NTFS too ?
As a workaround in the mean time, skip this file... (Do not select the folder where this file is)

Posts: 2
Joined: 03 Aug 2016, 20:30

Re: TestDisk file recovery loop

#3 Post by asta324 »

Thanks for the reply.
To answer your question, yes, the I'm copying from NTFS to NTFS. Before you have replied I found that promblem could be in mount.ntfs (I'm running TestDisk 6.14 from Parted Magicon the sick computer) it takes 35% of CPU resources.
Is there any other workaround (copying already took 2 days and the problematic file is deep in user's folder) ? Thank you very much.