From: Ballowe, Charles (CBallowe@usg.com)
Date: Fri Sep 13 2002 - 15:17:20 EDT
Turns out that the tape drive in question was wanting a cleaning, so
we gave it a cleaning tape. After it finished with that, we still couldn't
see it.
Alan@nabeth was providing some useful debugging information, however a
mis-typed bus id in a "scu> set nexus" command crashed a member of my
cluster, the reboot caused the tape drive to be seen. That was unpleasant,
but none of my users notice -- go go gadget application failover :).
-charlie
-----Original Message-----
From: Ballowe, Charles [mailto:CBallowe@usg.com]
Sent: Friday, September 13, 2002 11:39 AM
To: 'tru64-unix-managers@ornl.gov'
Subject: tape drive problems
I have a tape device in a SAN that I seem to have lost the ability to use.
Any clue what I might be able to do to re-establish contact with it without
downing my servers? Would resetting the MDR that is doing the fiber-scsi
bridging possibly fix the problem? combined with a hwmgr -scan scsi?
other suggestions?
Component State Change: Component "SCSI-WWID:0c000008:00e0-9e60-0003-2f03"
is unavailable (HWID=179)
Connectivity has been lost for device 25 (3/0/1)
Connectivity has been lost for device 25 (0/0/0)
DRD: Removed (unmapped) DRD server oraproddb
DRD: No server found for device 179
Charles Ballowe /"\
Unix System Administrator \ / ASCII Ribbon Campaign
cballowe@usg.com X Against HTML Mail
x3896 / \
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:53 EDT