Re: problem with 2nd jukebox
Jean-Louis, > Your driveslot must be set to '0', that's the drive you want to use. Quite right. I was being dense, I'd come to accept that the tapedev and the changerdev where separate entities and wasn't thinking in terms of the changer having any options as to where to load the tape into its drive, especially as there is only the one in my configuration. I've replaced my work-around with the corrected configuration. thank you, Brian --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: problem with 2nd jukebox
Jean-Louis, This display is 'normal' if I've unloaded the tape from the drive into the jukebox. # /usr/local/sbin/mtx -f /dev/scsi/changer/c6t4d0 unload > Data Transfer Element 0:Empty I see the same result from the jukebox/drive at c5t4d0 under the same circumstances. What the drive is loaded I see that one of the slots in the jukebox is empty. (here using jukebox # 1) > /usr/local/sbin/mtx -f /dev/scsi/changer/c5t4d0 status Storage Changer /dev/scsi/changer/c5t4d0:1 Drives, 9 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 2 Loaded):VolumeTag = AF6392L1 Storage Element 1:Full :VolumeTag=AF6393L1 Storage Element 2:Empty:VolumeTag= Storage Element 3:Full :VolumeTag=AF6391L1 Storage Element 4:Full :VolumeTag=AF6390L1 Storage Element 5:Full :VolumeTag=AF6394L1 Storage Element 6:Full :VolumeTag=AF6395L1 Storage Element 7:Full :VolumeTag=AF6396L1 Storage Element 8:Full :VolumeTag=AF6398L1 Storage Element 9:Full :VolumeTag=AF6397L1 === > On Tue, Jan 28, 2003 at 02:07:27PM -0500, Brian Cuttler wrote: > > 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) -> could not determine current slot > > Your driveslot must be set to '0', that's the drive you want to use. > > Jean-Louis > -- > Jean-Louis Martineau email: [EMAIL PROTECTED] > Departement IRO, Universite de Montreal > C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 > Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: problem with 2nd jukebox
On Tue, Jan 28, 2003 at 02:07:27PM -0500, Brian Cuttler wrote: > 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) -> could not determine current slot Your driveslot must be set to '0', that's the drive you want to use. Jean-Louis -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: problem with 2nd jukebox
You have number_configs 2, you have how many jukeboxes ? We only have one StorEdge L9, but for some reason, if I tried 'number_configs 1', I could not get it to work. I tried numbering the config '1', '0' and not at all. James, does chg-scsi work ok with a 2nd jukebox/drive ? Sorry, I haven't tried this (see above), although we're supposed to get our hands on some more changers soon :) James. -- UNIX and Comms, Computing, Royal Botanic Gardens, Kew Tel: +44 (0)20 8332 5729 Email: [EMAIL PROTECTED] PGP public key from: www.jamesthorne.net/j.thorne.pgp www.keyserver.net
Re: problem with 2nd jukebox
James, You have number_configs 2, you have how many jukeboxes ? I had problems with the 1st jukebox using the chg-zd-mtx script from 2.4.2p2 but replacing the script with the one in the 2.4.3 kit resolved the issue. Its adding the 2nd jukebox that is causing me this problem the first jukebox continues to function without problem. I've got 2 completely separate amanda config (sub)trees for the two jukeboxes, basically L and R configurations differ in the definitions of tapedev, changerdev, labelstr and the paths in the amanda-work area, infofile, logdir and indexdir, else the configs where identical. My best guess is that the issue is induced by the change of drive id number. > Hi Brian, > > Brian Cuttler wrote: > > Solaris 8, Amanda 2.4.2p2 (plus /usr/local/libexec/chg-zd-mtx from 2.4.3) > > SUN StorEdge 9, > > I was running the exact same setup as this. mtx was working fine for me > too. However... > > > 13:58:23 Exit (2) -> could not determine current slot > > I got the same error messages from chg-zd-mtx. :( > > After a couple of days of trying, I gave up, installed amanda 2.4.3 and > used the new chg-scsi that came with 2.4.3. [You could probably use it > without upgrading amanda, I don't know.] > > Anyway, this worked wonderfully and the chg-scsi script sent changer > commands straight to the StorEdge L9 without the need for mtx at all. :) > > amtape and everything else then worked fine. My chg-scsi config file is: > > ### > > number_configs 2 > > eject 0 > sleep 60 > cleanmax 20 > changerdev /dev/scsi/changer/c4t0d0 > scsitapedev /dev/nrst15 > > config 1 > > drivenum 0 > dev /dev/nrst15 > startuse 0 > enduse 7 > statfile /usr/local/etc/amanda/Images/chg-scsi.statfile > #slotfile /usr/local/etc/amanda/Images/chg-scsi.slotfile > cleancart 8 > #cleanslot 9 > cleanfile /usr/local/etc/amanda/Images/chg-scsi.cleanfile > usagecount /usr/local/etc/amanda/Images/chg-scsi.usagecount > tapestatus /usr/local/etc/amanda/Images/chg-scsi.tapelog > > ### end of chg-scsi.conf ### > > In amanda.conf, you need: > >tapedev "1" # use config '1' in chg-scsi.conf >tpchanger "chg-scsi"# the tape-changer glue script >changerfile "chg-scsi.conf" # or whatever you want to call it > > Hope this helps. :) > > James. > > -- > UNIX and Comms, Computing, Royal Botanic Gardens, Kew > Tel: +44 (0)20 8332 5729 > Email: [EMAIL PROTECTED] > PGP public key from: www.jamesthorne.net/j.thorne.pgp > www.keyserver.net >
Re: problem with 2nd jukebox
Jon, almost, this is the corrected chart. status changer drive debug file -- -- - -- Goodc5t4d0 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 : 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) -> 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
Re: problem with 2nd jukebox
Hi Brian, Brian Cuttler wrote: Solaris 8, Amanda 2.4.2p2 (plus /usr/local/libexec/chg-zd-mtx from 2.4.3) SUN StorEdge 9, I was running the exact same setup as this. mtx was working fine for me too. However... 13:58:23 Exit (2) -> could not determine current slot I got the same error messages from chg-zd-mtx. :( After a couple of days of trying, I gave up, installed amanda 2.4.3 and used the new chg-scsi that came with 2.4.3. [You could probably use it without upgrading amanda, I don't know.] Anyway, this worked wonderfully and the chg-scsi script sent changer commands straight to the StorEdge L9 without the need for mtx at all. :) amtape and everything else then worked fine. My chg-scsi config file is: ### number_configs 2 eject 0 sleep 60 cleanmax 20 changerdev /dev/scsi/changer/c4t0d0 scsitapedev /dev/nrst15 config 1 drivenum 0 dev /dev/nrst15 startuse 0 enduse 7 statfile /usr/local/etc/amanda/Images/chg-scsi.statfile #slotfile /usr/local/etc/amanda/Images/chg-scsi.slotfile cleancart 8 #cleanslot 9 cleanfile /usr/local/etc/amanda/Images/chg-scsi.cleanfile usagecount /usr/local/etc/amanda/Images/chg-scsi.usagecount tapestatus /usr/local/etc/amanda/Images/chg-scsi.tapelog ### end of chg-scsi.conf ### In amanda.conf, you need: tapedev "1" # use config '1' in chg-scsi.conf tpchanger "chg-scsi"# the tape-changer glue script changerfile "chg-scsi.conf" # or whatever you want to call it Hope this helps. :) James. -- UNIX and Comms, Computing, Royal Botanic Gardens, Kew Tel: +44 (0)20 8332 5729 Email: [EMAIL PROTECTED] PGP public key from: www.jamesthorne.net/j.thorne.pgp www.keyserver.net
Re: problem with 2nd jukebox
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 Badc6t4d0 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) -> 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 [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
