Jump to content
CCleaner Community Forums

Augeas

Moderators
  • Content Count

    4,363
  • Joined

Posts posted by Augeas

  1. The only thing you can do explicitly to any non-system disk is wipe free space with Drive Wiper. You can include folders and files on non-system disks by adding them to the Include list, have a look at the documentation to see how it's done.

  2. I don't think that your problem is similar to the O/P's. He or she has obviously done something at the global level, perhaps formatting the drive. I doubt very much whather all 798gb of files were shift/del'd individually.

    Do you mean on a scan with no filters applied no files were returned? I have never known this in over ten years of using Recuva on internal and occasional external drives. Or do you mean that your video wasn't found? That's quite possible. It's difficult to advise without more info.

    This should be continued on your other thread.

  3. Do you have a Windows.old? M/S says it is auto-deleted 10 days after the upgrade, but there are plenty of how to delete articles so perhaps it's more persistent than that. Anyway, do you? If not then the chances of recovery are very slim, in my opinion.

  4. I guess that this is NTFS, the drive is visible to Windows with a drive letter, and you ran a Recuva deep scan.

    A deep scan runs a normal scan first, so usually you will get a list of file names and associated folders before all those [001234].ext files. These file and folder names all come from a scan of the Master File Table, they are not held within the files. If youi are getting zero file names, then either the disk has been formatted or perhaps the MFT is corrupted. NTFS needs an MFT to do anything at all, so if the MFT is corrupt then the MFT mirror can be used, This only holds about 16 records so it will only identify system files, but it enables access by Windows.

    A deep scan will scan all unallocated clusters for a file header, which identifies the start of a file and the file type. Only a subset of all possible file types are scanned. No file or folder names can be deduced from a deep scan. As the clusers are unallocated they will all have a state of excellent, but don't let that fool you. Only the first extent of a file will be found and be a candidate for recovery. Subsequent extents cannot be identified and will be ignored, so a recovered file may not open anyway.

    I should rerun Recuva with deep scan unchecked, and (in Advanced mode, Options, Actions) check Search for Non-Deleted Files, and check Restore folder streucture. It should be fairly fast and is worth a try.

  5. I think I'm getting there. You ran a backup tio an already existing folder on the G drive (Y-Folder), and purge, which:

    'Deletes destination files and directories that no longer exist in the source',

    wiped out everything already in that folder. You then ran a recover of the contents of Y-Folder back to the D drive, but none of the files recovered open.

    But that doesn't get provide a solution. The headers aren't Recuva's, but the files', and no file with zeroes in the header will open (except text files) as the file structure is unidentifiable. It's highly likley that the rest of the file is zeroes also.

    I wouldn't have thought that Robocopy would overwrite deleted destination files with zeroes, but something has.

  6. Btw what does "zeros" in Header mean? = BUT Header: all "00"

    File names, directory names, cluster addresses etc are all held in the MFT. What's actually on the disk could be anything. I'm still not sure what you did or were trying to do. Perhaps someone with experience with Robocopy can chime in.

     

  7. You copied from your D drive to your G drive, yet you appear to be trying to recover from the D drive, which presumably is your internael drive?

    Whatever is happening, files with zeroes in the header are never going to open, or be fixed.

  8. Yes, NTFS clears up after deleting files greater than 4gb, presumably to release records in the MFT if the file is fragmented (as it most likely is). The fragments may still exist on the disk but retrieving them and piecing them together would be a nightmare.

  9. With TRIM enabled on the O/S and SSD the chance of recovering any deleted file from an SSD is just about zero. Recuva will scan the MFT to reetrieve the file names and cluster addresses, which still exist. The clusters will however be filled with zeroes. In Advanced Mode if you look at the file headers this should confirm the zeroes. Recuva will recover these zero clusters quite happily, but they are of no use. A professional data recovery service might be able to recover some of the files, at a cost, by reading the nand chips natively.

  10. I think that SSD rationale has changed over the past few years. We've seen that Win 8/10 runs what Microsoft describes as a 'Traditional' defrag on SSDs under certain conditions, and we also know that excessive fragmentation causes excessive I/Os as NTFS ploughs through the MFT. So an occasional defrag won't hurt. Does any manufacturer forbid defrags?

    As for longevity, TLC SSD has an erase/write limit of a little over 300. Before anyone panics if I write 1 gb a day on my minute 120 gb device (and that is far more than I do) then the SSD should start slowing down in 110 years.

  11. Or to try to answer Don's original post, dump Defraggler. If you're on Win 8 or 10 (and have sys restore enabled, and have more than 10% fragmentation) then you'll get the Windows defrag described above. Mercifully Win 10 has sys restore off by default so those defaulters (me included) won't get the defrag.

    Why were you running a defrag against your SSD in the first place? What was the fragmented percentage?

     

  12. As TRIM came out with Win 7 in 2009, and SSDs before that, your audience might be limited. Zero filling a non-TRIM SSD might improve write performance but not for the reasons above (and also falsely claimed in the OCZ forums some years ago).

    An empty SSD block contains ones not zeroes, and no software on earth can erase NAND flash blocks. What zero filling does is to allocate a dummy page of zeroes to the LBAs instead of a physical page. The freed pages are subject to garbage collection, which erases them. Thus a pool of erased blocks is available for wrtes, and performance increases.

    Zero filling a TRIM SSD is a waste of time, effort and the life of the SSD.

×
×
  • Create New...