CRC test failed

Have questions about Backup4all, or having problems using it? Ask here for help.
Post Reply
Balok
Posts: 1
Joined: Fri Jan 05, 2018 6:03 pm

CRC test failed

Post by Balok »

I found a few old threads/posts between 2011 and 2015 which seem to address this problem. Some seemed to go away with version upgrades.

I am using Backup4all 7.1.251

A few files from each backup result in warnings, with the catalog CRC always 44, and the destination a different (presumably correct) CRC. Here's the excerpt from the log file:

[1/5/2018 12:08:03 PM] Warning: CRC test failed for file "E:\Documents\Reference\Sports\Ravens\2015 Flip Cards\20151001 at Steelers.pdf". CRC stored in catalog is 44, destination CRC is 99B4F932
[1/5/2018 12:08:03 PM] Warning: CRC test failed for file "E:\Documents\Reference\Sports\Ravens\2014 Flip Cards\20141005 at Colts.pdf". CRC stored in catalog is 44, destination CRC is 427FD16A
[1/5/2018 12:08:03 PM] Warning: CRC test failed for file "E:\Documents\Reference\Sports\Ravens\2007 Flip Cards\20071105 at Steelers.pdf". CRC stored in catalog is 44, destination CRC is D9F5E395
[1/5/2018 12:08:03 PM] Warning: CRC test failed for file "E:\Documents\Reference\Sports\Ravens\2016 Flip Cards\20160925 at Jacksonville.pdf". CRC stored in catalog is 44, destination CRC is 8E96817C

I ran a quick repair on this archive (not just the catalog) and it reported no errors.

Anyone know how to fix this?

I've also had files with a catalog CRC value of 0 and a destination CRC value that is different, but those have been open files (for example, files used as catalogues by a mail client that was running).

Adrian (Softland)
Posts: 1912
Joined: Wed Dec 16, 2009 12:46 pm

Re: CRC test failed

Post by Adrian (Softland) »

Hi,

In your case, it is possible that the 4 files could not be read correctly from sources when calculating the CRC, but they were correctly copied in destination.
When you ran again the backup, those files were backed up again, correctly.

Post Reply