Archived - Retrospect: Error Messages (2 of 2)
This article list the following Retrospect error messages and possible solutions.
1) Error 43 (file not found)
2) Error 54 (file busy/locked)
3) Error 102 (trouble communicating)
4) Error 108 (out of application memory)
5) Error 203 (hardware failure)
6) Error 205 (lost access to storage media)
7) Errors -24201 (chunk checksum failed) and -25040 (Catalog invalid or damaged)
8) Error 24062 (limited to 32000 files/folders)
For more information on Retrospect error messages, see article 13001: "Retrospect: Error Messages (1 of 2)"
1) Error 43 (file not found)
2) Error 54 (file busy/locked)
3) Error 102 (trouble communicating)
4) Error 108 (out of application memory)
5) Error 203 (hardware failure)
6) Error 205 (lost access to storage media)
7) Errors -24201 (chunk checksum failed) and -25040 (Catalog invalid or damaged)
8) Error 24062 (limited to 32000 files/folders)
For more information on Retrospect error messages, see article 13001: "Retrospect: Error Messages (1 of 2)"
1) Error 43 (file not found)
Error 43 (file not found) in Retrospect means that someone moved or deleted one or more files and folders on the target Macintosh while a backup or compare operation was in progress.
What to do:
Try backing up again. If this error continues to occur, run Apple's Disk First Aid, or another commercial disk checking utility on the disk in question.
2) Error 54 (file busy/locked)
There are two causes for Error 54 (file busy/locked):
* You are trying to back up System files using System 7 file sharing or AppleShare.
* Another application, such as FileMaker or 4th Dimension, had the files open, preventing Retrospect from accessing them.
What to do:
Back up the busy files from the local Macintosh, quit the application that owns the busy file, or install Retrospect Remote and back up the files.
3) Error 102 (trouble communicating)
Error 102 (trouble communicating) occurs when the Macintosh loses contact with the backup device. The most common cause is improper SCSI termination.
What to do:
Refer to the following information on SCSI issues below:
Troubleshooting SCSI Issues
If the Macintosh SCSI chain is not set up properly, communication errors may occur that can cause data corruption or system failures during backup operations. This following information is designed to give you guidance when encountering SCSI issues.
Some devices such as scanners, CD-ROM drives, or external SCSI floppy drives can cause issues on the SCSI bus, especially if they are turned off. If you are experiencing SCSI communication issues, make sure that all of your SCSI devices are powered ON when you start your Macintosh.
The following sample errors can indicate communication errors on the SCSI bus:
* File "Home" didn't compare at resource offset 10,750
* File "Tech Note" didn't compare at data offset 3,253
* Trouble writing: "1-Office Backup 2" (0), error 102 (trouble communicating)
* Trouble reading: "1-Office Backup 2" (0), error 102 (trouble communicating)
The above errors can usually be traced to some failure in the SCSI configuration, whether it is termination, a particular device, cabling, or device order. The most common cause of communication issues is improper termination or bad SCSI cables.
Termination
The general rule for termination is to have only two terminators on the SCSI bus, one at the beginning and one at the end. If you have only a single device on the SCSI bus, then only one terminator is needed. Most Macintosh computers purchased with internal hard disks are internally terminated. Some SCSI peripherals come with internal termination built-in, and must be placed at the end of a SCSI chain.
For more information, refer to your Macintosh user's guide and the manual that came with your hardware device.
SCSI Cables
Communication issues can be caused by bad or loose-fitting SCSI cables. Check all cables for proper seating in each connector. The entire length of your SCSI bus should not exceed 20 feet. Whenever possible, avoid using cables over six feet in length.
Device Order and Device Conflicts
To avoid issues caused by device order or device conflicts, make sure that each device has a unique SCSI address. If issues occur, try changing the order of SCSI devices or temporarily removing unneeded devices.
For further information on working with Retrospect and Retrospect A/UX, search the Tech Info Library by "Retrospect" or "Remote."
4) Error 108 (out of application memory)
Error 108 (out of application memory) means that Retrospect needs more memory.
What to do:
Increase the memory you have allocated to Retrospect by using the Get Info command from the Finder's File menu. The following is a guide for how much memory Retrospect will need to back up large volumes:
If you are backing up volumes that contain a large number of files, you may need more than the recommended amount of memory.
5) Error 203 (hardware failure)
Error 203 (hardware failure) means that the tape drive is failing because of a bad tape, a SCSI issue, or a mechanical error.
What to do:
* If the error only occurs when you use a particular tape, that tape is probably damaged. Try using a new tape.
* If the error occurs when you use any tape, you may have an issue with your SCSI chain or device. Try turning off the tape drive and computer for two minutes and then turning them back on again. See article 13022: "Retrospect: Troubleshooting SCSI Issues" for more information.
6) Error 205 (lost access to storage media)
Error 205 (lost access to storage media) usually indicates that the SCSI bus was reset during a backup, causing Retrospect to lose contact with the tape. Usually this error indicates a SCSI issue and may be accompanied by an Error 102 (trouble communicating).
What to do:
If Error 102 accompanies Error 205, see article 13022: "Retrospect: Troubleshooting SCSI Issues."
If Error 102 does not accompany Error 205 and SCSI communication issues have been ruled out, the next step is to check for media failure on the source volume. Some hard disks reset the SCSI bus when they sense they are experiencing a media failure. Try testing the drive with the software that was originally used to format it.
7) Errors -24201 (chunk checksum failed) and -25040 (Catalog invalid or damaged)
Errors -24201 (chunk checksum failed) and -25040 (Catalog invalid or damaged) mean that a Catalog or other Retrospect 2.0 format file is unusable.
What to do:
If the error occurs when you are trying to back up to a particular StorageSet, you need to rebuild the Catalog for that StorageSet. After the recatalog, reselect this StorageSet in your scripts. If the error occurs when you launch Retrospect, the Retro.Configuration file may be unusable. Remove this file from the Retrospect Preferences folder and launch Retrospect again.
After you do this, you will need to recreate your scripts and other settings.
Alternatively, restore a previous copy of your Retro.Configuration file from one of your StorageSets.
8) Error 24062 (limited to 32000 files/folders)
Error 24062 (limited to 32000 files/folders) occurs if you:
* try to back up a volume that contains more than 32,000 files and folders, or
* perform a search request which finds more than this number of items.
What to do:
Partition your hard disk into two or more partitions, keeping less than 32,000 items in each partition. Or define each of the top level folders of the volume as a Subvolume.
Note: Dantz strongly recommends that you store fewer than 32,000 files on any single volume, both for Retrospect compatibility and because the Macintosh file system becomes less stable with this many files on a single volume.
Note: For further information on working with Retrospect and Retrospect A/UX, search the Tech Info Library by "Retrospect" or "Remote."
Error 43 (file not found) in Retrospect means that someone moved or deleted one or more files and folders on the target Macintosh while a backup or compare operation was in progress.
What to do:
Try backing up again. If this error continues to occur, run Apple's Disk First Aid, or another commercial disk checking utility on the disk in question.
2) Error 54 (file busy/locked)
There are two causes for Error 54 (file busy/locked):
* You are trying to back up System files using System 7 file sharing or AppleShare.
* Another application, such as FileMaker or 4th Dimension, had the files open, preventing Retrospect from accessing them.
What to do:
Back up the busy files from the local Macintosh, quit the application that owns the busy file, or install Retrospect Remote and back up the files.
3) Error 102 (trouble communicating)
Error 102 (trouble communicating) occurs when the Macintosh loses contact with the backup device. The most common cause is improper SCSI termination.
What to do:
Refer to the following information on SCSI issues below:
Troubleshooting SCSI Issues
If the Macintosh SCSI chain is not set up properly, communication errors may occur that can cause data corruption or system failures during backup operations. This following information is designed to give you guidance when encountering SCSI issues.
Some devices such as scanners, CD-ROM drives, or external SCSI floppy drives can cause issues on the SCSI bus, especially if they are turned off. If you are experiencing SCSI communication issues, make sure that all of your SCSI devices are powered ON when you start your Macintosh.
The following sample errors can indicate communication errors on the SCSI bus:
* File "Home" didn't compare at resource offset 10,750
* File "Tech Note" didn't compare at data offset 3,253
* Trouble writing: "1-Office Backup 2" (0), error 102 (trouble communicating)
* Trouble reading: "1-Office Backup 2" (0), error 102 (trouble communicating)
The above errors can usually be traced to some failure in the SCSI configuration, whether it is termination, a particular device, cabling, or device order. The most common cause of communication issues is improper termination or bad SCSI cables.
Termination
The general rule for termination is to have only two terminators on the SCSI bus, one at the beginning and one at the end. If you have only a single device on the SCSI bus, then only one terminator is needed. Most Macintosh computers purchased with internal hard disks are internally terminated. Some SCSI peripherals come with internal termination built-in, and must be placed at the end of a SCSI chain.
For more information, refer to your Macintosh user's guide and the manual that came with your hardware device.
SCSI Cables
Communication issues can be caused by bad or loose-fitting SCSI cables. Check all cables for proper seating in each connector. The entire length of your SCSI bus should not exceed 20 feet. Whenever possible, avoid using cables over six feet in length.
Device Order and Device Conflicts
To avoid issues caused by device order or device conflicts, make sure that each device has a unique SCSI address. If issues occur, try changing the order of SCSI devices or temporarily removing unneeded devices.
For further information on working with Retrospect and Retrospect A/UX, search the Tech Info Library by "Retrospect" or "Remote."
4) Error 108 (out of application memory)
Error 108 (out of application memory) means that Retrospect needs more memory.
What to do:
Increase the memory you have allocated to Retrospect by using the Get Info command from the Finder's File menu. The following is a guide for how much memory Retrospect will need to back up large volumes:
- 1,700K for 3,500 files/folders (This is the default setting.)
- 4,000K for 10,000 files/folders
- 6,000K for 20,000 files/folders
- 8,000K for 32,000 files/folders
If you are backing up volumes that contain a large number of files, you may need more than the recommended amount of memory.
5) Error 203 (hardware failure)
Error 203 (hardware failure) means that the tape drive is failing because of a bad tape, a SCSI issue, or a mechanical error.
What to do:
* If the error only occurs when you use a particular tape, that tape is probably damaged. Try using a new tape.
* If the error occurs when you use any tape, you may have an issue with your SCSI chain or device. Try turning off the tape drive and computer for two minutes and then turning them back on again. See article 13022: "Retrospect: Troubleshooting SCSI Issues" for more information.
6) Error 205 (lost access to storage media)
Error 205 (lost access to storage media) usually indicates that the SCSI bus was reset during a backup, causing Retrospect to lose contact with the tape. Usually this error indicates a SCSI issue and may be accompanied by an Error 102 (trouble communicating).
What to do:
If Error 102 accompanies Error 205, see article 13022: "Retrospect: Troubleshooting SCSI Issues."
If Error 102 does not accompany Error 205 and SCSI communication issues have been ruled out, the next step is to check for media failure on the source volume. Some hard disks reset the SCSI bus when they sense they are experiencing a media failure. Try testing the drive with the software that was originally used to format it.
7) Errors -24201 (chunk checksum failed) and -25040 (Catalog invalid or damaged)
Errors -24201 (chunk checksum failed) and -25040 (Catalog invalid or damaged) mean that a Catalog or other Retrospect 2.0 format file is unusable.
What to do:
If the error occurs when you are trying to back up to a particular StorageSet, you need to rebuild the Catalog for that StorageSet. After the recatalog, reselect this StorageSet in your scripts. If the error occurs when you launch Retrospect, the Retro.Configuration file may be unusable. Remove this file from the Retrospect Preferences folder and launch Retrospect again.
After you do this, you will need to recreate your scripts and other settings.
Alternatively, restore a previous copy of your Retro.Configuration file from one of your StorageSets.
8) Error 24062 (limited to 32000 files/folders)
Error 24062 (limited to 32000 files/folders) occurs if you:
* try to back up a volume that contains more than 32,000 files and folders, or
* perform a search request which finds more than this number of items.
What to do:
Partition your hard disk into two or more partitions, keeping less than 32,000 items in each partition. Or define each of the top level folders of the volume as a Subvolume.
Note: Dantz strongly recommends that you store fewer than 32,000 files on any single volume, both for Retrospect compatibility and because the Macintosh file system becomes less stable with this many files on a single volume.
Note: For further information on working with Retrospect and Retrospect A/UX, search the Tech Info Library by "Retrospect" or "Remote."
Last Modified: Feb 19, 2012
