Jump to content

Cancelling script loses comm to Tape drive until reboot + kernel panics

Recommended Posts

This happens now 4 out of 5 times that I try and cancel a running script, in Backup Server 6.0.


Steps to reproduce:

Hit cancel during a script running from Backup Server


Expected Results:

Script cancels and returns control to user


Actual Results:

Retrospect hangs after about 5 minutes of the spinning beachball

All access to SCSI SDLT320 drive is locked out until server reboot

Pushing eject button on tape drive causes hard lock/kernel panic on server (even after retrospect is no longer running)


Machine/Software Specs:

OSX Server 10.3.7 (with all but today's security patches)

Permissions repaired nightly (cron'ed)

Retrospect 6.0, running Backup Server


If anyone has any suggestions it would be great and if there's any other info that would be helpful please let me know. This used to happen on occasion, but now happens regularly, even after clean install of OS. Hardware disagnostics show no problems with SCSI card or tape drive.

Link to comment
Share on other sites

  • 2 weeks later...

The driver update didn't help, it seems to be worse now, instead of losing communication I go straight to kernel panic, in this case I didn't even cancel but it was a script running (about to start verification). Here's a stack trace from the logs if it's helpful:



Fri Feb 4 15:19:22 2005



panic(cpu 0): IOGMD: not wired for getPhysicalSegment()

Latest stack backtrace for cpu 0:


0x000836E4 0x00083BC8 0x0001EDA4 0x0026C62C 0x0026C848 0x0026C4A4 0x00717D38 0x0071813C

0x003AB768 0x003B70A8 0x003BB17C 0x003ADEE0 0x006C5D38 0x003ADA28 0x003AE000 0x0071548C

0x00280648 0x0007B8AC 0x00021668 0x0001BCE8 0x0001C0F0 0x000943B8 0x00000000

Kernel loadable modules in backtrace (with dependencies):


dependency: com.apple.iokit.IOStorageFamily(1.3.4)@0x5f2000

dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(1.3.8)@0x3a6000


dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(1.3.8)@0x3a6000


Proceeding back via exception chain:

Exception state (sv=0x2EED5000)

PC=0x900074C8; MSR=0x0200F030; DAR=0x09160000; DSISR=0x42000000; LR=0x90007018; R1=0xBFFF9570; XCP=0x00000030 (0xC00 - System call)


Kernel version:

Darwin Kernel Version 7.7.0:

Sun Nov 7 16:06:51 PST 2004; root:xnu/xnu-517.9.5.obj~1/RELEASE_PPC

Link to comment
Share on other sites

Hi Dave


Had you asked I would have gladly posted it! sigh. "Gave up" is about where I'm at with retrospect if I can't get this issue resolved frown.gif Is Eric still around after the EMC changeover? Maybe he can better advise me on this...


It's a Lacie branded Quantum SDLT-320, 6-7 months old (it was replaced the last time we ran into retrospect problems and it turned out to be retrospect's fault and not the tape drive's after some deliberation between Eric and myself). It works fine accessing directly from command line on the same box, and it also has no issues when attached to a linux server running Storix backup.


Any help you can offfer would be appreciated.

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...