Backup files initially identified as corrupt verified as normal later.

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 8
Comments: 6

I use Windows 7 64-bit. With Acronis true image home 2010

I'm looking for help explaining a problem I had where a backup file with was identified as corrupted multiple times when I attempted to restore from my backup CD but ultimately was both verified as normal had also mounted successfully as a virtual disk. when Windows was reinstall.

I decided to do a restore the from a backup which was only several days old. I ran this from Windows but when the computer rebooted it only said that the hard drive was corrupted. I booted from my backup CD which repeatedly said that this backup was corrupt. Both the incremental backup-up which resides properly in the same directory as the full backup-and the somewhat older full backup itself.

Ultimately I was able to restore from a backup which I made about four months ago. Once I reinstalled Windows I was unable to verify that the more recent files-the one that had been identified as corrupt-were intact. I I checked these with the verify function. I was also able to mount it as a virtual disk in Windows and obtain files from it.

The backup CD was made with the most recent version of Acronis-the same version that I created the backup which was misidentified as corrupt. 7064.

Any suggestions or analyses appreciated.. My concern of course is that I need to be able to a restore from backups which are proven to be intact.

Thank you in advance

Kevin Brady

Tue, 06/01/2010 - 03:36
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 11
Comments: 1342

Hello Kevin,

Let me assist you with the issue.

If you have a corrupt backup and need to restore data from it, the general strategy would be to:

  1. Copy the corrupt backup archive to the internal hard disk drive (if the backup is on an external resource/media);
  2. Mount or explore the backup archive and try to restore files or folders from it.

Another reason that may cause cause the issue is a corrupt memory module, so it's recommended to run memtest utility to check it.

1. Download the memtest utility:

2. Unpack the downloaded archive;

3. Burn the ISO file to a CD (see Burning an ISO Image);

  • (!) Please make sure you burn the file as an Image to have the CD bootable;

4. After that boot your machine from the media and memtest will start automatically.

If the memory module is faulty there will appear an error count in the Errors column.

The longer you run memtest, the better. If you can run memtest overnight without errors then you can be sure that your RAM functions correctly.

Please let me know if the issue still persists or if you have any additional questions.

Thank you.

Tue, 06/01/2010 - 09:45
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 8
Comments: 6

This is a good start. Thank you.

Could you please expand on your answer. Actually I only have one internal hard drive because it is a small computer with a solid-state drives. I guess I need to point out that I have had this problem with other earlier Acronis products. Archives are first identified as corrupted and then sometimes we either retries or by waiting they are suddenly recognized as healthy and can be restored from.

I'm a little concerned that there is some tendency for a Kronos backup archives to appear corrupted when they are not. Is this a recognize tendency?

I will run a test both on the external hard drive where the archives reside.

Thank you very much..

Tue, 06/01/2010 - 17:48
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Frequent Poster
Posts: 2
Comments: 570

I'd say no, this is not the norm. It is far, far more common for users to complain that they validated properly but then failed validation later.

The "archive corrupt" message really means that TI cannot read the archive from its storage device into RAM and successfully recreate and match the numerous checksums with the corresponding ones that were placed in the archive when it was created. In other words, anything that causes a bad disk read, transfer of data into RAM, or even calculating the checksums can cause the problem. Typical causes are bad area on disk, bad RAM, too aggressive RAM timings, overclocking, etc.

My first guess on your issue is that you have something marginal - it doesn't work, then it works, then it doesn't, then it does.... Perhaps the components were significantly warmer after creating and validating an archive than they were when you just validated it and you have some heat-sensitive component issue. This is a reason why Memtest86+ should be allowed to run overnight so it gets everything up to a warmer temperature than just a single run but even then without a lot of disk activity and more exotic graphics work the PC likely is not as warm as it normally can get.

Tue, 06/01/2010 - 18:52
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 12

Unfortunately, I had the same problem with the same negative outcome. Check the other posts regarding corrupt tib's. As a result of my experience and the reported experience of others, I no longer use Acronis True Image as I find it to be unreliable.

Check the other posts regarding corrupt tib's. For example, see 9603: ATIH creates TIB files, but Recovery indicates corrupted TIB.

Wed, 03/02/2011 - 12:17