shakeyguy Posted April 11, 2002 Report Share Posted April 11, 2002 I appoligise in advance for the length of this message but its the only clear way I could ask my question; Following my first use on 2-18 this was my log data, I BELIEVE the only files that didnt get copied based on execution error printout are ones that I really do not care about. First question ius is this backup usable with that exception? + Executing Immediate Backup at 2/18/2002 11:52 AM To backup set first full-2-18-02... - 2/18/2002 11:52:37 AM: Copying Drive C (C:) 2/18/2002 12:38:40 PM: Snapshot stored, 9,579 KB 2/18/2002 12:38:54 PM: Comparing Drive C (C:) Trouble reading: "first full-2-18-02" (2138), error -206 (drive reported a failure: dirty heads, bad media, etc.) Trouble reading: "first full-2-18-02" (2171), error -206 (drive reported a failure: dirty heads, bad media, etc.) Trouble positioning: "first full-2-1 ~ Trouble positioning: "first full-2-18-02" (2361), error -206 (drive reported a failure: dirty heads, bad media, etc.) Trouble reading: "first full-2-18-02" (2361), error -206 (drive reported a failure: dirty heads, bad media, etc.) Additional error information for device "Yamaha CD-RW" [1:1], Sense > 70 00 03 00 00 00 00 0a 00 00 00 00 11 05 00 00 00 00 (YAMAHA |CRW3200E |1.0b) 2/18/2002 1:20:33 PM: 22 execution errors Remaining: 10 files, 41.2 MB Completed: 21767 files, 2.2 GB, with 25% compression Performance: 53.7 MB/minute (51.2 copy, 56.6 compare) Duration: 01:27:57 (00:06:19 idle/loading/preparing) Quit at 2/18/2002 1:27 PM + Retrospect Express version 5.6.132 Launched at 2/18/2002 2:27 PM + Retrospect Driver Update, version 2.7.104 --------------------------------------------------------------------------------------------------------------------------------- Believing it acceptable yesterday I did a further backup of new files and received this log report. + Retrospect Express version 5.6.132 Launched at 4/10/2002 6:28 PM + Retrospect Driver Update, version 2.7.104 + Executing Immediate Backup at 4/10/2002 6:29 PM To backup set first full-2-18-02... - 4/10/2002 6:29:41 PM: Copying Drive C (C:) 4/10/2002 6:44:36 PM: Snapshot stored, 9,759 KB 4/10/2002 6:44:49 PM: Comparing Drive C (C:) Trouble reading: "3-first full-2-18-02" (2274), error -206 (drive reported a failure: dirty heads, bad media, etc.) Additional error information for device "Yamaha CD-RW" [1:1], Sense > 70 00 03 00 00 00 00 0a 00 00 00 00 11 05 00 00 00 00 (YAMAHA |CRW3200E |1.0b) 4/10/2002 6:55:04 PM: 1 execution errors Remaining: 1 files, 228.1 MB Completed: 1938 files, 402.5 MB, with 8% compression Performance: 49.4 MB/minute (50.9 copy, 47.4 compare) Duration: 00:25:23 (00:04:28 idle/loading/preparing) Quit at 4/10/2002 6:56 PM + Retrospect Express version 5.6.132 Launched at 4/11/2002 10:33 AM + Retrospect Driver Update, version 2.7.104 PLEASE: Am I safely backed up???? This is a new cd-rw unit on 2-18 and new high quality cd-rw disks. Thank you Mel S. Link to comment Share on other sites More sharing options...
ZakB Posted April 17, 2002 Report Share Posted April 17, 2002 You are experiencing a device communication error. It seems like your backup is completing, however, not successfully. Because of the error 206, your disks are not being compared effectively. You will need to correct the error –206 so that you will have a successful backup in the future. All 200-series errors are generated by hardware and reported through Retrospect. The first course of action to attempt to isolate the problem by backing up to a new piece of media. If the new media works, then the previous one(s) may have failed. If you see the error on all media you try, use the following checklist: 1) Try using a different brand of media, if one exists for your backup device. Follow the manufacturer's recommended list of brands. 3) Isolate the device. Another device on the USB/SCSI/FireWire chain may be interfering with the backup device's communication. Turn off your computer and all USB/SCSI/FireWire devices. If your backup device is connected to your computer through a hub or another USB/SCSI/FireWire device, unplug it and connect it directly to a USB/FireWire port on the computer. If it is already connected directly to the computer, try changing ports or SCSI card. If the problem persists, do not reconnect the other devices, and continue down the checklist. 4) Cabling. You may have a bad cable. Replace the USB/SCSI/FireWire cable that connects the device to the computer. 5) Update or reinstall the USB/SCSI/FireWire adapter drivers and/or firmware. Corrupt drivers can cause issues that may not be otherwise detectable. Check the manufacturer's or vendor's website for updated drivers. 6) Completely uninstall any other third-party backup software that may be on your machine, including any drivers that software may have loaded for the device. 7) The system board or USB/SCSI/FireWire adapter in the computer may be having a problem. Install Retrospect on another computer, if available, and try the device there as the only USB/SCSI/FireWire device. 8) The device itself may be defective. If you have implemented all of the preceding steps and get failures on new media after changing cables, software/firmware and computers, then the backup device, being the only factor that has not changed, is the culprit. Contact your vendor for servicing or warranty information. Link to comment Share on other sites More sharing options...
shakeyguy Posted April 18, 2002 Author Report Share Posted April 18, 2002 Thank you Zac. This is very informative information and I will incorporate it into my troubleshooting next backup. One question. I did not discover the problem until I ran a verify. Is there any indication of trouble as I burn the disks so hours do not get wasted? Mel Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.