Corrupted files problem

Discussion in 'Acronis True Image Product Line' started by ErnestTwo, Jan 24, 2006.

Thread Status:
Not open for further replies.
  1. ErnestTwo

    ErnestTwo Registered Member

    Joined:
    Jan 12, 2006
    Posts:
    12
    I have been trying since Jan 13/06 to get a straight forward answere to this problem of corrupted files. How can any respectful softwarevendor continue to sell this stuff whith verfication problems that go back through 3 to 4 versions. ~Snipped~ off topic comment Please refrain from such comments -Ron
    This is what TI9 did to my system:
    SYMPTOMS
    When you try to delete a file on an NTFS volume, you may receive the following error message:
    Cannot delete file name: The file or directory is corrupt and unreadable.
    The System event log in Windows NT 4.0 contains the following message:
    Event ID: 41
    Source: Diskperf
    Description: The file system structure on disk is corrupt and unreadable. Please run the chkdsk utility on the device with label "Volume_name"
    The System event log in Windows 2000 contains the following message:
    Event ID: 55
    Source: NTFS
    Description: The file system structure on disk is corrupt and unusable. Please run the chkdsk utility on the volume "Drive_letter:"
    If you run Chkdsk against the volume, Chkdsk may or may not make repairs, but afterwards you still cannot delete the corrupted file.
    CAUSE
    This behavior can occur if the NTFS volumes' Master File Table (MFT) is corrupted. The short and long file name pairs that are stored in the directory index record and the file names that are stored in the associated File Record Segment (FRS) contain case-sensitive characters that do not match.

    NTFS supports case-sensitive (POSIX) file names, but Chkdsk does not check file names in case-sensitive mode.

    For example, assume that the directory index record has a BADFILe.TXT entry but the FRS has a BADFILE.TXT entry for the file name. NTFS views this as being invalid or corrupted, but Chkdsk compares only the names and ignores the case. It does not make repairs.
    RESOLUTION
    To resolve this issue, back up the volume that contains the corrupted file(s) and exclude the corrupted file(s) from the backup job. Reformat the volume, and then restore from the backup.
     
    Last edited by a moderator: Jan 24, 2006
  2. tachyon42

    tachyon42 Registered Member

    Joined:
    Dec 26, 2004
    Posts:
    455
    Can you please explain how this is related to TrueImage?
     
  3. ErnestTwo

    ErnestTwo Registered Member

    Joined:
    Jan 12, 2006
    Posts:
    12
    I attempted to restore a directory with files from true image Image file and it created corrupted files on my drive that nothing short of C4 can remove. any other help you can provide? This product is absolute garbage. And they actually charge for this!!
     
  4. tachyon42

    tachyon42 Registered Member

    Joined:
    Dec 26, 2004
    Posts:
    455
    Please tell us more about your system configuration.

    What version of Windows do you have? What service pack?
    What version and build of TI are you using?
    Did you use this same version/build to both create and restore the .tib file?
    Did you get any errors during the restore?
    Did you use the Windows version or bootable rescue CD version for these operations?
    Are you restoring a complete disk which has multiple partitions or are you restoring a single partition?
    Does chkdsk /r give any errors after the restore?
    Does Windows start successfully after the restore?
    What was the first sign of a problem?
    Did you change any hardware between creating the .tib file and trying to restore it?
    What size disks do you have?
     
    Last edited: Jan 26, 2006
  5. Acronis Support

    Acronis Support Acronis Support Staff

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

    Thank you for choosing Acronis Disk Backup Software.

    Could you please do the following?

    - Create Acronis Report and Windows System Information as it is described in Acronis Help Post;

    - Rename the report created to report_before.txt;

    - Reproduce the problem (restore individual files\folders from a disk\partition image) and create Acronis Report once more;

    - Rename the report created to report_after.txt;

    - Make a screen shots of your consequent steps taken during the individual files\folders restoration process.

    Please submit a request for technical support with the subject indicating the you want to contact Alexey Popov. Attach all the collected files and information to your request along with the link to this thread. I'll forward this information to our Testing Team and they will certainly do their best in order to find out the actual reason for this problem.

    Thank you.
    --
    Alexey Popov
     
Thread Status:
Not open for further replies.