I wonder if I have done something wrong or is this amount of time the normal period
I am in the reading sector / recovery mode and the estimated time to completion says it will be 64 hours till ended?
Is there any way to speed this up?
Maybe it is not working correctly it has been doing the recovery for 25 minutes and has had an error reading every sector from 0 forward?
3 days to recover
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
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
Re: 3 days to recover
If you achieve any read errors, testdisk and an OS can hang.
That's why it's possible that it takes so long.
You shouldn't stress your disk as much and running a diagnose instead of.
The cause of read errors can be, wrong memory management (LBA-Logical Block Addressing) faulty file system and bad sectors.
It's recommended to run diagnosing tool from your disk manufacturer, smartmontools or crystal disk info first.
If you'd like to run crystal disk info, you should use the portable version, because the windows installer (exe) contains adware open candy.
You can also consider to have a try to clone your disk.
It's worth a try if you don't have too many read errors.
Fiona
That's why it's possible that it takes so long.
You shouldn't stress your disk as much and running a diagnose instead of.
The cause of read errors can be, wrong memory management (LBA-Logical Block Addressing) faulty file system and bad sectors.
It's recommended to run diagnosing tool from your disk manufacturer, smartmontools or crystal disk info first.
If you'd like to run crystal disk info, you should use the portable version, because the windows installer (exe) contains adware open candy.
You can also consider to have a try to clone your disk.
It's worth a try if you don't have too many read errors.
Fiona
Re: 3 days to recover
thanks
I guess I didn't clarify that the file I am trying to recover is on a 64 Gb micro disk SD memory card
Today the terminal window says it is now 322 hours till completion
I must have failed to follow the instructions
I will try a program from a chinese company that does disk / file recovery and offers support to the client
Thanks
I guess I didn't clarify that the file I am trying to recover is on a 64 Gb micro disk SD memory card
Today the terminal window says it is now 322 hours till completion
I must have failed to follow the instructions
I will try a program from a chinese company that does disk / file recovery and offers support to the client
Thanks
Re: 3 days to recover
trying one more time
was using photo rec then tried test disk and now back to photo rec on the images copied to hard drive, seems like a better result this time
keeping my fingers crossed
was using photo rec then tried test disk and now back to photo rec on the images copied to hard drive, seems like a better result this time
keeping my fingers crossed
Re: 3 days to recover
Please let me know, did it work for you?
Are your read errors gone?
Fiona
Are your read errors gone?
Fiona
Re: 3 days to recover
that didn't work
it recovered some files but I can't find where it put them
it recovered some files but I can't find where it put them