Re: problem with 2nd jukebox
2003-01-28 17:49:10
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)
|
|
|