When I go to recover a few videos on my memory stick, the progress bar will open up and it will freeze at 0% and calculating time left. It will stay this way for well over 6 hrs. The weird thing is it will recover other photos off of the memory card but not these videos. If it makes any difference the files are .3GP videos coming off of a MicroSD memory stick.
I have a similar problem. Recuva finds 507 file on the sd card. I have tried many times and many ways to get it to recover, trying one or two files up to the 507. Nothing ever happens, it says restoring and i have let it run all night with the same status the next morning. Nothing
Perhaps you could try running it in debug mode for a while, this might give the devs some info to work on. Just attach the log in a post
http://docs.piriform.com/recuva/troublesho...a-in-debug-mode
I have the EXACT same issue as the OP (freezing on 3gp files off a MicroSD card)
NOTE: Any version before 1.28 CAN recover these files but the names are missing (and some files are corrupt)
All versions after 1.27 can find the exact file / dir names but the recovery freezes at calculating time (with 100% CPU)
Here is the log, please take a look at this when you get a minute,
keep up the good work guys... 8 )
[2010-03-22 15:59:08] [INFO ] Recuva v1.36.479 [2010-03-22 15:59:08] [INFO ] System Info: MS Windows Vista Home Premium SP2, Intel Core2 Duo CPU P8600 @ 2.40GHz, 4.0GB RAM, NVIDIA GeForce 9600M GT [2010-03-22 15:59:10] [INFO ] No update available [2010-03-22 15:59:26] [INFO ] Boot sector: 6/6QZnNpbTUuNjEAAiABAAIAAgAA+OsAIAACAAAAAAAAYB0AAAApU7QAACAgICAgICAgICAgRkFUMTYgICAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAVao=
[2010-03-22 15:59:26] [INFO ] FS type detected by BPB parameters, OEM name fsim5.61 is unknown.
[2010-03-22 15:59:26] [INFO ] Processing folders from 0
[2010-03-22 15:59:27] [INFO ] Analyzing damage
[2010-03-22 15:59:27] [INFO ] 136 deleted files, 961 filesystem objects
[2010-03-22 15:59:27] [INFO ] Processing deleted emails
[2010-03-22 15:59:27] [INFO ] Processing recycle bin
[2010-03-22 15:59:27] [INFO ] Returning list
[2010-03-22 15:59:27] [INFO ] 109 / 31
[2010-03-22 15:59:27] [INFO ] Exiting scan
Hi,
It is important that you send us a .dmp file so we can further analyze this problem.
A .dmp file can be created doing the following:
1 - If you can cancel the recovery while is hanging, then run Recuva once again with /debug command line and cancel recovery while hanging. A .dmp file should be created in the same folder as Recuva executable.
or
2 - If you can not cancel the recovery and if you are running Vista or later, you can create a .dmp file for running process using Task Manager (see attached snapshot for example).
Thanks
Any updates to this current issue? I have an iPod that I would like to recover some MP4s prior to doing s restore. Have not done a thing with the iPod since (1) the videos stopped playing on the iPod, though they appear as IMG_00?? listings, (2) the videos files no longer appear in Windows Explorer.
RV
I keep hanging up around 84-86% and I have to use task to close recuva. Any suggestions?
Craig-
Hi,
It is important that you send us a .dmp file so we can further analyze this problem.
A .dmp file can be created doing the following:
1 - If you can cancel the recovery while is hanging, then run Recuva once again with /debug command line and cancel recovery while hanging. A .dmp file should be created in the same folder as Recuva executable.
or
2 - If you can not cancel the recovery and if you are running Vista or later, you can create a .dmp file for running process using Task Manager (see attached snapshot for example).
Thanks
I ran into the same problem as teh others in this thread. Trying to recover files from an iPod Nano. The files are quickly identified in non-deep mode and have "excellent" recovery prognoses. The "cancel" button in Recuva yielded no response whatsoever; the process continued to tax the system at 50% CPU power (2 cores). Attempting to create a Dump File from TaskMan yields "The operation could not be completed. Access is denied."
Any other options? I would really love to get my files back, but I would also love to be able to use my iPod as a pedometer to track injury rehabilitation work.
Thanks for any tips you may have.
i have a problem where Recuva will reach 43% and then just sit at 43% for hours even at realtime process priority.
this is interesting since I have the same exact problem trying to recover a .3gp file from a micro SD card, I posted the problem in the bug reports section an someone told me it could be a bad card or a bad reader, I removed the reader from the ecuation since i tried in another computer with the same resuts, the card seems to be O.K. since you can read an write to it (tried once only to avoid overwriting)from either cell phone and computer.
MicroSD is a kingston 2GB (SD-C02G) 8DC/2GB
Windows reports filesystem as RAW
Thanks, the logs here are very useful.
So, were the log files interesting enough to warrant fixing the issue? Still seems to happen on Win7 x64 with Recuva 1.40.525, as well as on Windows XP.
Yes, we are hoping to get a fix for this in the next release
Yes, we are hoping to get a fix for this in the next release
On my iPod, it appears to not recognized the OEM correctly. I've done a cursory look at the iPod drive with a hex editor, and it seems like there's an awful lot of zeros in the Partition Tables and FAT. I'm guessing they might not be completely standard FAT32 layouts.
Is there an experimental build anywhere? I'd love to get the files back, but have to sync/modify the iPod in a couple of days.
Here's my log file, in case it helps: