Skip to main content

File Corrupted

Thread needs solution

Hi, I purchased ATI 2016 a couple of months ago and it was working OK. For the past 2/3 weeks when I do a backup I get an error saying the file is corrupted possibly due to poor media quality (error code 0x0004000D).  I have assumed that my external hard drive is at fault and have ordered a new one. Can you help? Thank you. Stephen.

0 Users found this helpful

What are you backing up to?  If using a hard drive - it could be bad or have bad sectors.  You may want to run "chkdsk /f /r" against the destination disk to see if Windows finds bad sectors and can attempt to repair them.

You can also use the free version of HD Sentinel to see what it shows about yoru disk health.  

WD data lifeguard is another free one.

Your Windows system logs may show warnings/errors about disk health as well. 

Stephen,

Recommend downloading the Log File Viewer App...link below.  The Service log may provide additional information.  Also, if possible, please post the log here...I am confident one of the MVPs will be able to help.

https://forum.acronis.com/forum/115626

Regards,

FtrPilot

I have attached the logfile from c:\programdata\acronis\trueimagehome\logs to this post. Is that OK? 

Attachment Size
359792-129427.log 4.12 KB

Stephen, please run a check against your Entire PC as that looks to be the source for your backup and the corrupt file is more likely to be a file on the source disk than on the target for the backup, especially as the backup is reported as completing successfully in the log file you posted.

Stephen & Steve,

Even though the service log says "Operation has succeeded" there are no file names after the message "message=The following backups have been successfully created: "  So, this needs to be investigated further. 

Stephen, can you post any early service logs where the backup succeeded?  Is the current backup an incremental to an earlier full backup?

Thanks,

FtrPilot

FtrPilot,

I have attached a log from 10/02/2016 which was the first full backup and a log from the following week (17/02/2016) which was the first incremental. Both were successful. The current backup which is failing is the incremental one.

Attachment Size
359932-129454.log 5.4 KB
359932-129457.log 3.47 KB

I don't see anything that stands out in either log - they look like the backup were successful.

However, just because a backup was successful, does not mean the content within it is not already bad/corrupted.  There are options for "silent" in the Windows version of the Acronis app that supresseses hide errors - or, perhaps Acronis is stil able to backup a corrupted file on it's own.  You're only backing up corrupted data at that point though.

We're you able to run System Mechanic Disk Medic on your primary dive as well?  I'd get a second opinion from dskchk and possibly a third one from WD datalifeguard and/or the fee version of hard disk sentinel too.

 

Does it show which file it's hanging on when it errors out at the warning prompt?  

What about your Windows System logs - do you see any errors or warnings about hard drives?  

Stephen,

I have looked at your logs...On your E drive, there should be 10 tib files associated with the full backup:

E:\Entire PC (LAPTOP-6AMOSA9D)_full_b1_s1_v1.tib E:\Entire PC (LAPTOP-6AMOSA9D)_full_b1_s1_v2.tib E:\Entire PC (LAPTOP-6AMOSA9D)_full_b1_s1_v3.tib E:\Entire PC (LAPTOP-6AMOSA9D)_full_b1_s1_v4.tib E:\Entire PC (LAPTOP-6AMOSA9D)_full_b1_s1_v5.tib E:\Entire PC (LAPTOP-6AMOSA9D)_full_b1_s1_v6.tib E:\Entire PC (LAPTOP-6AMOSA9D)_full_b1_s1_v7.tib E:\Entire PC (LAPTOP-6AMOSA9D)_full_b1_s1_v8.tib E:\Entire PC (LAPTOP-6AMOSA9D)_full_b1_s1_v9.tib E:\Entire PC (LAPTOP-6AMOSA9D)_full_b1_s1_v10.tib

There should also be 1 tib file from the successful incremental backup:

E:\Entire PC (LAPTOP-6AMOSA9D)_inc_b1_s2_v1.tib

The first thing you should try is to mount the E:\Entire PC (LAPTOP-6AMOSA9D)_inc_b1_s2_v1.tib  file.  You can do this by double clicking on it using Windows Explorer.

Let us know if this works.  Whether this works or not will determine how to proceed.

Regards,

FtrPilot

 

sorry ftrpilot i deleted that backup by accident. i have started a new one, done a full backup plus one increment which seems to have worked. i have attached the logs. i double clicked the increment tib which opened in windows explorer.

Attachment Size
360050-129478.log 5.53 KB
360050-129481.log 3.84 KB

Stephen,

I am glad it is now working for you...

Thanks for closing the loop.

Regards,

FtrPilot