ianouth1 Posted January 26, 2004 Report Share Posted January 26, 2004 Retrospect 6.0 Workgroup. When I attempt to check devices Retrospect scans and then attempts to read the contents of the exabyte 8505 - but quits with this error: Esmq Internal consistency check failed: Assertion check at "dat.c-1582" Quit at 1/26/2004 6:22 PM Does anyone know how to fix this? Link to comment Share on other sites More sharing options...
Mayoff Posted January 27, 2004 Report Share Posted January 27, 2004 Hi, We will be contacting you via email tomorrow to get you a version of Retrospect with enough logging to capture the assert error for our engineers to review ASAP. Link to comment Share on other sites More sharing options...
mkelner Posted January 28, 2004 Report Share Posted January 28, 2004 I am having the exact same problem with Retrospect, same problem, same data. I downloaded the program about 5 hours ago and have not left my seat (well maybe once) trying to solve this problem. What to do? Mkelner@adelphia.net Link to comment Share on other sites More sharing options...
ianouth1 Posted January 28, 2004 Author Report Share Posted January 28, 2004 Haven't received any email as far as I can tell.... Has one been sent? Link to comment Share on other sites More sharing options...
Mayoff Posted January 28, 2004 Report Share Posted January 28, 2004 An email just went out from Amy. Link to comment Share on other sites More sharing options...
Mayoff Posted January 28, 2004 Report Share Posted January 28, 2004 We now the cause of this assert and hope to have an RDU with a fix within the next day or so. This only happens when you have a huge amount of RAM Link to comment Share on other sites More sharing options...
lstone19 Posted January 29, 2004 Report Share Posted January 29, 2004 I know you said you've figured out what's causing but just in case this is something different, tonight doing a backup to CD-RW in the internal Superdrive (1.25GHz iMac, 768 MB RAM), it errorred during the comparison pass. I then did a Verify on the Backup Set and received: Trouble in Retrospect Internal consistency check failed: Asserion check at "elem.c-811" Link to comment Share on other sites More sharing options...
Mayoff Posted January 29, 2004 Report Share Posted January 29, 2004 That would be a different problem. You should probably contact support directly so we can help troubleshoot and debug the cause. Link to comment Share on other sites More sharing options...
davejud Posted February 3, 2004 Report Share Posted February 3, 2004 On my new installation i was able to run a full backup, but on quitting Retrospect 6, I get Trouble in Retrospect: Internal consistency check failed: Assertion check at "memory.c-424" I tried a reinstall and same problem? Link to comment Share on other sites More sharing options...
Mayoff Posted February 3, 2004 Report Share Posted February 3, 2004 how much RAM do you have? Link to comment Share on other sites More sharing options...
davejud Posted February 4, 2004 Report Share Posted February 4, 2004 I have 1 Gig RAM on a Powerbook G4. Thanks, Link to comment Share on other sites More sharing options...
zegor Posted February 5, 2004 Report Share Posted February 5, 2004 It has been a few days since we heard "hope to have an RDU with a fix within the next day or so" - what is the current timeline for getting a fix out? Cheers, Z. Link to comment Share on other sites More sharing options...
Mayoff Posted February 5, 2004 Report Share Posted February 5, 2004 As noted in this forum topic yesterday and on several Mac news sites (and the RDU notify list) this RDU has already been released at www.dantz.com/updates Link to comment Share on other sites More sharing options...
davejud Posted March 5, 2004 Report Share Posted March 5, 2004 Still getting this everytime Retrospect 6.0 is quit. Updated Drivers, no improvement. Any thoughts on why? Link to comment Share on other sites More sharing options...
CallMeDave Posted March 5, 2004 Report Share Posted March 5, 2004 Quote: Still getting this everytime Retrospect 6.0 is quit. Updated Drivers, no improvement. Any thoughts on why? I kinda wonder why you didn't provide a single bit of specific information about your hardware/software configuration. Most installs don't assert on quit, so knowing what's different about your setup is what it will take to figure out what's happening. Dave Link to comment Share on other sites More sharing options...
davejud Posted March 6, 2004 Report Share Posted March 6, 2004 Sorry, I thought I had listed system setup in a previous post. G4 PowerBook 1.33Ghz, OS X 10.3.2, 1Gig RAM, Retrospect 6.0.178, Driver Update version 5.1.103. Even if I just open Retrospect and quit, without running a backup I get the Assertion check at "memory.c-424". Link to comment Share on other sites More sharing options...
raporter Posted March 13, 2004 Report Share Posted March 13, 2004 I am having the same error message "memory.c-424" but it happens on my machine just after scanning my volume and matching. No such error message when I quit. I have a G3 (upgraded to 500 MHz G4 processor), 1 GB memory, 10.3.2, Retrospect 6.0.178, rdu 5.2.101. I am trying to backup to a file on an external drive. Before upgrading to 6.0, I was successfully backing up to a file with 5.0. Of course, I have since created a new backup file as recommended for 6.0. It appears to have successfully completed the initial backup, although it was unattended, with 14 execution errors. No backups have been successful since the initial one. Could the initial execution errors have something to do with the "memory.c-424"? Link to comment Share on other sites More sharing options...
raporter Posted March 15, 2004 Report Share Posted March 15, 2004 Since I was getting a lot of execution errors related to files, I ran Norton Disc Doctor. Once it fixed several errors in directories and files, Retrospect ran just fine, with no "memory.c-424" errors. However, there were still several execution errors. Link to comment Share on other sites More sharing options...
murphyatgenome Posted March 15, 2004 Report Share Posted March 15, 2004 I also get the error: Internal consistency check failed: Assertion check at "elem.c-811" I am running Retro 6 Workgroup on OS X 10.2.8, 450MHz PPC, 896 MB RAM. Link to comment Share on other sites More sharing options...
RGrouper Posted March 16, 2004 Report Share Posted March 16, 2004 I have a similar issue: G3 400/384, Retro 6.x & 160 GB FW Drives as destnation. The first backup of the week works fine then the second day crashes with the "Assertion ... c-424" message. When this happens I cannot put away my FW drive or mount it with Disk Utility. Link to comment Share on other sites More sharing options...
chrisb14 Posted March 21, 2004 Report Share Posted March 21, 2004 I am getting the error: Assertion check at "elem.c-816" I am running Retro Desktop 6.0.178. Error happens during a media verify. Computer is G4 (MDD) Dual 1.25 PPC, 1.5GB Ram, OS X 10.3.3, Destination drive is a 2X superdrive. Link to comment Share on other sites More sharing options...
rickb Posted March 23, 2004 Report Share Posted March 23, 2004 Ok, maybe I've a different assertion violation at "elem.c-821" (not "elem.c-811"). Seems to occur while accessing a catalog for 200k+ files. Mac OS 10.3.3, 1.2GB ram, G4/500, Retrospect 6.0.178 Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.