Catalog Damaged or Corrupt Errors
  • 09 Nov 2023
  • 2 Minutes to read
  • Dark
  • PDF

Catalog Damaged or Corrupt Errors

  • Dark
  • PDF

Article summary


Should a catalog become damaged or corrupt, you may see one of the following errors:

Macintosh Retrospect errors:

-24203 not a chunk file or badly damaged

-24202 chunk file map missing/damaged

-24201 chunk checksum didn’t match

Windows Retrospect errors:

-641 chunk checksum didn’t match

-642 chunk file map missing/damaged

-643 not a chunk file or badly damaged

These all basically mean that Retrospect has detected that the catalog file is corrupt or damaged. You will need to rebuild it, or restore it, if you have it backed up somewhere.?

How does this happen? Typically these errors can been seen if there is a crash or power failure while Retrospect is updating a catalog file. You can also see these errors if you have a configuration problem that is causing data corruption on your hard disk or network. If you have only see this error once, we recommend making a note of it, and moving on. If you have seen it multiple times, then you should work to figure out the source of the problem. Try saving your catalogs onto a different hard disk (we have seen obscure problems with data corruption being caused by specific hard disks). If the problem does not follow your catalogs to the new hard disk, consider the original hard disk suspect. It may be that the drive is corrupting other data as well. Consult your drive vendor’s documentation, or contact the vendor for assistance.

If the problem follows your catalogs to another hard disk, we recommend changing the computer you are running on, if possible. We have, in very rare cases, seen problems with computers that could not be easily quantified, that consistently led to chunk checksum errors on catalogs. These could be caused by RAM, ATAPI or SCSI bus configuration issues, USB or FireWire or IEEE 1394 conflicts or driver issues, or other failing hardware. These are terribly hard to troubleshoot; if things work well on another computer, we recommend switching the backups to that computer, and investigating what might be causing the corruptions on the original computer. Obviously this would be very complex to do. You may end up being satisfied with having your backups working again in their new configuration. It is up to you.

However you troubleshoot chunk checksum errors, the bottom line remains that they are caused by Retrospect’s data becoming corrupt. Retrospect itself is not corrupting the data, so your troubleshooting efforts should focus on the other variables, as noted above.

Last Update: August 20, 2012

Was this article helpful?