RAW external HDD

Using TestDisk to undelete files
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: 1
Joined: 08 Oct 2013, 03:59

RAW external HDD

#1 Post by ASUDave »

I have a 2TB USB HDD that I suddenly couldn't get access to my files. The drive was labeled as RAW, an issue which I've seen others on this forum have had. I'm running testdisk and it was able to find my files. So, I'm having testdisk copy those files to an internal 2TB HDD. However, the process is literally taking forever. It has been running for almost 10 days non-stop. It appears that it is actually copying my files as testdisk shows "826 ok, 0 failed" and the the destination drive is starting to show some of the files that have been copied. I'm just not sure how much longer this is going to go. I don't know the total number of files on the disk, so I have no idea how much farther it has to go.

My questions are:
1) Is the time it is taking normal?
2) Is there a process I should have done instead?

I'm a bit leery of stopping the current process because I have no desire to start all over. However, if a quicker process is available, I'd consider it.

User avatar
Posts: 2835
Joined: 18 Feb 2012, 17:19
Location: Ludwigsburg/Stuttgart - Germany

Re: RAW external HDD

#2 Post by Fiona »

It's not normal that it takes so long!
There must be a reason for.
Probably some sectors are bad?
Did you get some read errors?
Can you check your disk using CrystalDiskInfo?
http://crystalmark.info/software/Crysta ... dex-e.html
It's pretty fast and should only provide the status of your disk.
Don't change or modify anything to your disk!
Please copy the content of your testdisk.log, from your last diagnose, into your next post!