Skip to main content

This File is Corrupted

Thread needs solution

    I do a full backup and set my backups to Incremental after that and I keep getting "The file is corrupted and seems to be due to Poor Media Quality". Why is it that I can do a FULL backup without a problem and the minute I do an Incremental on my second one I get the error that my file is corrupted and the error is due possibly to poor media quality. I am using a Verbatim 931 GB external drive on a windows 10 Acer Laptop. I just don't get this at all. I never had this kind of error on any previous Acronis True Image programs.

0 Users found this helpful

A few random thoughts:

Can you tell whether it is the source or destination file that is being complained about?

Did you move or rename the successful backup file?  That will upset ATI.

Do you have the MVP Log Viewer program?  If so, does it give any clue?
If you don't have it, download it from the "MVP User Tools and Tutorial" page mentioned in the Forum's sidebar.

Did you try a Validate on the successful backup file?  If ATI can validate it, it is probably not physically corrupted (but could still have logical corruptions).

I would guess that ATI is complaining about the target drive, and that it is having intermittent errors accessing it (but that's just a guess).  Are any other programs having trouble accessing files on the drive?

Seeing the log messages for this issue will be a help in trying to understand the context and also which file is being reported as corrupt?  Otherwise sorry but too little to go on here.

p.s. I would never recommend using 'Incremental forever' for the backup scheme - incremental chains need to be kept to a sensible length as every file is dependent on the ones before it and the longer the chain the greater the chance of the chain being broken!  The default schemes use only around 5 or 6 files in a chain before making a new full backup image.

Patrick O'Keefe wrote:

A few random thoughts:

Can you tell whether it is the source or destination file that is being complained about?

Did you move or rename the successful backup file?  That will upset ATI.

Do you have the MVP Log Viewer program?  If so, does it give any clue?
If you don't have it, download it from the "MVP User Tools and Tutorial" page mentioned in the Forum's sidebar.

Did you try a Validate on the successful backup file?  If ATI can validate it, it is probably not physically corrupted (but could still have logical corruptions).

I would guess that ATI is complaining about the target drive, and that it is having intermittent errors accessing it (but that's just a guess).  Are any other programs having trouble accessing files on the drive?

   I downloaded the MVP log viewer as you asked and installed the standalone .exe program and ran it. I will upload the results if I did this properly.

    I will have to take a guess and say it is the latter or destination file that is being complained about. Here is how I do it: I have a 931 GB Verbatim external hard drive First off it is a USB3 and the computer laptop USB ports are 2. Thought the difference might have something to do with corrupting the data file, but what do I know. I validate every backup I do at the time of doing the backup I will upload the MVP log to you if I did it properly and also a snip of the external hard drive and the way it came out. Notice the first backup was a successful full backup. The 2nd 3rd and 4th were all supposed to be #2. Check the dates. They were all done at the same date and somehow were split 3 ways. strange but true. Maybe you can make some sense out of this.

Attachment Size
505928-170286.jpg 23.05 KB
505928-170288.txt 179 bytes
505928-170290.log 1.08 KB

Randy, thanks for the further information but unfortunately this does not tells us much more!

The image shows that your backup is either being interrupted & restarted, or else the file is being split for some reason, hence why you have 'My partitions_inc_b1_s2_v1.tib', 'My partitions_inc_b1_s2_v2.tib' and,'My partitions_inc_b1_s2_v3.tib' files.

There is no information on the size of these v1, v2 and v3 files to show if they are being split at a specific size?

The text file is just a list of folders, and the log file is not the ti_demon logs that are needed here.

When you run the MVP Log Viewer tool, it opens by default to the TI_demon logs, so you need to look at the contents of these shown in the lower panel for each log shown in the top panel.

What format is used for your 931GB external backup drive?  Ideally this should be NTFS (either with GPT or MBR) to allow backup files to be created as a single file.  If is FAT32 this will split files into 2GB segments due to the limitations of the file system.

   Hi Steve, 

                  I decided to uninstall and re-install the whole program and had total success. I ran a full backup to start and used the default incremental as the base backup plan. It worked like a charm, so whatever was tripping it was in the old build. I updated to 17750 and that seemed to do the trick as it went through a full and 1 incremental w/o a hitch. Just the way I like it. What I don't understand is how to get the proper log files with MVP. I ran the standalone and the extracted file and it still comes out like the ones that I posted. Could you explain to me how I can come up with the proper log files? 

                   I downloaded the MVP .zip file and extracted the files to a data drive and then ran the standalone .exe and you saw what happened. I look at yours and somehow mine aren't running properly. I ran them as administrator and still no luck. Both backups I did today ran properly and came up aces.

Randy, great to hear that your backups are now running fine and as expected.

When you mention the MVP zip file, that sounds more like the MVP Custom ATIPE builder tool than the MVP Log Viewer tool - the latter comes as a standalone .exe file.

MVP Log Viewer & Custom ATI PE Builder available from Community Tools page.

Log Viewer

A simple application that allows viewing Acronis True Image service logs in a graphical user interface.

  1. Download the tool.
  2. Double-click to run it.
  3. Using date and time, find the log you want to check:

There is nothing to install just a standalone program to use as needed.