File Shredder does not work on all files

Discussion in 'Acronis True Image Product Line' started by John Farrar, Dec 1, 2007.

Thread Status:
Not open for further replies.
  1. John Farrar

    John Farrar Registered Member

    Joined:
    Nov 9, 2004
    Posts:
    194
    I have a few corrupt files on my PC which I cannot delete or get fixed with CHKDSK. I ran the File Shredder, using various algorithms, but the file remains despite a message saying the file had been deleted.o_O
    Any comments please Acronis?
    John
     
  2. bodgy

    bodgy Registered Member

    Joined:
    Sep 22, 2005
    Posts:
    2,387
    Location:
    Qld.
    When you ran ckdsk did you include the /r switch?

    Is this the file shredder included with TI 11 and which build?

    What file system are you using - FAT32 or NTFS?

    When you say the file still exists, is this from Windows Explorer or the check box in File Shredder?

    If you know how to do i, have you checked from a CMD box to see if the file is listed when a DIR /w is issued?

    It might be that the Shredder has problems with a corrupted file, especially if the corruption is caused by incorrect cluster linking in the FAT or MFT, in which case only something like chkdsk or a disk editor of some kind will fix the problem.

    I can confirm that it does work, as I've just tried it with TI11:8053.

    Just to test if it is TI with the problem - make a file and empty tib file or a notepad file, and then use Shredder to delete it. If Shredder deletes that file satisfactorily, then we can assume that the corrupted file is the problem - if it doesn't then we can then go down the TI is having a spasm attack.

    Colin
     
  3. John Farrar

    John Farrar Registered Member

    Joined:
    Nov 9, 2004
    Posts:
    194
    Hi Colin and thanks for your reply.
    I ran chkdsk from Windows and on the reboot chkdsk went through 5 sets of checks and concluded the drive was 'clean'.
    I'm using TI11 build 8053 and the file shredder is included under Disk Utilities.
    The drive is NTFS format. The file exists in Windows Explorer and in File Shredder if I run it again.
    I've checked the File Shredder with a blank file and the delete was successful so the problem is with a corrupted file. Therefore, if File Shredder cannot delete the file then it should say so not 'delete successful'.
    The boot CD does not include the Disk Utilities so I could not use File Shredder from DOS.
    Thanks for your input.
    John
    PS Any comments Acronis please?
     
  4. bodgy

    bodgy Registered Member

    Joined:
    Sep 22, 2005
    Posts:
    2,387
    Location:
    Qld.
    I've just had another thought. Where in the file tree is this corrupted file?

    In other words, is in the root directory or in the desktop folder etc, and is it using a short file name (8.3) or a long text one? If a long text one, how many characters.


    I have come across some software that doesn't operate properly if it is either installe don the desktop or is asked to perform functions on a desktop, though I doubt that is the problem here.

    However, if you are using a very long file name or the file is way down a list of sub folders, then this could cause problems with programs.

    Are you able to rename this faulty file to an 8.3 type?

    Colin
     
  5. John Farrar

    John Farrar Registered Member

    Joined:
    Nov 9, 2004
    Posts:
    194
    Hi Colin
    Thanks for the quick reply. The file is not in the root directory but in a folder within a folder and is only a few characters long. (It's a .doc file)
    I try to rename it but on the save I get a message saying the file is corrupted so cannot do that.
    Actually, I have found a way to delete the file but it is longwinded but does work.
    Create a file with the same name and extension as the corrupted file.
    Use TI to create a file backup of it. Use Restore from the backup and choose to overwrite the file. A reboot is necessary so the Restore is done in DOS. The corrupted file is replaced with the dummy file and it can then be deleted after a reboot. It's a long winded way though and it would help if the File Shredder could handle it.
    Thanks again.
    John
     
  6. John Farrar

    John Farrar Registered Member

    Joined:
    Nov 9, 2004
    Posts:
    194
    I should have named this thread "File Shredder does not work on corrupt files":( :(
     
  7. Acronis Support

    Acronis Support Acronis Support Staff

    Joined:
    Apr 28, 2004
    Posts:
    25,885
    Hello all,

    Thank you for choosing Acronis Disk Backup software

    The most probable reason is that this file was not accessible by file system. In simple words - the file system was aware that this file exist (and there was a link to this file in MFT) but was not able to access it, so File Shredder was not able to delete it too. It's also possible that the file was deleted, but the link to the file in MFT was not affected and it was still displayed as existing one. It's hard to investigate the issue if you've managed to erase the file, but if you will encounter this issue again you can submit a request for technical support, attach all the information to your request along with the link to this thread. We will investigate the problem and try to provide you with a solution.

    Thank you.

    --
    Michael Levchenko
     
  8. John Farrar

    John Farrar Registered Member

    Joined:
    Nov 9, 2004
    Posts:
    194
    Hello Michael
    Thank you for your reply. The file is still listed with the same file size etc. as if nothing has happened. I have posted a message to technical support.

    There is only one way I can delete the file and that is by creating a blank file with the same name and file extension in a different location to the corrupt one of course. I then make a file backup with TI11 and then Restore that backup to overwrite the corrupt file. I have to reboot to do that as the restore is done in DOS. When that is complete, I reboot and the file has been overwritten with the dummy file which I can then delete. So it is possible so perhaps that process may provide the answer to the problem.
    Regards
    John
     
  9. Bruce Mahnke

    Bruce Mahnke Registered Member

    Joined:
    May 21, 2005
    Posts:
    629
    Location:
    Woodbury, MN USA
    Have you tried booting in to Safe Mode [F8] to see if you can delete the file from there?
     
  10. Acronis Support

    Acronis Support Acronis Support Staff

    Joined:
    Apr 28, 2004
    Posts:
    25,885
    Hello all,

    John Farrar - could you please let me know your Acronis request # which was sent to you in autoreply to your letter? I will find out how the investigation of your issue is going.

    Thank you.

    --
    Michael Levchenko
     
  11. John Farrar

    John Farrar Registered Member

    Joined:
    Nov 9, 2004
    Posts:
    194
    Hello Michael and thanks
    The ticket number is 1249311.
    I have tried deleting in Safe Mode but that did not work. I also booted from a BartPE disk but no joy there either.

    The point is that restoring a file by overwriting it with a 'dummy' file and deleting that file does work. The overwrite is done during a reboot so it is possible. Michael. If the File Shredder was included on the boot CD would it work from there?

    John
     
  12. shieber

    shieber Registered Member

    Joined:
    Oct 27, 2004
    Posts:
    3,710
    I'd still try "chkdsk /f /r" the "/f" being the most important switch, it tells chkdskto fix erros. the "/r" on tells it to relocate bad sectors.
     
  13. MudCrab

    MudCrab Imaging Specialist

    Joined:
    Nov 3, 2006
    Posts:
    6,483
    Location:
    California
    The /f switch is implied when you use the /r switch with chkdsk.

    Code:
    Checks a disk and displays a status report.
    
    
    CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C] [/L[:size]]
    
    
      volume          Specifies the drive letter (followed by a colon),
                      mount point, or volume name.
      filename        FAT/FAT32 only: Specifies the files to check for fragmentation
    .
      /F              Fixes errors on the disk.
      /V              On FAT/FAT32: Displays the full path and name of every file
                      on the disk.
                      On NTFS: Displays cleanup messages if any.
    [COLOR="Blue"]  /R              Locates bad sectors and recovers readable information
                      (implies /F).[/COLOR]
      /L:size         NTFS only:  Changes the log file size to the specified number
                      of kilobytes.  If size is not specified, displays current
                      size.
      /X              Forces the volume to dismount first if necessary.
                      All opened handles to the volume would then be invalid
                      (implies /F).
      /I              NTFS only: Performs a less vigorous check of index entries.
      /C              NTFS only: Skips checking of cycles within the folder
                      structure.
    
    The /I or /C switch reduces the amount of time required to run Chkdsk by
    skipping certain checks of the volume.
     
  14. shieber

    shieber Registered Member

    Joined:
    Oct 27, 2004
    Posts:
    3,710
    I've been "slash-r"ed. I stand corrected.
     
  15. John Farrar

    John Farrar Registered Member

    Joined:
    Nov 9, 2004
    Posts:
    194
    Thanks guys.
    I've used CHKDSK with all switches with no success.
    John
     
  16. John Farrar

    John Farrar Registered Member

    Joined:
    Nov 9, 2004
    Posts:
    194
    After a lengthy communication with Acronis, sending them reports on the state of my system and hard drives etc., I have been told that it is not an Acronis problem.o_O o_O
    All I know is that an uncorrupted file restore will overwrite the corrupt file so why doesn't the File Shredder work?
    John
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.