The ntfs partition on my USB disk is a bit corrupted. A huge backup tar file is still on the disk, but is somehow split into two parts. Recuva lists one of them with the correct name "usr.tar" and a correct size of 21GB, but only recovers half of that. The other file is listed without a filename and with the remaining size that was not recovered. So when I tried to restore the second file, Recuva failed with the error "Invalid access". It worked with the first part and there's still plenty of space left on that other drive. So I assume this is probably related to the empty filename, but I'm not sure of course
Anyway, it would be nice to have some option "Recover as ... " or something, so I can rename it at least. I don't really expect Recuva to recover the full file at once because the ntfs-undelete tool on Linux lists two files as well (both without name) and refuses to recover them as well saying it is in use by the MFT.
But whatever happens, Recuva recovered half the tar file already, that's 10GB of files saved, thanks for that!
Of course, it would be really great if I could restore the other part too
After nearly 6 years still not fixed?... Got the same problem with a Truecrypt container. 10Gb splitted in 2 files, both have an empty name and cant be restored... Please fix this bug. (Its giving me a different error message, Recuva is saying it couldnt find the path)
If it gives a different error it's a different "bug". However the OP isn't really a bug unrecoverable happens, recover is a crapshoot based, at least in part, on however much use the drive gets after a deletion.
As far as your "bug", I don't really see how this even possibly comes within what someone would think a free recovery software could or should do.
A truecrypt file by definition is made to NOT be recoverable after removal.
It's not 'fixed' after six years because it can't be. NTFS overwrites the cluster addresses on deleted files greater than 4gb in size. No software can magic these cluster addresses back again. Recuva shows an error message something like 'Data not found on Disk' on these files, a different error message from that six years ago.
A deep scan might find the start cluster of the file, but if it is in more than one fragment, as it quite likely, it will not find the subsequent fragments so recovery will be incomplete.
It's pointless responding to threads as old as this. PC's and software have moved on, even if we haven't.