Jump to content
Piriform Community Forums

Augeas

Moderators
  • Content count

    4,082
  • Joined

  • Last visited

Posts posted by Augeas


  1. 12tb? Are you a commercial enterprise?

    A normal scan should not take too long to analyse, as it is reading the MFT only. I don't know how many files there are on 12tb but even if there are a few million the scan should only take a few minutes (if it gets to stage 2 or 3 you can cancel the scan and still see the results without any apparent deleterious effect).

    If it's a deep scan then I guess it will take forever. Users with 2 or 2 tb disks complain that a deep scan takes days, so 12tb?

    If Recuva did finish, and found multiple millions of files, what human brain could sort that out? I doubt if I could.


  2. OK, let's step back a little and wrap this up. Yeah3346, you can post anything relevant to this forum as you wish, subject to the same rules as everyone, which I try to interpret (and don't always succeed) as don't post anything you wouldn't say face to face. Nobody holds any grudges and in a few days I for one will have forgotten your username or what you posted.

    I think that we all appreciate that the original banning for bumping was harsh, so in future the quite rare bumps will just be deleted.

    I'll close this thread now, enough has been said.


  3. Probably not a lot, but your conception of data recovery might be rather hazy. After all, 'Recovering permanently deleted files' is a little contradictory.  No deleted file can be guaranteed to be recovered, and no operating system cares about, or helps in, recovering deleted files.

    A deep scan runs a normal scan first, and those with a file name will be from the normal scan, and  those with a numerical name in square brackets will be from the deep scan. The deep scan looks for a particular set of file signatures in every non-allocated cluster. Those clusters with a match are listed, along with the following clusters, until another cluster with a file header, or a live file, is found. Only the first extent of a file is found, as there is no way of linking extents, so video or audio files - which are usually large and more likely to be in multiple extents - are quite often unplayable.

    The normal scan files are found by following the cluster addresses in the MFT. Recuva will recover whatever is in these clusters, whether they have all or partly been reused since file deletion. Any corrupt clusters are unlikely to display or play correctly. Very large files, over 4gb, will have the cluster addresses zeroed by NTFS so recovery is impossible. If the file system is FAT32 then the cluster addresses are half-zeroed by the O/S.

    Zero byte files are only found with a normal scan. Naturally they can't be recovered.

     


  4. These a/v's are getting too big for their boots.

    You could run a hex editor such as HxDen and using Recuva's cluster number work out the start sector, go there and have a look at the following sectors to see if there's anything actually there apart from zeroes. You could use the start and end sectors and copy all 80 gb elsewhere but there will be some head-scratching maths involved.

    If the header is zeroed then the chances of any application apart from wordpad opening what you've recovered is very slight. You could also try a data recovery specialist.


  5. I'm a little confused about what you are suggesting. Do you want a Check All for Windows (and ditto fpr Applications) that would check/uncheck everything under that, or for the individual sections under Windows?  Your first paragraph seems to imply the former, and the second paragraph the latter. The last paragraph sort of shoots the whole idea in the foot.

    If you want to check all within in subsection just right click on the heading and select check/uncheck all.

    I think that the current install setup, where a default selection is checked, is better, and safer, than checking everything.

     


  6. I've never seen a file found with any scan not have a name, so I din't know what's happening there. There's no way to rename a file during recovery. What's the message when you try to recover it?

    Is it a file that you just 'found', or is it a file you know about? After all you would probably know if you had lost an 80gb file, but if you didn't know you had one then it probably isn't worth worrying about.

    PS I think I might have had some no-name files right at the end of a deep scan, but they were of no significance so I ignored them.


  7. Recuva will copy whatever is in the clusters whose addresses are in the file's MFT record. So if the deleted file previously occupied say 50 clusters, and 5 clusters in the middle have been overwritten, Recuva will copy all 50 clusters, including the overwritten data, whatever that is. It's not really insecure as the user is already on the machine so he or she just has to look at the live files.

    A deep scan doesn't have overwritten clusters, as there's no way of knowing what was in a 'free' cluster previously.


  8. Just scroll to the right of that box to see the error messages.

    You're trying to recover files found with a normal scan, those found with a deep scan have no file names. The error message might say that 'This file is overwritten by xxxx' which can occur on flash drives.

    Next time make sure the files being recovered are the same as we can see in the underlying pane (which isn't the case here) and don't hide the info with the error box.

×