Jump to content
Piriform Community Forums

Augeas

Moderators
  • Content count

    4,079
  • Joined

  • Last visited

Everything posted by Augeas

  1. Is This Normal for a Deep Scan?

    1) You an recover the files to anywhere you want, except the 'source' drive. Recovered files are copies of what's on the source drive. I'm not sure what you mean by ' is there nothing at all on the drive that I was trying to recover?'. All the found files come from the source drive (the drive you're trying to 'recover'). 2) No. Recover the files and then decide which are to be reinstated on the source drive. Well, that's the correct advice, but as you're recovering a backup drive you could recover all to your recovery drive, recreate the partitions on your backup drive, and then replace your recovered files. The problem with this is that you will be reinstating a lot of junk along with the good stuff. 3) Yes - ish. In Recuva Advanced Mode select Options/Actions/Restore folder structure. However this will not work with files found with a deep scan that have a number instead of a name, as they hold no folder information. If you have a list of file names then these should be in folder order, if that is possible. 4) Perhaps. In Advanced Mode Options/Actions check Scan for Non-Deletred Files. This might, just might, give you better results. Try it without a deep scan as it is vastly faster that way.
  2. I don't think that there's a way to do this. Recuva will just put a (2) suffix on duplicate file names. How did you do the original selection, are you repeating this? You could always dump the first lot of recovered files to DVD and then plough on, depending on how many gb you are recovering. Or buy a big flash drive and dump them there.
  3. First of all the free and the paid versions both have the same recovery capabilities. Secondly those 'empty boxes' aren't going to right themselevs in a Newtonian world. But don't delete what you've recovered. Don't delete anything until the recovery is finished, or abandoned. I asume your drive is NTFS? Did you do a normal or deep scan? How long has it been since the folders were deleted? In Recuva's list of found files, those marked as overwritten or partly overwritten will not be recoverable, or not be completely recoverable. With a deep scan nothing is overwritten, but only the first fragment of a fragmented file can be recovered, so some will be recoverable, some won't. There's no magic in recovery: Stop using the drive for anything except the recovery. Run a normal scan, sort by state, and recover all those marked as Excellent. (You could also recover those marked as poor, some might be usable.) Run a deep scan, select by .jpg, recover all. Many will be unusable, some will be good. When you've done spend £20 on a pack of DVDs and half an hour on accasional backups.
  4. I'm not aware of any such proposal.
  5. Unsure of function

    No, not according to the documentation and my 10+ years experience.
  6. Need help recovering deleted videos

    As you say card I assume the file system is FAT32. If so then (regulars will be getting bored with me repeating this) on file deletion the file system will zero the first two bytes of the file's cluster address, making the file inaccessible. If you look at the info pane on the right for each of the files the cluster address may start at under 65,535. If this is so then this indicates that the cluster address has been zapped. This will explain why four of the files appear to be overwritten by the fifth. their adresses are now pointing to, or near to, the start of the fifth file, which has a valid address. Unfortunately there's no trick to resolve this. The values in the first two bytes are gone forever. The files will still remain on the card in their original position, but are difficult to locate. If you run a deep scan and look for, and recover, any files with a similar size of the four 'lost' files, then you just might, just might, be lucky. Any files that are fragmented will not be able to be recovered in their entirety, as only the first fragment can be identified. It's worth a try.
  7. Wipe free space does not.

    And if you've solved it, please tell us how so we can become just a fraction more knowledgeable.
  8. For what it's worth, I believe that Windows defrag doesn't include large fragments (I think it's 64 mb) in its defrag count. So if a file has fragments larger than 64 mb it isn't classed as fragmented. I've no idea what Defraggler does. Personally I'd forget it. Why chase your tail for something that won't last five minutes and has no noticable benefit at all?
  9. Winapp2.ini additions

    Please do not use insulting language on this forum. Last warning.
  10. Restore a completed folder

    You can sort the Path column by clicking on the column header. You can then find the desired path, highlight or check all you find, and recover to a folder on a different drive. If you have sub-folders then in Advanced Mode/Options/Actions check Restore Folder Structure (ignore the Secure Overwriting box). Alternatively after the scan enter all or part of the path in the Filename or Path box (in Advanced Mode) in the form of users\name\documents for example. Then check all by checking the box next to Fiklename and recover as above. This is the easier way if the folder has very many files.
  11. Defraggle Improper SSD handling

    And what was that, I wonder?
  12. Photos lost

    I don't have any good news. SSD's are a nightmare for recovery, too clever for their (or our) own good. When a file is deleted on an SSD a TRIM command is sent to the SSD which tells the device controller that the pages are no longer needed. The controller then unmaps those pages (and effectively replaces them with a page of zeroes). At that point the previous data is irretrievably lost. I think that this explains the zeroes in the headers. If the device were USB attached then the TRIM command might not be passed to the controller, and there would be a chance of recovery, but the zeroes do not bode well. Files are listed because Recuva reads the MFT and gets the file list and page addresses from there (TRIM does not touch the contents of the MFT). Unfortunately the address of the old data is of no use. Have you put any filter i your scan? If so I would rescan with no filter at all so you retrieve all deleted files. Did you run a deep scan? If not do so (yes, with no filter). You might find some edit copies etc. Do you have any shadow copies listed in Recuva? If so I would scan these. In advanced Mode Options/Actions check scan for non-deleted files, again not putting any filter in the scan. After the scan enter yourname\documents in the filter box to reduce the list. I have tried this and the results were not as good as I expected, with most pics chopped or distorted. As soon as you find anything recover it to a folder on another drive. Good luck.
  13. Have to go out now but it looks as if you're right, can't see my serial no at first glance.
  14. Well, that just goes to show how I can mis-read a post. I'll have another look.
  15. Yes, still there in the same place using Speccy 1.31.372 PS I am using the portable version, although I can't see that making a difference..
  16. Yes, uder Storage/Hard Drives the first disk is specified, and the tenth entry is Serial Number, between ATA Standard and LBA Size. My speccy is 1.25.674, which I downloaded a couple of years ago and tested, and didn't bother with it anymore. I'll download the latest vers and try that.
  17. I have a very old version of Speccy and it shows the serial number in the XML extract, about 10 down in the disk section. Does your version not have this?
  18. WIPE FREE SPACE

    There's no correct or incorrect, it depends on what you want. Normal file deletion has no part in wipe free space. As you are running wfs from Options/Settings it will do one pass of zeroes. Checking Wipe MFT will obviously take more time, depending on the size of the MFT and how many invalid records it holds. The rest is due to the size of the disk and how much free space there is. Possibly the fragmented state might increase the total time as well. Also when you run wfs you are running the other cleaning processes as well (unless you right click wfs in Cleaner and select Wipe Free Space, which runs it alone). As you have selected normal file deletion this shouldn't take too long, but still has to be accounted for. Wipe Free Space, simple overwrite, within Drive Wiper will do a stand-alone wipe so you can see how long it is really taking.
  19. Comment field

    No. If you are in Wizard mode, just click on the Switch to Advanced Mode box in the top right corner.
  20. WIPE FREE SPACE

    Are you using Drive Wiper or options/Settings? I would think that the time for wiping free space depends on the disk size, whether wipe MFT has been checked, and how many passes have been selected. I haven't personally noticed any increase in time with the same disk size and options.
  21. Comment field

    In Advanced Mode the Info pane will show the full comment for each file.
  22. Speccy Help?

    Please do not double post, GMV.
  23. Recuva recovers (copies) whatever is at the clusters at the address held in the file header. Word will attempt to open the file, and if the file isn't in Word format then it will fail. As Mta said, what is the file system, how long has it been since the file was deleted?
  24. How to recover a directory ?

    My tests have been on FAT32 only, and I can recover a deleted directory back to the root (they were simle tests however). I think that success depends on the circumstances of the individual.
  25. I believe the 'problem' here is that when you plug a device into a USB slot it communicates with the system using the USB mass storage protocol. It simply doesn't support SMART (which is an ATA command). A USB attached hard disk is no different from a USB attached flash drive or SD card, or anything that has a USB plug on the end of a cable, they use different protocols. The system doesn't know what sits on the other end, it may not speak ATA at all. Some protocols, like the one used by USB hard disks, allow ATA commands to be passed through different protocol layers, but there is no general protocol to speak to those devices, and it's probably not supported by WMI, because it's a very complex task. Speccy, like the other Piriform applications, I believe only use WMI requests, so SMART data is not available from USB connected devices. As I said I'm no expert (and this was mainly cribbed from an article in StackOverflow) so I'm quite amenable to being corrected, as I'm at the limits of my knowledge on this subject..
×