And climbing. I've been scanning a drive for about 20 minutes and so far it states 1055% complete. Shouldn't it only be a total of 100%?
And climbing. I've been scanning a drive for about 20 minutes and so far it states 1055% complete. Shouldn't it only be a total of 100%?
I'm having the same problem, except I've been running way longer than 20 minutes... and much much higher than 1055%.
One of the partitions (~800gb) on my external 1TB Buffalo drivestation has a corrupt MFT and I was hoping to use Recuva to recover the files. I did not reformat the drive before attempting recovery, for fear of further contaminating the process. So the volume I'm scanning still has a corrupt MFT.
When I started the recovery, it took about 30 minutes to complete 2% and estimated that it would be done anywhere from 15-19 hours later. So far so good. However, the recovery has now been running for ~19.5 hours. It displays "Current progress: 12520%" and at the moment it's climbing at about 1-2%/second. The "estimated time left" indicator bounces wildly anywhere between 2 hours and 41 days. The green progress bar has filled up, and reset itself, countless times.
Recuva seems to be working because it has found 6725 files (that sounds like it could be right). However it is still running and I'd like to get on with the recovery process! I'm wondering if the lack of an uncorrupt MFT makes Recuva unable to keep track of what parts of the partition it has already scanned? Has it been scanning the same parts of the drive over and over and over again and just didn't know it?
If I cancel the current scan will it still let me attempt to recover the files it has already found? Or will I cancel 19 hours of waiting in the process?
I'm using a deep scan in Windows 7 x64 with Recuva 1.36.479. I can easily provide any other info if it's important.
Thank you very much if you can help
23 hours into the original scan it finally finished. Glad i didn't try cancelling and starting over!
I do, however, think the "xxxxx% complete" and random skipping "estimated time left" indicators probably qualify as bugs. I'm still willing to contribute - if there's any more info i can provide to help squash them!