denniskane Posted July 29, 2003 Report Share Posted July 29, 2003 Well, first I got internal consistency check failed: memory.c-747 on one catalog. Tried to repair it and could not get around this error. Went back to another catalog and it worked for awhile and now I'm getting consistency check failed: arc.c-1590 and I can't repair this catalog either. Retrospect is hosed. I tried checking my system with fsck and repairing privileges -- no luck. This might have happened about when I updated 10.2.6 for the security update. Oh, and to top it off my Dantz maintenance agreement just expired, so I can't upgrade to 5.1. Can't tell you how many years (feels like over 10) that I ran Retrospect problem free, but now things are quite frustrating. Looked through the knowledge base and the forum and it looks like consistency check fails of several flavors are killing users right and left with no fix in sight. Any help out there would be greatly appreciated. Dennis Kane Link to comment Share on other sites More sharing options...
natew Posted July 30, 2003 Report Share Posted July 30, 2003 Hi Consistency check errors are generally caused by memory managment problems or corrupt configs. How about a reboot? New Retrospect configs? Can you also give some info on your hardware and software setup? Thanks Nate Link to comment Share on other sites More sharing options...
denniskane Posted July 30, 2003 Author Report Share Posted July 30, 2003 Dual 1GHz G4 with 512 MB RAM Sony DDS3 autoloader and VXA 15xAutopak, both yield consistency check errors SCSI cards an ATTO Express SCSI 2 hooked up to the VGA and an Adaptec 2906 hooked up to the Sony. Guess I could hunt for new drivers for the autoloaders, but since they are on different PCI slots, and both involved in problematic behaviors, I figured Retro was the common problem. Moving the config file to the trash as advised as a test in the knowledgebase may be OK, but if that's it, I have a ton of work to do reconfiguring the clients and scripts, right? Link to comment Share on other sites More sharing options...
denniskane Posted July 30, 2003 Author Report Share Posted July 30, 2003 Oh, and Retro 5.0238 with this error log - 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: 7/29/2003 4:25 PM version: 5.0.238 Internal consistency check failed: Assertion check at "arc.c-1590" Stack Crawl... DATA_0000 +4c998 DATA_0000 +effcc DATA_0000 +29430 DATA_0000 +875ec DATA_0000 +2fd84 DATA_0000 +158fb8 DATA_0000 +159324 DATA_0000 +2fd84 DATA_0000 +16991c DATA_0000 +2fd84 DATA_0000 +1599bc DATA_0000 +557b4 DATA_0000 +559b0 DATA_0000 +159d50 DATA_0000 +557b4 DATA_0000 +2fe98 DATA_0000 +55a34 DATA_0000 +159de0 DATA_0000 +2fd84 DATA_0000 +c7cc8 DATA_0000 +2fd84 DATA_0000 +d2fe4 DATA_0000 +557b4 DATA_0000 +559b0 DATA_0000 +557b4 DATA_0000 +559b0 DATA_0000 +d30a8 DATA_0000 +557b4 DATA_0000 +559b0 DATA_0000 +29670 DATA_0000 +557b4 DATA_0000 +559b0 DATA_0000 +29768 DATA_0000 +298b4 Link to comment Share on other sites More sharing options...
natew Posted July 31, 2003 Report Share Posted July 31, 2003 Hi Yeah it is a lot of work but it is worth a try. If it doesn't fix the problem you can always move the configs back. Seriously- reboots help a lot too if you can manage taking the server down. Nate Link to comment Share on other sites More sharing options...
denniskane Posted August 1, 2003 Author Report Share Posted August 1, 2003 Thanks for the replies, Nate. Moving the config didn't help. Same symptoms. Link to comment Share on other sites More sharing options...
denniskane Posted August 2, 2003 Author Report Share Posted August 2, 2003 I just noticed something interesting. When I just did a Configure-Backup Sets-Members of the backup set that I'm getting "consistency check failed: arc.c-1590" some of the tapes are set to Missing (I did not do this) and the dates are 1/1/1904 with zero K used. I cannot set the tapes to Found. For the other data set where I get "consistency check failed: memory.c-747" I cannot inspect members. When I select that backup set to look at the members, I get the memory.c-747 and Retrospect quits. I would conclude that there is a bug that is corrupting my catalogs now, maybe coinciding with a recent system software update. I may try rebuilding my catalog from tapes, but that will take a while. Link to comment Share on other sites More sharing options...
denniskane Posted August 2, 2003 Author Report Share Posted August 2, 2003 Of course, I was a bad boy about backing up my catalog so I have to rebuild it from scratch. Based on how it's going so far, it should take me about 114 hours to rebuild the catalog from my 86 DDS3 tapes. Lesson is - make sure that you backup your catalog. Hate to be a pessimist, but I expect that I'll rebuild the catalog over the next week and the problem will recur. Link to comment Share on other sites More sharing options...
CallMeDave Posted August 3, 2003 Report Share Posted August 3, 2003 Quote: Hate to be a pessimist, but I expect that I'll rebuild the catalog over the next week and the problem will recur. Always listen to your gut feelings... I'd suggest there's something in your hardware configuration that's causing the corruptions. Since the SCSI subsystems are integral to your backup, you probably would want to start with somewhere else. I'd suggest memory. Retrospect is _very_ memory intensive. If the catalog data that gets written to memory becomes scrambled, the catalog will be hosed and crash each time you access it (as is happening). Good entry on today's (8/3/03) MacFixIt (not sure if the link will be permenant without having an account): http://www.macfixit.com/article.php?story=2003080107264938 Even if the 512M is the RAM that shipped with your G4, I'd suggest swapping it out with another known good stick. Worth the $80 or so if it ends up helping. If not, the RAM won't go to waste! Dave Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.