webdeck Posted February 26, 2003 Report Share Posted February 26, 2003 I just switched to Mac OS 10.2.4 from Mac OS 9.2.2, using the same install of Retrospect 5.0.238. I have not had a successful backup to my SCSI Ecrix VXA-1 tape drive since doing so. I always get error 102 (trouble communicating). I have never had problems with Mac OS 9. The VXA drive and a JAZ drive are the only things on my SCSI bus. My SCSI card is an Adaptec 2930CU. Once this error happens, Retrospect freezes. I hear my tape drive make a whirring sound every 15-30 seconds. I have to force quit retrospect and reboot to gain access to the tape drive again. I turned on the additional file and SCSI logging in the preferences, but left all the other advanced prefs at their defaults - here is what my log looked like for my last failed backup attempt: ? Retrospect version 5.0.238 automatically launched at 2/26/2003 2:02 AM + Retrospect Driver Update, version 3.4.103 kyxDidLoad: KyxClass class version 0x503 loaded arxDidLoad: ArxClass class version 0x503 loaded nildrDidLoad: DatClass class version 0x501 loaded onstDidLoad: OnstClass class version 0x501 loaded dltDidLoad: DltClass class version 0x502 loaded dsixDidLoad: DsixClass class version 0x504 loaded datDidLoad: DatClass class version 0x503 loaded dprwDidLoad: DVD_PRW class version 0x502 loaded dvdVPCTDidLoad: DVD_VPCT class version 0x501 loaded cdrVPCTDidLoad: CDR_VPCT class version 0x501 loaded cdrVPCTbDidLoad: CDR_VPCT_BASE class version 0x501 loaded cdrVarPackDidLoad: CDR_VARPACK class version 0x501 loaded cdrFixPackDidLoad: CDR_FIXPACK class version 0x501 loaded dvdMMCDidLoad: Dvd_MMC_Class class version 0x501 loaded cdrMMCDidLoad: Cdr_MMC_Class class version 0x501 loaded cdrMMCBaseDidLoad: Cdr_MMC_Base_Class class version 0x501 loaded cdrFormatterDidLoad: CDR_FORMATTER class version 0x501 loaded cdrBaseDidLoad: Cdr_Base_Class class version 0x501 loaded cdrDidLoad: CdrClass class version 0x501 loaded + Normal backup using FredG4 VXA at 2/26/2003 2:02 AM DeviceAccess: Opened Device PIONEER|DVD-RW DVR-104|1.33 DeviceAccess: Opened Device ECRIX|VXA-1|2C8C SCSI SCSI-A:3: 2:02:32 AM Read <1a 00 0f 00 1c 00> [28 bytes] [28 bytes] > 1b 81 10 08 80 13 88 00 00 02 00 00 0f 0e c0 80 00 00 00 03 00 00 00 03 00 00 00 00 To backup set FredG4-VXA [017]… - 2/26/2003 2:02:30 AM: Copying MacOS X… SCSI SCSI-A:3: 2:15:51 AM Command <00 00 00 00 00 00> SCSI SCSI-A:3: 2:15:51 AM Read <1a 00 0f 00 1c 00> [28 bytes] [28 bytes] > 1b 81 10 08 80 13 88 00 00 02 00 00 0f 0e c0 80 00 00 00 03 00 00 00 03 00 00 00 00 SCSI SCSI-A:3: 2:15:52 AM Write <15 10 00 00 1c 00> [28 bytes] [28 bytes] > 00 00 10 08 80 00 00 00 00 02 00 00 0f 0e 40 80 00 00 00 03 00 00 00 03 00 00 00 00 SCSI SCSI-A:3: 2:15:52 AM Command <01 00 00 00 00 00> SCSI SCSI-A:3: 2:15:52 AM Command <00 00 00 00 00 00> SCSI SCSI-A:3: 2:15:52 AM Read <1a 00 0f 00 1c 00> [28 bytes] [28 bytes] > 1b 81 10 08 80 13 88 00 00 02 00 00 0f 0e 40 80 00 00 00 03 00 00 00 03 00 00 00 00 SCSI SCSI-A:3: 2:15:52 AM Write <15 10 00 00 1c 00> [28 bytes] [28 bytes] > 00 00 10 08 80 00 00 00 00 02 00 00 0f 0e 40 80 00 00 00 03 00 00 00 03 00 00 00 00 SCSI SCSI-A:3: 2:15:52 AM Read <08 01 00 00 01 00> [131,072 bytes] [131,072 bytes] > 52 78 76 72 44 41 54 20 00 02 40 00 ba 80 cc f8 ba 80 cc f8 00 02 00 00 48 22 00 00 00 00 00 00 SCSI SCSI-A:3: 2:16:01 AM Read <1a 00 0f 00 1c 00> [28 bytes] [28 bytes] > 1b 81 10 08 80 13 88 00 00 02 00 00 0f 0e 40 80 00 00 00 03 00 00 00 03 00 00 00 00 SCSI SCSI-A:3: 2:16:01 AM Write <15 10 00 00 1c 00> [28 bytes] [28 bytes] > 00 00 10 08 80 00 00 00 00 02 00 00 0f 0e c0 80 00 00 00 03 00 00 00 03 00 00 00 00 SCSI SCSI-A:3: 2:16:01 AM Command <00 00 00 00 00 00> SCSI SCSI-A:3: (<00> passed 7 more times) SCSI SCSI-A:3: 2:16:02 AM Command <01 00 00 00 00 00> SCSI SCSI-A:3: (<01> passed 1 more times) SCSI SCSI-A:3: 2:16:16 AM Read <03 00 00 00 1a 00> [26 bytes] [26 bytes] > f0 00 40 00 00 00 00 18 00 00 00 00 00 00 00 00 00 00 00 01 00 00 01 12 0d 95 SCSI SCSI-A:3: 2:16:16 AM Read <1a 00 0f 00 1c 00> [28 bytes] [28 bytes] > 1b 81 10 08 80 13 88 00 00 02 00 00 0f 0e c0 80 00 00 00 03 00 00 00 03 00 00 00 00 SCSI SCSI-A:3: 2:16:16 AM Write <15 10 00 00 1c 00> [28 bytes] [28 bytes] > 00 00 10 08 80 00 00 00 00 02 00 00 0f 0e c0 80 00 00 00 03 00 00 00 03 00 00 00 00 SCSI SCSI-A:3: 2:16:17 AM Write <0a 01 00 00 01 00> [131,072 bytes] [131,072 bytes] > 52 78 76 72 44 41 54 20 00 02 40 01 ba 81 d3 f0 ba 81 d3 f0 00 02 00 00 48 22 00 00 00 00 00 00 SCSI SCSI-A:3: 2:16:17 AM Command <10 00 00 00 00 80> SCSI SCSI-A:3: 2:16:22 AM Command <00 00 00 00 00 00> SCSI SCSI-A:3: 2:16:26 AM Write <0a 01 00 00 01 00> [131,072 bytes] [131,072 bytes] > 53 67 6d 74 00 00 00 9a 52 78 76 72 00 02 00 00 00 01 ba 81 d0 b6 00 00 00 17 00 00 00 00 ff 70 SCSI SCSI-A:3: (<0a> passed 1599 more times) SCSI SCSI-A:3: 2:17:57 AM Command <10 00 00 00 01 80> SCSI SCSI-A:3: 2:17:58 AM Command <10 00 00 00 00 80> SCSI SCSI-A:3: 2:17:58 AM Read <34 00 00 00 00 00 00 00 00 00> [20 bytes] [20 bytes] > 00 00 00 00 00 00 06 42 00 00 00 00 00 00 00 00 00 00 00 00 datReadPos: fm_pos 0x0, locPos 0x642, pos 0x0 SCSI SCSI-A:3: 2:17:58 AM Command <00 00 00 00 00 00> SCSI SCSI-A:3: (<00> passed 4 more times) SCSI SCSI-A:3: 2:18:08 AM Write <0a 01 00 00 01 00> [131,072 bytes] [131,072 bytes] > 53 67 6d 74 00 00 00 9a 52 78 76 72 00 02 00 00 00 01 ba 81 d0 b6 00 00 00 18 00 00 06 42 ff 6a SCSI SCSI-A:3: (<0a> passed 1599 more times) SCSI SCSI-A:3: 2:19:38 AM Command <10 00 00 00 01 80> SCSI SCSI-A:3: 2:19:38 AM Command <10 00 00 00 00 80> SCSI SCSI-A:3: 2:19:39 AM Read <34 00 00 00 00 00 00 00 00 00> [20 bytes] [20 bytes] > 00 00 00 00 00 00 0c 83 00 00 00 00 00 00 00 00 00 00 00 00 datReadPos: fm_pos 0x642, locPos 0xc83, pos 0x0 SCSI SCSI-A:3: 2:19:39 AM Command <00 00 00 00 00 00> SCSI SCSI-A:3: (<00> passed 4 more times) SCSI SCSI-A:3: 2:19:41 AM Write <0a 01 00 00 01 00> [131,072 bytes] [131,072 bytes] > 53 67 6d 74 00 00 00 9a 52 78 76 72 00 02 00 00 00 01 ba 81 d0 b6 00 00 00 19 00 00 0c 83 ff 64 SCSI SCSI-A:3: (<0a> passed 1599 more times) SCSI SCSI-A:3: 2:20:25 AM Command <10 00 00 00 01 80> SCSI SCSI-A:3: 2:20:26 AM Command <10 00 00 00 00 80> SCSI SCSI-A:3: 2:20:26 AM Read <34 00 00 00 00 00 00 00 00 00> [20 bytes] [20 bytes] > 00 00 00 00 00 00 12 c4 00 00 00 00 00 00 00 00 00 00 00 00 datReadPos: fm_pos 0xc83, locPos 0x12c4, pos 0x0 SCSI SCSI-A:3: 2:20:26 AM Command <00 00 00 00 00 00> SCSI SCSI-A:3: (<00> passed 4 more times) SCSI SCSI-A:3: 2:20:29 AM Write <0a 01 00 00 01 00> [131,072 bytes] [131,072 bytes] > 53 67 6d 74 00 00 00 9a 52 78 76 72 00 02 00 00 00 01 ba 81 d0 b6 00 00 00 1a 00 00 12 c4 ff 5d SCSI SCSI-A:3: (<0a> passed 1599 more times) SCSI SCSI-A:3: 2:21:35 AM Command <10 00 00 00 01 80> SCSI SCSI-A:3: 2:21:35 AM Command <10 00 00 00 00 80> SCSI SCSI-A:3: 2:21:35 AM Read <34 00 00 00 00 00 00 00 00 00> [20 bytes] [20 bytes] > 00 00 00 00 00 00 19 05 00 00 00 00 00 00 00 00 00 00 00 00 datReadPos: fm_pos 0x12c4, locPos 0x1905, pos 0x0 SCSI SCSI-A:3: 2:21:36 AM Command <00 00 00 00 00 00> SCSI SCSI-A:3: (<00> passed 4 more times) SCSI SCSI-A:3: 2:21:48 AM Write <0a 01 00 00 01 00> [131,072 bytes] [131,072 bytes] > 53 67 6d 74 00 00 00 9a 52 78 76 72 00 02 00 00 00 01 ba 81 d0 b6 00 00 00 1b 00 00 19 05 ff 57 SCSI SCSI-A:3: (<0a> passed 549 more times) SCSI SCSI-A:3: 2:22:17 AM Command <10 00 00 00 01 80> SCSI SCSI-A:3: 2:22:18 AM Command <10 00 00 00 00 80> SCSI SCSI-A:3: 2:22:18 AM Read <34 00 00 00 00 00 00 00 00 00> [20 bytes] [20 bytes] > 00 00 00 00 00 00 1b 2c 00 00 00 00 00 00 00 00 00 00 00 00 datReadPos: fm_pos 0x1905, locPos 0x1b2c, pos 0x0 SCSI SCSI-A:3: 2:22:32 AM Read <08 01 00 00 01 00> [131,072 bytes] Sense > f0 00 08 00 00 00 01 18 00 00 00 00 00 05 00 00 00 00 SCSI SCSI-A:3: 2:23:01 AM Read <34 00 00 00 00 00 00 00 00 00> [20 bytes] [20 bytes] > 00 00 00 00 00 00 1b 2c 00 00 00 00 00 00 00 00 00 00 00 00 datReadPos: fm_pos 0x1b2c, locPos 0x1b2c, pos 0x0 2/26/2003 2:23:54 AM: Comparing MacOS X… SCSI SCSI-A:3: 2:23:55 AM Command <00 00 00 00 00 00> SCSI SCSI-A:3: (<00> passed 4 more times) SCSI SCSI-A:3: 2:23:56 AM Command <01 00 00 00 00 00> datUStart: fm_pos 0x0, pos 0x0 SCSI SCSI-A:3: 2:24:17 AM Command <11 00 00 00 01 00> SCSI SCSI-A:3: 2:24:17 AM Read <08 01 00 00 01 00> [131,072 bytes] [131,072 bytes] > 53 67 6d 74 00 00 00 9a 52 78 76 72 00 02 00 00 00 01 ba 81 d0 b6 00 00 00 17 00 00 00 00 ff 70 File “SystemEntropyCache”: different modification date/time (set: 2/26/2003 1:18:09 AM, vol: 2/26/2003 2:18:09 AM), path: “MacOS X/private/var/db/SystemEntropyCache”. File “ntp.drift”: different creation date/time (set: 2/26/2003 1:18:12 AM, vol: 2/26/2003 2:18:12 AM), path: “MacOS X/private/var/run/ntp.drift”. File “cifsd.log”: different data size (set: 212,396, vol: 212,730), path: “MacOS X/System/Library/Filesystems/DAVE/cifsd.log”. SCSI SCSI-A:3: (<08> passed 1599 more times) Sense > f0 00 80 00 00 00 01 18 00 00 00 00 00 01 00 00 00 00 SCSI SCSI-A:3: 2:26:11 AM Read <34 00 00 00 00 00 00 00 00 00> [20 bytes] [20 bytes] > 00 00 00 00 00 00 06 42 00 00 00 00 00 00 00 00 00 00 00 00 datReadPos: fm_pos 0x0, locPos 0x642, pos 0xc800000 datUStart: fm_pos 0x642, pos 0x0 SCSI SCSI-A:3: 2:26:11 AM Read <08 01 00 00 01 00> [131,072 bytes] [131,072 bytes] > 53 67 6d 74 00 00 00 9a 52 78 76 72 00 02 00 00 00 01 ba 81 d0 b6 00 00 00 18 00 00 06 42 ff 6a SCSI SCSI-A:3: (<08> passed 1599 more times) Sense > f0 00 80 00 00 00 01 18 00 00 00 00 00 01 00 00 00 00 SCSI SCSI-A:3: 2:28:07 AM Read <34 00 00 00 00 00 00 00 00 00> [20 bytes] [20 bytes] > 00 00 00 00 00 00 0c 83 00 00 00 00 00 00 00 00 00 00 00 00 datReadPos: fm_pos 0x642, locPos 0xc83, pos 0xc800000 datUStart: fm_pos 0xc83, pos 0x0 SCSI SCSI-A:3: 2:28:07 AM Read <08 01 00 00 01 00> [131,072 bytes] [131,072 bytes] > 53 67 6d 74 00 00 00 9a 52 78 76 72 00 02 00 00 00 01 ba 81 d0 b6 00 00 00 19 00 00 0c 83 ff 64 SCSI SCSI-A:3: (<08> passed 1599 more times) Sense > f0 00 80 00 00 00 01 18 00 00 00 00 00 01 00 00 00 00 SCSI SCSI-A:3: 2:28:58 AM Read <34 00 00 00 00 00 00 00 00 00> [20 bytes] [20 bytes] > 00 00 00 00 00 00 12 c4 00 00 00 00 00 00 00 00 00 00 00 00 datReadPos: fm_pos 0xc83, locPos 0x12c4, pos 0xc800000 datUStart: fm_pos 0x12c4, pos 0x0 SCSI SCSI-A:3: 2:28:59 AM Read <08 01 00 00 01 00> [131,072 bytes] [131,072 bytes] > 53 67 6d 74 00 00 00 9a 52 78 76 72 00 02 00 00 00 01 ba 81 d0 b6 00 00 00 1a 00 00 12 c4 ff 5d SCSI SCSI-A:3: (<08> passed 1599 more times) Sense > f0 00 80 00 00 00 01 18 00 00 00 00 00 01 00 00 00 00 SCSI SCSI-A:3: 2:30:12 AM Read <34 00 00 00 00 00 00 00 00 00> [20 bytes] [20 bytes] > 00 00 00 00 00 00 19 05 00 00 00 00 00 00 00 00 00 00 00 00 datReadPos: fm_pos 0x12c4, locPos 0x1905, pos 0xc800000 datUStart: fm_pos 0x1905, pos 0x0 SCSI SCSI-A:3: 2:30:12 AM Read <08 01 00 00 01 00> [131,072 bytes] [131,072 bytes] > 53 67 6d 74 00 00 00 9a 52 78 76 72 00 02 00 00 00 01 ba 81 d0 b6 00 00 00 1b 00 00 19 05 ff 57 2/26/2003 2:30:44 AM: 3 execution errors. Completed: 38403 files, 806.2 MB Performance: 111.9 MB/minute (101.8 copy, 124.3 compare) Duration: 00:28:14 (00:13:50 idle/loading/preparing) - 2/26/2003 2:30:47 AM: Copying FredG4… SCSI SCSI-A:3: (<08> passed 191 more times) SCSI SCSI-A:3: 2:35:33 AM Command <00 00 00 00 00 00> SCSI SCSI-A:3: (<00> passed 4 more times) SCSI SCSI-A:3: 2:35:34 AM Command <2b 00 00 00 00 1b 2c 00 00 00> SCSI SCSI-A:3: 2:35:49 AM Command <11 00 00 00 01 00> Sense > f0 00 08 00 00 00 01 18 00 00 00 00 00 05 00 00 00 00 SCSI SCSI-A:3: 2:35:49 AM Read <34 00 00 00 00 00 00 00 00 00> [20 bytes] [20 bytes] > 00 00 00 00 00 00 1b 2c 00 00 00 00 00 00 00 00 00 00 00 00 datReadPos: fm_pos 0x1905, locPos 0x1b2c, pos 0x0 SCSI SCSI-A:3: 2:35:52 AM Write <0a 01 00 00 01 00> [131,072 bytes] [131,072 bytes] > 53 67 6d 74 00 00 00 9a 52 78 76 72 00 02 00 00 00 02 ba 81 d7 57 00 00 00 1c 00 00 1b 2c ff 55 SCSI SCSI-A:3: (<0a> passed 1599 more times) SCSI SCSI-A:3: 2:36:41 AM Command <10 00 00 00 01 80> SCSI SCSI-A:3: 2:36:42 AM Command <10 00 00 00 00 80> SCSI SCSI-A:3: 2:36:42 AM Read <34 00 00 00 00 00 00 00 00 00> [20 bytes] [20 bytes] > 00 00 00 00 00 00 21 6d 00 00 00 00 00 00 00 00 00 00 00 00 datReadPos: fm_pos 0x1905, locPos 0x216d, pos 0x0 SCSI SCSI-A:3: 2:36:42 AM Command <00 00 00 00 00 00> SCSI SCSI-A:3: (<00> passed 4 more times) SCSI SCSI-A:3: 2:36:44 AM Write <0a 01 00 00 01 00> [131,072 bytes] [131,072 bytes] > 53 67 6d 74 00 00 00 9a 52 78 76 72 00 02 00 00 00 02 ba 81 d7 57 00 00 00 1d 00 00 21 6d ff 4f SCSI SCSI-A:3: (<0a> passed 1599 more times) SCSI SCSI-A:3: 2:37:45 AM Command <10 00 00 00 01 80> SCSI SCSI-A:3: 2:37:45 AM Command <10 00 00 00 00 80> SCSI SCSI-A:3: 2:37:45 AM Read <34 00 00 00 00 00 00 00 00 00> [20 bytes] [20 bytes] > 00 00 00 00 00 00 27 ae 00 00 00 00 00 00 00 00 00 00 00 00 datReadPos: fm_pos 0x216d, locPos 0x27ae, pos 0x0 SCSI SCSI-A:3: 2:37:46 AM Command <00 00 00 00 00 00> SCSI SCSI-A:3: (<00> passed 4 more times) SCSI SCSI-A:3: 2:37:48 AM Write <0a 01 00 00 01 00> [131,072 bytes] [131,072 bytes] > 53 67 6d 74 00 00 00 9a 52 78 76 72 00 02 00 00 00 02 ba 81 d7 57 00 00 00 1e 00 00 27 ae ff 48 SCSI SCSI-A:3: (<0a> passed 1599 more times) SCSI SCSI-A:3: 2:38:33 AM Command <10 00 00 00 01 80> SCSI SCSI-A:3: 2:38:34 AM Command <10 00 00 00 00 80> SCSI SCSI-A:3: 2:38:34 AM Read <34 00 00 00 00 00 00 00 00 00> [20 bytes] [20 bytes] > 00 00 00 00 00 00 2d ef 00 00 00 00 00 00 00 00 00 00 00 00 datReadPos: fm_pos 0x27ae, locPos 0x2def, pos 0x0 SCSI SCSI-A:3: 2:38:34 AM Command <00 00 00 00 00 00> SCSI SCSI-A:3: (<00> passed 4 more times) SCSI SCSI-A:3: 2:38:36 AM Write <0a 01 00 00 01 00> [131,072 bytes] [131,072 bytes] > 53 67 6d 74 00 00 00 9a 52 78 76 72 00 02 00 00 00 02 ba 81 d7 57 00 00 00 1f 00 00 2d ef ff 42 SCSI SCSI-A:3: (<0a> passed 1599 more times) SCSI SCSI-A:3: 2:39:33 AM Command <10 00 00 00 01 80> SCSI SCSI-A:3: 2:39:34 AM Command <10 00 00 00 00 80> SCSI SCSI-A:3: 2:39:34 AM Read <34 00 00 00 00 00 00 00 00 00> [20 bytes] [20 bytes] > 00 00 00 00 00 00 34 30 00 00 00 00 00 00 00 00 00 00 00 00 datReadPos: fm_pos 0x2def, locPos 0x3430, pos 0x0 SCSI SCSI-A:3: 2:39:34 AM Command <00 00 00 00 00 00> SCSI SCSI-A:3: (<00> passed 4 more times) SCSI SCSI-A:3: 2:39:36 AM Write <0a 01 00 00 01 00> [131,072 bytes] [131,072 bytes] > 53 67 6d 74 00 00 00 9a 52 78 76 72 00 02 00 00 00 02 ba 81 d7 57 00 00 00 20 00 00 34 30 ff 3c SCSI SCSI-A:3: (<0a> passed 1599 more times) SCSI SCSI-A:3: 2:40:39 AM Command <10 00 00 00 01 80> SCSI SCSI-A:3: 2:40:40 AM Command <10 00 00 00 00 80> SCSI SCSI-A:3: 2:40:40 AM Read <34 00 00 00 00 00 00 00 00 00> [20 bytes] [20 bytes] > 00 00 00 00 00 00 3a 71 00 00 00 00 00 00 00 00 00 00 00 00 datReadPos: fm_pos 0x3430, locPos 0x3a71, pos 0x0 SCSI SCSI-A:3: 2:40:41 AM Command <00 00 00 00 00 00> SCSI SCSI-A:3: (<00> passed 4 more times) SCSI SCSI-A:3: 2:40:42 AM Write <0a 01 00 00 01 00> [131,072 bytes] [131,072 bytes] > 53 67 6d 74 00 00 00 9a 52 78 76 72 00 02 00 00 00 02 ba 81 d7 57 00 00 00 21 00 00 3a 71 ff 36 DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 SCSI SCSI-A:3: (<0a> passed 899 more times) Result -2, status 255 SCSI SCSI-A:3: 2:41:33 AM Write <0a 01 00 00 01 00> [131,072 bytes] DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 Result -2, status 255 DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 SCSI SCSI-A:3: (<0a> failed 4 more times) SCSI SCSI-A:3: 2:43:11 AM Command <10 00 00 00 01 80> DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 Result -2, status 255 DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 Trouble writing: “2-FredG4-VXA [017]” (4281509888), error 102 (trouble communicating). SCSI SCSI-A:3: (<10> failed 5 more times) SCSI SCSI-A:3: 2:45:08 AM Command <1b 00 00 00 00 00> DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 Result -2, status 255 DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 Please help! Thanks, -Mike Link to comment Share on other sites More sharing options...
AmyJ Posted February 26, 2003 Report Share Posted February 26, 2003 From the Knowledgebase: The devices and SCSI cards listed in our OS X supported list have undergone preliminary testing by Dantz for use with OSX. This list is provided as a service to our customers and does not guarantee compatibility or performance in all systems. If you are experiencing a SCSI communication error it could be caused by one or more of the following: 1) A dirty tape heads or bad media. Clean the drive using a cleaning cartridge. Try another piece of media. If other media works then dispose of the bad media and continue to backup with the new media. 2) Another device on your SCSI bus is interfering with the device’s communication. Make sure your SCSI ID numbers are set correctly. Turn off your computer and the devices. Disconnect all SCSI devices except for the backup device making it the only SCSI device on the chain. Note: If you are using Mac OS X, you should not use a wide device with a narrow card. Nor should you use a narrow device with a wide card. 3) You have a bad cable. Replace the SCSI cable that connects the device to the computer after removing other devices and cables from the SCSI chain. 4) You are missing a terminator or have a bad terminator. The last device and ONLY the last device in your SCSI chain needs to be terminated. Try replacing the terminator if you already have one on the chain. 5) Your SCSI card and backup device combination may not be fully functional under OS X. "Bad backup set header" error messages are a common symptom of this problem. Check with the SCSI card vendor for firmware and driver updates. If those updates do not help, try a different SCSI card. 6) The computer may be having a problem. Install Retrospect on another computer and try the device on that other machine. 7) Boot into OS 9 and check the OS 9 System Profiler to confirm that the drive is visible. Apple Menu> Apple System Profiler If it is, open Retrospect and attempt to back up. 8) If the backup fails again, the drive may be defective. If you have implemented all of the preceding steps and get failures on multiple tapes after changing cables terminators and computers then the drive (being the only factor that has not changed) is the culprit—contact the drive vendor for additional suggestions. If your device does not appear or function correctly in Mac OS X: 1) Confirm that your backup device and SCSI card are supported by both Mac OS X and by Retrospect. 2) Another device on your SCSI bus is interfering with the device’s communication. Make sure your SCSI ID numbers are set correctly. Turn off your computer and the devices. Disconnect all SCSI devices except for the backup device making it the only SCSI device on the chain. Note: If you are using Mac OS X, you should not use a wide device with a narrow card. Nor should you use a narrow device with a wide card. 3) Check the Apple System Profiler to see if the drive is visible. Applications> Utilities> Apple System Profiler. If your device is not visible in the Apple System Profiler, Retrospect will not be able to use the device for backup. 4) If the device is still not visible, boot into OS 9 and check the OS 9 System Profiler. Apple Menu> Apple System Profiler. 5) If the drive is visible in the Mac OS 9 Apple System Profiler, contact the drive vendor for compatibility information. Link to comment Share on other sites More sharing options...
shadowspawn Posted February 26, 2003 Report Share Posted February 26, 2003 Quote: I just switched to Mac OS 10.2.4 from Mac OS 9.2.2, using the same install of Retrospect 5.0.238. I have not had a successful backup to my SCSI Ecrix VXA-1 tape drive since doing so. I always get error 102 (trouble communicating). I have never had problems with Mac OS 9. The VXA drive and a JAZ drive are the only things on my SCSI bus. My SCSI card is an Adaptec 2930CU. I am using the same tape drive, Mac OS, and SCSI card, so there is a good chance it will work! The Adaptec card was unreliable early on with Mac OS X (and it was hell), but Adaptec finally got the drivers right. A few things to confirm: a) Are you using the latest Adaptec driver? I am not sure whether you need to install this separately, or whether it is built into Mac OS X. Check in the System Profiler, under Extensions. I have one called "Adaptec290X-2930.kext" at version 1.1.0. Are you using the latest VXA firmware? In Retrospect, got into Devices, and click the Device Status button. I have version 2C8C. c) As Amy covered, try having just the VXA drive connected on SCSI, nothing else. Try a different cable too. Link to comment Share on other sites More sharing options...
webdeck Posted February 27, 2003 Author Report Share Posted February 27, 2003 Quote: I am using the same tape drive, Mac OS, and SCSI card, so there is a good chance it will work! The Adaptec card was unreliable early on with Mac OS X (and it was hell), but Adaptec finally got the drivers right. A few things to confirm: a) Are you using the latest Adaptec driver? I am not sure whether you need to install this separately, or whether it is built into Mac OS X. Check in the System Profiler, under Extensions. I have one called "Adaptec290X-2930.kext" at version 1.1.0. Are you using the latest VXA firmware? In Retrospect, got into Devices, and click the Device Status button. I have version 2C8C. c) As Amy covered, try having just the VXA drive connected on SCSI, nothing else. Try a different cable too. My driver extension and VXA firmware are the same as what you have. What does the profiler show for your Adaptec card? Mine shows: Card Type scsi Card Name ADPT,2930CU Card Modem ADPT,1686806-04 Vendor ID 9004 Device ID 5078 ROM# 4.3 Revision 3 I'll try removing the JAZ drive, but it is doing the smart termination of my SCSI bus, so I'll have to mess with that. Thanks, -Mike Link to comment Share on other sites More sharing options...
webdeck Posted February 28, 2003 Author Report Share Posted February 28, 2003 Quote: If you are experiencing a SCSI communication error it could be caused by one or more of the following: 1) A dirty tape heads or bad media. Clean the drive using a cleaning cartridge. Try another piece of media. If other media works then dispose of the bad media and continue to backup with the new media. This happens with multiple media. The same media works without problems under MacOS 9. Quote: 2) Another device on your SCSI bus is interfering with the device’s communication. Make sure your SCSI ID numbers are set correctly. Turn off your computer and the devices. Disconnect all SCSI devices except for the backup device making it the only SCSI device on the chain. Note: If you are using Mac OS X, you should not use a wide device with a narrow card. Nor should you use a narrow device with a wide card. 3) You have a bad cable. Replace the SCSI cable that connects the device to the computer after removing other devices and cables from the SCSI chain. 4) You are missing a terminator or have a bad terminator. The last device and ONLY the last device in your SCSI chain needs to be terminated. Try replacing the terminator if you already have one on the chain. I have removed all other SCSI devices. The VXA-1 drive is the only device on the SCSI bus. The SCSI card and the VXA-1 drive have 50 pin connectors and are connected by a high quality 50 pin cable. The VXA-1 drive is properly terminated. The same SCSI card, drive, and cable work flawlessly under MacOS 9. Quote: 5) Your SCSI card and backup device combination may not be fully functional under OS X. "Bad backup set header" error messages are a common symptom of this problem. Check with the SCSI card vendor for firmware and driver updates. If those updates do not help, try a different SCSI card. I cannot find a reference on your site or Adaptec's that lists the latest firmware for the SCSI card. The VXA-1 drive has the latest firmware. The Adaptec card is using the latest driver for Mac OS X 10.2.4. Quote: 6) The computer may be having a problem. Install Retrospect on another computer and try the device on that other machine. 7) Boot into OS 9 and check the OS 9 System Profiler to confirm that the drive is visible. Apple Menu> Apple System Profiler If it is, open Retrospect and attempt to back up. 8) If the backup fails again, the drive may be defective. If you have implemented all of the preceding steps and get failures on multiple tapes after changing cables terminators and computers then the drive (being the only factor that has not changed) is the culprit—contact the drive vendor for additional suggestions. The exact same hardware works flawlessly under MacOS 9 with the same version and configuration of Retrospect. Quote: If your device does not appear or function correctly in Mac OS X: 1) Confirm that your backup device and SCSI card are supported by both Mac OS X and by Retrospect. According to your web site, they are supported. Quote: 2) Another device on your SCSI bus is interfering with the device’s communication. Make sure your SCSI ID numbers are set correctly. Turn off your computer and the devices. Disconnect all SCSI devices except for the backup device making it the only SCSI device on the chain. Note: If you are using Mac OS X, you should not use a wide device with a narrow card. Nor should you use a narrow device with a wide card. See above. Quote: 3) Check the Apple System Profiler to see if the drive is visible. Applications> Utilities> Apple System Profiler. If your device is not visible in the Apple System Profiler, Retrospect will not be able to use the device for backup. It shows up as IOSCSIParallelDevice, SCSI Product Name VXA-1, SCSI Target 1, SCSI Product Revision 2C8C, SCSI Lun 0, Product Identification VXA-1, SCSI Device Type 1, Vendor Identification ECRIX. Quote: 4) If the device is still not visible, boot into OS 9 and check the OS 9 System Profiler. Apple Menu> Apple System Profiler. 5) If the drive is visible in the Mac OS 9 Apple System Profiler, contact the drive vendor for compatibility information. The drive is visible under both Mac OS 9 and Mac OS X. It works flawlessly under Mac OS 9, but consistently gets error 102 under Mac OS X. Link to comment Share on other sites More sharing options...
AmyJ Posted February 28, 2003 Report Share Posted February 28, 2003 Quote: It works flawlessly under Mac OS 9, but consistently gets error 102 under Mac OS X. Mac OS X requires a new method of interaction between the SCSI adapter and the operating system. Because of this, not all SCSI adapters that functioned properly on Mac OS 9 will function properly on OS X. DantzLab has tested many of the OS X supported SCSI adapters for compatibility. The cards listed have undergone preliminary testing by Dantz for use with Mac OS X. This list is provided as a service to our customers and does not guarantee compatibility or performance in all configurations. Try a different OS X machine and a different SCSI card. Link to comment Share on other sites More sharing options...
webdeck Posted March 1, 2003 Author Report Share Posted March 1, 2003 Quote: Mac OS X requires a new method of interaction between the SCSI adapter and the operating system. Because of this, not all SCSI adapters that functioned properly on Mac OS 9 will function properly on OS X. DantzLab has tested many of the OS X supported SCSI adapters for compatibility. The cards listed have undergone preliminary testing by Dantz for use with Mac OS X. This list is provided as a service to our customers and does not guarantee compatibility or performance in all configurations. Try a different OS X machine and a different SCSI card. I do not have a different OS X machine or a different SCSI card to try, and I can not afford to go out and purchase them. Can anyone out there provide advice to get this to work? I've upgraded the VXA-1 firmware to version 2D9D. I cannot find newer drivers or firmware for the Adaptec SCSI card. I've toggled every secret SCSI preference in Retrospect, in every combination. I've tried every setting in the PowerDomain Control application (which requires booting back into MacOS 9 to use.) Nothing helps. I've watched the backup attempt. Everything goes normally for a while, and then I'll see the error: DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 After that, there is no more tape drive activity. Retrospect will continue to error out, every couple of minutes, until it finally just hangs completely. SCSI SCSI-A:1: (<0a> passed 1339 more times) Result -2, status 255 SCSI SCSI-A:1: 12:03:26 PM Write <0a 01 00 00 01 00> [131,072 bytes] DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 Result -2, status 255 DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 DeviceAccess: stucFinished: transaction failed, error 0xffffdcd8 Link to comment Share on other sites More sharing options...
shadowspawn Posted March 2, 2003 Report Share Posted March 2, 2003 Quote: What does the profiler show for your Adaptec card? Ironically mine has an older ROM. Here are the details for my (working) card: Card Type scsi Card Name ADPT,2930CU Card Modem ADPT,1686806-04 Vendor ID 9004 Device ID 5078 ROM# 4.0 Revision 3 Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.