|
Re: problem with 2nd jukebox
2003-01-29 09:58:26
Jon,
almost, this is the corrected chart.
status changer drive debug file
------ ------ ----- ----------
Good c5t4d0 0cn ...drive0
Bad c6t4d0 1cn ...drive1
All output below is from the "bad" or problem changer.
Actually all mtx commands work on both drives so I'm
thinking its not an OS issue nor an mtx issue but something
higher in the call chain.
This works
> /usr/local/sbin/mtx -f /dev/scsi/changer/c6t4d0 status
Yes, the problem exists in amtape also.
> /usr/local/sbin/amtape newtonl slot 1
amtape: could not load slot <none>: could not determine current slot
I was seeing something odd yesterday that I'm not remembering how
to reproduce this morning (but I'll keep trying), the output from
the commands was giving a listing of available slots and listed
them as 2 through 9.
The only time I'm seeing "slot_list" displayed is if I set DEBUG to 1
and then it shows up on the active screen but I'm not seeing it in the
debug file.
Today (and I don't know what is different) I'm seeing the slot list
containing 1-9 but I'm still unable to determine current tape position
and chg-zd-mtx is failing
09:07:37 Exit (2) -> <none> could not determine current slot
I'm running as user "amanda", group "sys" which is how I compiled
everything, the /usr/local/etc/amanda/* tree is properly owned
and /newtonr is working but /newtonl isn't.
I can include a script of the chg-zd-mtx output and a complete
copy of the debug file if anyone is able to look at it.
thank you,
Brian
> On Tue, Jan 28, 2003 at 02:07:27PM -0500, Brian Cuttler wrote:
> >
> > Solaris 8, Amanda 2.4.2p2 (plus /usr/local/libexec/chg-zd-mtx from 2.4.3)
> > SUN StorEdge 9,
> >
> > /usr/local/sbin/mtx -f /dev/scsi/changer/c6t4d0 inquiry
> > Product Type: Medium Changer
> > Vendor ID: 'HP '
> > Product ID: 'C7145 '
> > Revision: '233S'
> > Attached Changer: No
> >
> > Config works perfectly with drive /dev/rmt/1cn and changer
> > /dev/scsi/changer/c5t4d0, now so with 0cn and c6t4d0.
> >
> > I finally figured out the script was naming the output files based
> > on the number of the drive, ie 0cn logs to changer.debug.drive0 and
> > 1cn has log file changer.debug.drive1.
> >
>
> Maybe I'm not following.
>
> status changer drive debug fild
> Good c5t4d0 1cn ...drive1
> Bad c6t4d0 0cn ...drive0
> >
> >
> > > /usr/local/sbin/mtx -f /dev/scsi/changer/c6t4d0 status
>
> That's the bad one.
>
> > Storage Changer /dev/scsi/changer/c6t4d0:1 Drives, 9 Slots ( 0
> > Import/Export )
> > Data Transfer Element 0:Empty
> > Storage Element 1:Full :VolumeTag=AF6385L1
> > Storage Element 2:Full :VolumeTag=AF6386L1
> > Storage Element 3:Full :VolumeTag=AF6387L1
> > Storage Element 4:Full :VolumeTag=AF6388L1
> > Storage Element 5:Full :VolumeTag=AF6389L1
> > Storage Element 6:Full :VolumeTag=AF6399L1
> > Storage Element 7:Full :VolumeTag=CLNI59L1
> > Storage Element 8:Full :VolumeTag=CLNI58L1
> > Storage Element 9:Full :VolumeTag=CLNI57L1
> >
> > # setenv DEBUG 1
> > # /usr/local/libexec/chg-zd-mtx -info
> >
> > > cat changer.debug.drive1
>
> That's the good one.
>
> > Storage Changer /dev/scsi/changer/c6t4d0:1 Drives, 9 Slots ( 0
> > Import/Export )
> > Data Transfer Element 0:Empty
> > Storage Element 1:Full :VolumeTag=AF6385L1
> > Storage Element 2:Full :VolumeTag=AF6386L1
> > Storage Element 3:Full :VolumeTag=AF6387L1
> > Storage Element 4:Full :VolumeTag=AF6388L1
> > Storage Element 5:Full :VolumeTag=AF6389L1
> > Storage Element 6:Full :VolumeTag=AF6399L1
> > Storage Element 7:Full :VolumeTag=CLNI59L1
> > Storage Element 8:Full :VolumeTag=CLNI58L1
> > Storage Element 9:Full :VolumeTag=CLNI57L1
> > > cat changer.debug.drive1
>
> That's the same file but the contents differ below
>
> > 13:58:23 === Start Tue Jan 28 13:58:23 EST 2003 ===
> > 13:58:23 Arg info:
> > $# = 1
> > $0 = "/usr/local/libexec/chg-zd-mtx"
> > $1 = "-info"
> > 13:58:23 Running: mtx status
> > 13:58:23 Exit code: 0
> > Stdout:
> > Storage Changer /dev/scsi/changer/c6t4d0:1 Drives, 9 Slots ( 0
> > Import/Export )
> > Data Transfer Element 0:Empty
> > Storage Element 1:Full :VolumeTag=AF6385L1
> > Storage Element 2:Full :VolumeTag=AF6386L1
> > Storage Element 3:Full :VolumeTag=AF6387L1
> > Storage Element 4:Full :VolumeTag=AF6388L1
> > Storage Element 5:Full :VolumeTag=AF6389L1
> > Storage Element 6:Full :VolumeTag=AF6399L1
> > Storage Element 7:Full :VolumeTag=CLNI59L1
> > Storage Element 8:Full :VolumeTag=CLNI58L1
> > Storage Element 9:Full :VolumeTag=CLNI57L1
> > 13:58:23 Config info:
> > firstslot = "1"
> > lastslot = "9"
> > cleanslot = "-1"
> > cleancycle = "120"
> > offline_before_unload = "0"
> > unloadpause = "0"
> > autoclean = "0"
> > autocleancount = "99"
> > havereader = "1"
> > driveslot = "1"
> > poll_drive_ready = "3"
> > max_drive_wait = "120"
> > 13:58:23 Exit (2) -> <none> could not determine current slot
>
> If you do an amtape to load the first slot does it fail also?
>
> >
> >>> End of included message <<<
>
> --
> Jon H. LaBadie jon AT jgcomp DOT com
> JG Computing
> 4455 Province Line Road (609) 252-0159
> Princeton, NJ 08540-4322 (609) 683-7220 (fax)
|
|
|
