ddrazen Posted June 2, 2008 Report Share Posted June 2, 2008 I need to use Retrospect on Leopard to perform manual Duplications on large files that are excluded in Time Machine. I trashed all prefs and started over, and Retrospect still reliably crashes when I try to browse or create a sub-volume of my startup drive. Retrospect acknowledges that it's the startup drive with the little power icon next to the drive's icon. I can browse or create a sub-volume of any other volume, however. It only crashes when I do this with my startup drive. I searched for the issue here but didn't find any results. Any ideas? Thanks. iMac 3.06GHz 4GB RAM Mac OS 10.5.3 Retrospect 6.1.138 Quote Link to comment Share on other sites More sharing options...
Mayoff Posted June 2, 2008 Report Share Posted June 2, 2008 What do you mean "crash"? What specifically happens? Does the console log have a crashlog? Quote Link to comment Share on other sites More sharing options...
ddrazen Posted June 2, 2008 Author Report Share Posted June 2, 2008 Oh, good questions. Sorry for the lack of detail. Retrospect quits unexpectedly with no dialog boxes coming up. It just quits. I'll relay what the console says: Jun 2 14:23:33 iMac ReportCrash[4548]: Formulating crash report for process Retrospect[4539] Jun 2 14:23:33 iMac ReportCrash[4548]: Saved crashreport to /Library/Logs/CrashReporter/Retrospect_2008-06-02-142333_iMac.crash using uid: 0 gid: 0, euid: 0 egid: 0 And the crash report says: Process: Retrospect [4539] Path: /Applications/Retrospect 6.1/Retrospect/Contents/MacOS/AuthenticateUser.app/Contents/MacOS/../../../Retrospect Identifier: Retrospect Version: ??? (???) Code Type: PPC (Translated) Parent Process: launchd [1] Date/Time: 2008-06-02 14:23:33.517 -0400 OS Version: Mac OS X 10.5.3 (9D34) Report Version: 6 Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000342000 Crashed Thread: 0 Thread 0 Crashed: 0 translate 0xb816034d CallPPCFunctionAtAddressInt + 25833 1 translate 0xb816ce24 CallPPCFunctionAtAddressInt + 77760 2 translate 0xb80bdb8b 0xb8000000 + 777099 3 translate 0xb80b7007 0xb8000000 + 749575 4 translate 0xb80d49c0 0xb8000000 + 870848 5 translate 0xb813ce79 spin_lock_wrapper + 1981 Thread 1: 0 ??? 0x800bc4a6 0 + 2148254886 1 ??? 0x800c3c9c 0 + 2148285596 2 translate 0xb818b6ea CallPPCFunctionAtAddressInt + 202886 3 ??? 0x800ed6f5 0 + 2148456181 4 ??? 0x800ed5b2 0 + 2148455858 Thread 2: 0 translate 0xb8152b34 spin_lock_wrapper + 91256 1 translate 0xb8167dce CallPPCFunctionAtAddressInt + 57194 2 translate 0xb80bdb8b 0xb8000000 + 777099 3 translate 0xb80b7007 0xb8000000 + 749575 4 translate 0xb80d49c0 0xb8000000 + 870848 5 translate 0xb813d75f spin_lock_wrapper + 4259 Thread 3: 0 translate 0xb8152c24 spin_lock_wrapper + 91496 1 translate 0xb816c825 CallPPCFunctionAtAddressInt + 76225 2 translate 0xb80bdb8b 0xb8000000 + 777099 3 translate 0xb80b7007 0xb8000000 + 749575 4 translate 0xb80d49c0 0xb8000000 + 870848 5 translate 0xb813d75f spin_lock_wrapper + 4259 Thread 0 crashed with X86 Thread State (32-bit): eax: 0x00000100 ebx: 0xb81601b0 ecx: 0x001b5810 edx: 0xb81d86cc edi: 0x00341fc0 esi: 0x00342000 ebp: 0xb7fff968 esp: 0xb7fff930 ss: 0x0000001f efl: 0x00010206 eip: 0xb816034d cs: 0x00000017 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 cr2: 0x00342000 Binary Images: 0xb8000000 - 0xb81d7fe7 translate ??? (???) /usr/libexec/oah/translate Translated Code Information: Rosetta Version: 21.03 Args: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp /Applications/Retrospect 6.1/Retrospect/Contents/MacOS/AuthenticateUser.app/Contents/MacOS/../../../Retrospect Exception: EXC_BAD_ACCESS (0x0001) Thread 0: (0xb011cd38, 0xb8152c24) 0x969a78c0: /usr/lib/libSystem.B.dylib : __pthread_cond_wait + 1260 0x0126c04c: /System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport : _CarbonOperationThreadFunc + 136 0x969f5e8c: /usr/lib/libSystem.B.dylib : __pthread_body + 40 0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0 PPC Thread State srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000 cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x969a7a04 ctr: 0x9696f73c r00: 0x0000014e r01: 0xf0101a50 r02: 0xf0101a90 r03: 0x00005f03 r04: 0x00006003 r05: 0x00000000 r06: 0x00000000 r07: 0x00000000 r08: 0x00000000 r09: 0x00000001 r10: 0xfffffff1 r11: 0xa0c54898 r12: 0x9696f73c r13: 0xf0101b28 r14: 0xf0101b24 r15: 0xf0101b20 r16: 0xf0101b1c r17: 0xf0101b18 r18: 0xf0101ce8 r19: 0x00000000 r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000 r24: 0x00000000 r25: 0x00000000 r26: 0x00000000 r27: 0xa0c573e8 r28: 0x001951e0 r29: 0x0086aa00 r30: 0x00195188 r31: 0x969a73e8 Thread 1: Crashed (0xb7fff930, 0xb816034d) 0x96a4b03c: /usr/lib/libSystem.B.dylib : _statx1 + 52 0x96a4b25c: /usr/lib/libSystem.B.dylib : _statx_np$INODE64 + 64 0x969f96d4: /usr/lib/libSystem.B.dylib : _acl_get_file1 + 100 0x853c502c: No symbol 0x853c5350: No symbol 0x85367708: No symbol 0x85368254: No symbol 0x852c51d0: No symbol 0x850fdd14: No symbol 0x852c114c: No symbol 0x851238a4: No symbol 0x85123aa0: No symbol 0x852c1764: No symbol 0x850fdd14: No symbol 0x851680b4: No symbol 0x850fdd14: No symbol 0x8522390c: No symbol 0x850cf300: No symbol 0x850fdd14: No symbol 0x850dc67c: No symbol 0x850dc6c0: No symbol 0x850fdd14: No symbol 0x85100804: No symbol 0x850fdd14: No symbol 0x85150a0c: No symbol 0x850fdd14: No symbol 0x85151968: No symbol 0x850ead5c: No symbol 0x851238a4: No symbol 0x85123aa0: No symbol 0x850eb248: No symbol 0x850f65f4: No symbol 0x851238a4: No symbol 0x85123aa0: No symbol 0x850f6750: No symbol 0x851238a4: No symbol 0x85123aa0: No symbol 0x850f6848: No symbol 0x850f69b4: No symbol 0x853c5f48: No symbol PPC Thread State srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000 cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x96a4b070 ctr: 0x96a4aff0 r00: 0x00000155 r01: 0xbfffc960 r02: 0xa0c554ec r03: 0xbfffcc88 r04: 0xbfffca5c r05: 0x001b5810 r06: 0xbfffc99c r07: 0x001fd730 r08: 0x00000002 r09: 0x00000004 r10: 0xf0000003 r11: 0xa0c53da0 r12: 0x96a4aff0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000 r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0xffffffff r20: 0xbffff650 r21: 0xbffff4a8 r22: 0xffffffff r23: 0x00000001 r24: 0x0017f590 r25: 0xbfffc99c r26: 0x0000000c r27: 0xbfffca38 r28: 0xbfffca5c r29: 0x96a4aff0 r30: 0x000001ac r31: 0x96a4b22c Thread 2: (0xb009ad68, 0xb8152b34) 0x0126ae34: /System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport : _BSD_watchevent + 44 0x0126ffb8: /System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport : _CarbonSelectThreadFunc + 204 0x969f5e8c: /usr/lib/libSystem.B.dylib : __pthread_body + 40 0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0 PPC Thread State srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000 cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x0126aea0 ctr: 0x969ba46c r00: 0x00000000 r01: 0xf0080d60 r02: 0x01288010 r03: 0x000000e8 r04: 0xf0080e34 r05: 0x00000000 r06: 0x00000000 r07: 0x01000000 r08: 0x00000000 r09: 0x01000000 r10: 0x00000000 r11: 0x0128842c r12: 0x969ba46c r13: 0x01288010 r14: 0x00000000 r15: 0x01288010 r16: 0x01288008 r17: 0xf0080e18 r18: 0x0128fefc r19: 0xf0080e0c r20: 0xf0080dfc r21: 0xf0080e08 r22: 0xf0080e34 r23: 0x00000000 r24: 0x0128fefc r25: 0x01288010 r26: 0x00000000 r27: 0xf0080e04 r28: 0xf0080e34 r29: 0x00000000 r30: 0x01288010 r31: 0x0126fefc Quote Link to comment Share on other sites More sharing options...
ddrazen Posted June 3, 2008 Author Report Share Posted June 3, 2008 hi, any ideas on this issue? if not i guess i'll have to contact technical support. Quote Link to comment Share on other sites More sharing options...
byrd62au Posted June 21, 2008 Report Share Posted June 21, 2008 (edited) Has there been any progress on this problem? I am experiencing an identical issue. Retro Workgroup 6.1 latest driver update. Leopard Server 10.5.3 (was 10.5 no difference). Mac Pro Apple software RAID on startup drive. TIme Machine turned on. VXA Tape Drive - Firewire 800 connection. Problem is identical to above. Edited June 21, 2008 by Guest Quote Link to comment Share on other sites More sharing options...
ddrazen Posted June 21, 2008 Author Report Share Posted June 21, 2008 No, no one has responded to this or contacted me about it and I'm getting frustrated. I'd like to use Retrospect instead of manually copying files over. Where are you, Mayoff? Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted June 23, 2008 Report Share Posted June 23, 2008 Where are you, Mayoff? While Mayoff does often respond to items here, please be aware that this Forum is a community based support resource; it's user helping users, _not_ an official tech support channel for Retrospect. if you need individual help on an issue that other users are not able to address, you'll want to open a Support Incident with EMC. That being said, it seems entirely reasonable to bump a post after a couple of weeks; hopefully your log has been forwarded to the engineers already. Dave (user who helps users) Quote Link to comment Share on other sites More sharing options...
byrd62au Posted July 2, 2008 Report Share Posted July 2, 2008 I solved this problem tonight yay! In Retrospect go to special and then preferences. In the OSX section tick the box that says ignore ACLS. That's it. Fixed. Done. Thanks to Dave from Keyoptions for the suggestion. I'm suprised this is not more of a known bug. Quote Link to comment Share on other sites More sharing options...
rhwalker Posted July 2, 2008 Report Share Posted July 2, 2008 I'm suprised this is not more of a known bug. Um, yes, it is a known Apple bug. It's been discussed at length here many times in the forums, and there is a knowledgebase article (that sadly, still, after over a year, incorrectly identifies which systems are affected). It looks like a Carbon framework bug that Apple has no desire to fix, and which Retrospect users must tolerate because the current code base uses the Carbon framework. Perhaps when (if) the new (Cocoa framework) Universal Binary version of Retrospect X goes into beta later this year, the bug will be fixed. Russ Quote Link to comment Share on other sites More sharing options...
byrd62au Posted July 2, 2008 Report Share Posted July 2, 2008 I'm suprised this is not more of a known bug. Um' date=' yes, it is a known Apple bug. It's been discussed at length here many times in the forums, and there is a knowledgebase article (that sadly, still, after over a year, incorrectly identifies which systems are affected). [/quote'] Ah well then I suppose I'm surprised that the Retro support people I emailed and the one who posted on this thread didn't suggest it as the first port of call. I've been tearing my hair out :glasses: Thanks! Quote Link to comment Share on other sites More sharing options...
ddrazen Posted July 2, 2008 Author Report Share Posted July 2, 2008 That works. Thanks byrd! Quote Link to comment Share on other sites More sharing options...
SMV21 Posted July 4, 2008 Report Share Posted July 4, 2008 Was just having the same problem after updating to Mac OS 10.5.4 and Retrospect. Retrospect would just quit when trying to select (a sub-vol) of the startup disk (when setting up a script). byrd's suggestion is the fix. All forums should be this easy! Thanks! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.