Skip to main content

True Image Home 2010 - Corrupt backups or False validation results?

Thread needs solution

I'm running True Image Home 2010 build 7046 on my Windows 7 Pro PC and I'm a bit concerned that I may be seeing false reports of corrupt backups and I'm looking for more information about this.

I've been using Acronis for years and when performing a backup I've always confirmed the validity of the backup immediately after the backup and I've never found any of my backups to be corrupted. On several recent backups however, the validation process, after a full, complete backup, ends fairly quickly and reports that my backup is corrupt. I read a few things on this forum about the potential for corrupt memory however my PC is less than a year old and I have run memory tests that indicate that I don't have a memory problem. Last month I had 1 failure followed by a successful backup. Tonight I had two back to back failures and I was only able to get a successful backup by burning a fresh bootable CD and performing the backup to my external harddrive and validation thru the CD version. I've used this product many times to pull myself out of a jam so I must be able to trust that my backups are not corrupt. Can anyone shed any light on this problem? Is there a cause, a solution a work around, etc so that I can perform my backups within Windows 7? Any help would be appreciated.

0 Users found this helpful

Why did you need a fresh bootable CD?

Do the validates fail if you validate independently of the backup task? That is, make the archive then manually go into the Validate command.

Did you let the memory test run a long time or just a pass or two. I consider running Memtest86+ overnight as a good test. PC being new is no guarantee RAM isn't bad and it could be you have some marginal RAM which is the worst kind of problem- works most of the time but not always.

Look in the Windows Event Viewer and see if there any problems reported particularly with your disk devices.

Reseat the disk cables. My validation problems were caused by flakey SATA cable - PC appeared to work fine for everything else. It was indicated in the Event Viewer as a problem and it even said to change the cable.

Do a chkdsk /r on the partition storing the archive. Good idea to run it on the partition being imaged as well.

Can you validate an archive with the CD that the Windows validation fails on? If you can do this reliably, it may indicate a Windows conflict issue. Unfortunately, if you have something flakey it is easy to jump to conclusions and thus needs a long series of tests using the CD to build confidence that this really is the cause.

Remember the most important recovery version is the CD version since this version and not the Windows version has to run to be able to restore the active partition. Windows can't be running when the active partition is deleted which TI does before the restoration.

The "corrupt" message really means TI can't read the archive file into RAM and properly reconstruct the 4000 checksums/GB such that they all compare perfectly with the ones included in the archive when it was created. Anything which causes this problem is suspect and it can be a pretty broad list of suspects just for hardware alone.

SeekForever.... Thanks for the reply and your insight.

I created a new bootable CD because I had not created one since updating to the current build.
I didn't realize that I could validate independently of the backup as I have always validate as part of the backup. I never trust ANY backup software to create a backup without a backup. Never the less, My backup from 4/30 did fail an indendent validation.

I only ran the 2 pass Windows 7 memory test vs. Memtest86+ as I could not figure out how to successfully create the bootable ISO CD. Nero was telling me it was creating an ISO CD but I think I may have been burning things incorrectly and there was no instructions I could find to actually burn the data to CD.

After reading your email I did run a chkdsk against both the source drive and the target drive and neither had errors.

I did check the event logs and found that I didn't have any errors but I did have a ton of Event 51 Disk warnings for DR1 (Disk Removable 1) - "An Error was detected diring a paging operation". I also looked at the date/time stamps of the warnings and they all were associated with dates and times when I was doing backups..

This particular external drive was connected to my Windows 7 system via firewire which was necessary on my old system as my old XP box did not like the USB connection at boot time as it would always hang my system on the system post before Windows XP loaded. Since this is a new system appears to be more acceptable to USB then my old system I switched from Firewire to USB.

The next step was to run a full system backup with a validation following the backup and I was able to successfully backup my system within Windows 7. Also when I looked at my event logs I had no Disk 51 Warnings after swapping the cables from Firewire to USB.

So... The problem could have been related to firewire vs USB or to a loose connection as I do recall having to remove a cable from the back of the PC in the month since my last backup. Anyway I feel that your insight and suggestions lead to a successful resolution to my problem.

Thanks so much for replying. It was MOST appreciated.

Solution to Event code: 0x000101F6 Operation with partition was terminated

Details: Operation with partition '0-0' was terminated.
Details:
The archive is corrupted. (0x70020)
Tag = 0xF5F8CBCF76155639

More information can be found at: http://kb.acronis.com/errorcode/
Event code: 0x000101F6

I hope this can get published somewhere to help everyone out there ... including Acronis & maybe even me Hint hint (free software or something perhaps) hint hint ... as so far, in all my searching I haven't come across the following solution.

I must point out however that for "try and decide" in TI Home 2010 Acronis does warn to turn off background defragmentation.

I was having terrible times getting any kind of reliability with validation, or mounting of images. Random failures galore including a restore that went terribly wrong and left a Netbook unbootable (Netbook = NO optical drive so had to create bootable USB Key etc etc I have much less hair now !!!)

Anyhow ... I was backing up using True Image Home 2010 on Windows 7 starter edition 2 GB ram to a Lacie 1 TB USB external Hard Drive. Never even thought of it but had the Lacie supplied "USB Boost" program running in boost mode. (does it automatically when drive is present)

Since turning that off while using True Image No more problems

I will wager that all these "USB Boost" type apps cause similar problems.

Hope this gets looked into and solved. But after many frustrating hours of troubleshooting I now have 100% reliability

Kami,
Vancouver
Canada