I got "partition reading error" and I used TestDisk to do an analyse and it had already took 24 hours and still running. I didn't run TestDisk 6.14 as an administrator. Can you advise the problem as I need to recover my data back?
TestDisk 6.14 takes forever to scan
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
TestDisk 6.14 takes forever to scan
Hi,
I got "partition reading error" and I used TestDisk to do an analyse and it had already took 24 hours and still running. I didn't run TestDisk 6.14 as an administrator. Can you advise the problem as I need to recover my data back?
I got "partition reading error" and I used TestDisk to do an analyse and it had already took 24 hours and still running. I didn't run TestDisk 6.14 as an administrator. Can you advise the problem as I need to recover my data back?
Re: TestDisk 6.14 takes forever to scan
Still running.
- Attachments
-
- testdisk_win.png (37.5 KiB) Viewed 8606 times
-
northlodger
- Posts: 2
- Joined: 27 Nov 2012, 17:59
Re: TestDisk 6.14 takes forever to scan
Same here, each sector takes ~1 second. A complete deep scan on a 2TB HD take 2.81 days. 
Any advice??
Any advice??
Re: TestDisk 6.14 takes forever to scan
How many read errors did you get?
Read errors can cause that datarecovery software hangs during a scan.
Can you test your disk, using crystal disk info?
http://crystalmark.info/software/Crysta ... dex-e.html
Fiona
Read errors can cause that datarecovery software hangs during a scan.
Can you test your disk, using crystal disk info?
http://crystalmark.info/software/Crysta ... dex-e.html
Fiona
Re: TestDisk 6.14 takes forever to scan
I got the similar problem. With 6.13 (not 6.14) under Ubuntu live CD bootup, the system freeze after "Quick Search" was clicked. (Should I post a new thread for my problem? Well, one thing I need to figure out first...)
The Seagate HD is inside the new purchased Asus desktop. I used to "Ghost" the OS partition. Yesterday somehow I restored the partition image through Ghost in DOS. Then everything went wrong and I finally understand the partition table was ruined.
The failed hard drive was put into a usb case and let another desktop check what went wrong. Ubuntu's GParted showed hundreds of partitions existed. (255 might reaches its display limit.) And TestDisk seemed to show dozens of partitions also. I read a forum article about extended logical partition would mistakenly cause a certain daisy chain loop, which probably fits my case. Well, I don't know.
I read the wiki thoroughly. There's one thing I need to know. The main menu Delete erases all partition data. Could TestDrive recover my HD after the "Delete" is performed?? If it can, I won't give "Quick Search" a chance to scan the infinite loop, freezing the system. Any suggestion?
BTW, is it possible to give a more different wording for the menu list items of TestDrive program? "Delete" is quite too common and hard to be a search keyword if a specific digging is needed.
TestDrive is a great program. I like the way it programmed and designed. Thanks.
The Seagate HD is inside the new purchased Asus desktop. I used to "Ghost" the OS partition. Yesterday somehow I restored the partition image through Ghost in DOS. Then everything went wrong and I finally understand the partition table was ruined.
The failed hard drive was put into a usb case and let another desktop check what went wrong. Ubuntu's GParted showed hundreds of partitions existed. (255 might reaches its display limit.) And TestDisk seemed to show dozens of partitions also. I read a forum article about extended logical partition would mistakenly cause a certain daisy chain loop, which probably fits my case. Well, I don't know.
I read the wiki thoroughly. There's one thing I need to know. The main menu Delete erases all partition data. Could TestDrive recover my HD after the "Delete" is performed?? If it can, I won't give "Quick Search" a chance to scan the infinite loop, freezing the system. Any suggestion?
BTW, is it possible to give a more different wording for the menu list items of TestDrive program? "Delete" is quite too common and hard to be a search keyword if a specific digging is needed.
TestDrive is a great program. I like the way it programmed and designed. Thanks.
Re: TestDisk 6.14 takes forever to scan
Hi, my problem now is solved. Under Ubuntu Live CD, scanning freezes but it became to work under root command prompt under Live CD recovery mode.
I posted another thread. Not quite related to "forever scan" but i'll move to there for further sharing. http://forum.cgsecurity.org/phpBB3/two- ... t1648.html
I posted another thread. Not quite related to "forever scan" but i'll move to there for further sharing. http://forum.cgsecurity.org/phpBB3/two- ... t1648.html