rarnold Posted May 30, 2002 Report Share Posted May 30, 2002 I have an PowerMac 8500 running Mac OS 9.0.4 and ASIP 6.3.x and Retrospect 5.0.205 Other than occasional freezes when starting up, Retrospect has run fine. That is until I installed the "Retrospect 5.0 Driver Update" that was just released. Now when backing up a remote X client to an archive on the internal hard disk, Retrospect barfs: $[31]Retrospect$[32] version 5.0.205 launched at 05/30/2002 14:44 + Retrospect Driver Update, version 2.6.106 + 05/30/2002 14:45: Backup Server started + Normal backup using $[24]Back up to server$[25] at 05/30/2002 14:52 To backup set $[*!s301,,14,+3]Power Mail files… - 05/30/2002 14:52:55: Copying $[*!s307,,14,+3]PowerMail on $[35]K2$[36]… 05/30/2002 14:52:55: Connected to $[*!s13805,,14,+3]K2 Internal consistency check failed: Assertion check at "elem.c-812" 05/30/2002 14:54:37: Execution incomplete. $[3105615175] Completed: 5 files, 90.6 MB, with 56% compression Performance: 55.4 MB/minute Duration: 00:01:42 (00:00:04 idle/loading/preparing) - 05/30/2002 14:55: Backup Server stopped, general error Quit at 05/30/2002 14:55 Upon removing the driver update, Retrospect continues without incident. Below is the error log generated by Retrospect (note the phone numbers and the suggestion to call, which results in a demand for a credit card...) Rand ------ Retrospect detected a failure: This report documents an unusual condition detected by Retrospect’s internal integrity checking. This might be caused by a software bug, but can also be the result of an incompatibility, hardware malfunction, damaged system software, or other problems. Details on possible causes can be found on Dantz’s website: http://www.dantz.com/support For further assistance, call us at (888) 777-5664 or (925) 253-3050. Please be prepared to provide us a brief description of the steps that led to this failure along with the assert log. --- Retrospect Problem Report date: 05/30/2002 14:55 version: 5.0.205 Internal consistency check failed: Assertion check at "elem.c-812" Stack Crawl... DATA_0000 +4cc44 DATA_0000 +f0224 DATA_0000 +2962c DATA_0000 +1ad2c DATA_0000 +137c0 DATA_0000 +2fdb0 Ret_Addr 00b085800 DATA_0000 +55c74 DATA_0000 +2ff94 DATA_0000 +55f14 Ret_Addr 00b085924 DATA_0000 +2fe60 DATA_0000 +55d34 DATA_0000 +2ff94 DATA_0000 +55f14 Ret_Addr 00b085b78 DATA_0000 +2fe60 DATA_0000 +cbf90 DATA_0000 +2fe60 DATA_0000 +d3254 DATA_0000 +55c74 DATA_0000 +55e98 DATA_0000 +d333c DATA_0000 +55c74 DATA_0000 +55e98 DATA_0000 +d0d78 DATA_0000 +2fe60 DATA_0000 +d3254 DATA_0000 +55c74 DATA_0000 +55e98 DATA_0000 +55c74 DATA_0000 +55e98 DATA_0000 +d3318 DATA_0000 +55c74 DATA_0000 +55e98 DATA_0000 +29868 DATA_0000 +55c74 DATA_0000 +55e98 DATA_0000 +29968 DATA_0000 +29ab4 --- Link to comment Share on other sites More sharing options...
AmyJ Posted June 3, 2002 Report Share Posted June 3, 2002 This is an issue that we are aware of and are fixing with the next Retrospect Driver Update, which is due out soon. The issue only occurs when writing to a file backup set. The current RDU for Retrospect 5.0 for the Mac only addresses issues with certain Ecrix tape drives. If you are not using an Ecrix tape drive, you should remove the driver update file. Link to comment Share on other sites More sharing options...
rarnold Posted June 3, 2002 Author Report Share Posted June 3, 2002 I do have an Ecrix drive, which is why I got the driver. And I did remove it, which is why I can still back up files... I'm glad that Dantz is aware of the problem and working on a fix. Rand Link to comment Share on other sites More sharing options...
AmyJ Posted June 4, 2002 Report Share Posted June 4, 2002 We released a driver this morning that should fix these assert errors. This RDU only addresses assert errors with Ecrix drives. ftp://ftp.dantz.com/pub/updates/rdu26a.sit Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.