I've had a unfortunate situation where a child (somehow managed to) delete a folder containing 7.62TB of data files... In fact over 94k+ files in all. Now this drive is an iSCSI mount on a NAS, so it's not a OS drive that's going to get damaged by temporary files etc, so it should be a simple undelete job; or so I thought...
So, I used Recuva and it managed to find, probably all of the files, however there are quite a few with state that's either unrecoverable or poor etc. and that's what I expected. Recuva is bound to find files that I'd long since meant to delete etc. What I find hard to believe is that this program produces NO LOG; I mean literally nothing! I've got thousands of files to check and go through to make sure they're not corrupt and can be recovered and no way to do this in a orderly fashion without a log file. I mean, what am I supposed to do? Keep Recuva open indefinitely whist I verify the recovered files?
Okay, so I found there's a /debug switch you can add to the end of the command line, but this only dumps a log of what the program is doing etc and doesn't produce anything meaningful in terms of a recovery operation.
Honestly, this literally has to be the stupidest thing I've ever encountered. How can someone say, do a scan and then properly analyse all the files that can/cannot be recovered in cases where you're dealing with tens of thousands of files? In fact this insanity is going to force me to use some other undelete software to recover my files just so that I have some like of log I can browse an analyse and see what I have recovered. Even at the end of a recovery process you get a pointless dialog that says, xxxx files recovered, xxx possibly damaged files and xxx files that cannot be recovered - Okay, it gives you a dialog saying "Cannot recover these files" and gives you a list, but your possibly damaged files, well you just have to trust to luck! (Recuva just said, you have 2,357 possibly damaged files, okay, so which files are those then???!?!??) Have I got to scroll through the 94k+ files in the Recuva window looking for the damaged files?
Come on Piriform, this isn't rocket science. Every program should have a log, especially an application like this.