Jump to content

Recuva only gets to step 1


Brabazon

Recommended Posts

HI. Just wondering if Im doing something wrong here. I can run Recuva and it lists files on a corrupt HDD OK but it doesn't stop there. The percentage has gone up as far as 304500% and down to 500% at random intervals and over a million files found, the only way to stop it is by cancelling. Is this a problem and is it then supposed to go to step 2?

 

Thanks all

Link to comment
Share on other sites

  • Moderators

Sounds like you are doing deep scan and/or include non-deleted files, this seems to be occuring with this mode. ignore the percentage and wait for a while (like multiple hours in the tens-of range) and it will finish

 

ADVICE FOR USING CCleaner'S REGISTRY INTEGRITY SECTION

DON'T JUST CLEAN EVERYTHING THAT'S CHECKED OFF.

Do your Registry Cleaning in small bits (at the very least Check-mark by Check-mark)

ALWAYS BACKUP THE ENTRY, YOU NEVER KNOW WHAT YOU'LL BREAK IF YOU DON'T.

Support at https://support.ccleaner.com/s/?language=en_US

Pro users file a PRIORITY SUPPORT via email support@ccleaner.com

Link to comment
Share on other sites

Hello guys.

 

As I'm typing this reply, Recuva is scanning a 320GB SATA hard drive (damaged NTFS that became RAW), connected externally with USB adapter.

I'm experiencing same problem as Brabazon did, with few differences.

* I did choose deep scan and include non-deleted files, as Nergal assumed.

* After about 3 hours, the scan is on step 1, found 13470 files.

* In my case, the percentage is not random, just goes up and up (currently above 25,000,000% !!!).

* The progress bar switches sometime from completely full to completely empty.

* The estimated time left jumps randomly from 5 days to 24 to 17 to 34 etc.

 

Brabazon, I want to know please what has happened finaly with your scan, and if I should wait.

 

Some fact to mention:

Before Recuva, I tried to scan the hdd several times with GetDataBack. It found lots of files, but every time stopped at some bad sector, which caused to the media to disconnect, and screwed the scan.

Perhaps Recuva also behaves this way when it gets to this bad sector? The good thing is that the hdd stays connected and responding.

 

 

 

Thanks in advance for your cooperation :)

Meir.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.