If it helps, I am running mtx 1.2.17rel and modified the /usr/local/libexec script, not certain if I completely replaced with with another version - but I know that I did replace the shell call on the first like and now invoke /bin/sh rather than ksh.
Yes, I replaced the original script with one retrieve after discussion with Peter Stokes (he provided the following URL). but I do not know the version of the script, I further changed the script by replacing the shell call on the first line. Notes are from April 2003, the URL is http://www.ashlyn.co.uk/downloads/chg-zd-mtx If the script looks to be your problem and the link is bad I can email the script I use. It is about 2x the size of the script that had come with MTX 1.2.17rel. On Mon, Sep 17, 2007 at 09:38:31AM -0400, Brian Cuttler wrote: > > I'm sorry, missed this thread until this morning and don't know > your config or the actual problem. > > I have an L9 on solaris and might be able to help. > > See that you've configured sgen, the L9 uses different scsi id > for the robot and the tape, these have to be reflected in the > amanda.conf. This is somewhat unlike the C2 which used a single > scsi id and different LUNs. > > Don't know which glue script you are using, I'm running the mtx > version, chg-zd-mtx, however I found that the version of mtx > I was running had a problem with the script itself. I have to dig > through my notes to find both the version and the problem, it was > something I think as simple as the shell the script invoked. > > Sorry - realize I'm being less than completely helpful, but those > are the items that I recall biting me. The good news is that I've > successfully run the L9 from Solaris for at least 5 years, under > amanda and mtx and have been very pleased. > > Brian > > > On Mon, Sep 17, 2007 at 07:07:16AM -0400, Chris Hoogendyk wrote: > > > > > > Craig Dewick wrote: > > > > > >I've had another go at this today by shifting the entire Amanda host > > >setup to a different machine (Sun Ultra 2) and recompiling mtx and > > >amanda from source. I'm using the same sort of Sbus Qlogic > > >differential SCSI card to communicate with the L9 array that I had in > > >the previous host system. > > > > > >After figuring our the right config for the 'sgen' driver, I changed > > >the amanda.conf file to show the device name for the changer (it's > > >been detected as /dev/scsi/sequential/c1t1d0). > > > > > >I have all the directories that Amanda needs created and chowned to be > > >owned by amanda with group 'sys' and I also changed all the /dev/rmt > > >nodes along with /dev/scsi/sequential/c1t1d0 to be owned by amanda > > >with group 'sys'. > > > > > >However when I rum 'amcheck' I still get the: > > > > > >Changer problem: no slots available > > > > > >error message that occured with the previous host system. Running > > >'amtape ORBnet update' produces the same thing. > > > > > >If I replace 'tapelist' with a blank file, same result. > > > > > >I'm also starting to think the problem is the array itself but I am > > >sure others are using L9's with Amanda without any problems, even > > >connected to a Sun box for the host. > > > > > >Can anyone think of anything else I should be checking? > > > > > >Running 'mtx -f /dev/scsi/sequential/c1t1d0 inquiry' reports the DLT > > >drive type, etc. as expected. > > > > Just a possible note on this. > > > > When I configured my AIT5 library, I configured the tape drive with > > st.conf and the library with sgen.conf. I ended up getting the tape as > > /dev/rmt/1 and the library as /dev/scsi/changer/something. In the > > process of setting it up, I did everything one step at a time. I first > > just played with the front panel of the library to load a tape and mt > > and ufsdump to do things with the tape. Then I installed mtx and > > configured it and spent some time playing with that to see that I could > > move tapes around and load them and unload them. Finally, I configured > > chg-zd-mtx and amanda to use the tape drive and changer. Then I played a > > bit with amtape and amlabel to see that I could set the current slot, > > check the tape in the current slot, label it and so on. Only after that > > did I set up a tape rotation and launch amdump. That process kept it > > from being too complicated. > > > > The question I would have on your setup is whether your changer presents > > itself as 2 different devices and needs to be set up this way (using > > both st.conf and sgen.conf). I never had to mess with ownership of > > anything in /dev. > > > > > > > > --------------- > > > > Chris Hoogendyk > > > > - > > O__ ---- Systems Administrator > > c/ /'_ --- Biology & Geology Departments > > (*) \(*) -- 140 Morrill Science Center > > ~~~~~~~~~~ - University of Massachusetts, Amherst > > > > <[EMAIL PROTECTED]> > > > > --------------- > > > > Erd?s 4 > > > > > --- > Brian R Cuttler [EMAIL PROTECTED] > Computer Systems Support (v) 518 486-1697 > Wadsworth Center (f) 518 473-6384 > NYS Department of Health Help Desk 518 473-0773 > > > > IMPORTANT NOTICE: This e-mail and any attachments may contain > confidential or sensitive information which is, or may be, legally > privileged or otherwise protected by law from further disclosure. It > is intended only for the addressee. If you received this in error or > from someone who was not authorized to send it to you, please do not > distribute, copy or use it or any attachments. Please notify the > sender immediately by reply e-mail and delete this from your > system. Thank you for your cooperation. > > --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support (v) 518 486-1697 Wadsworth Center (f) 518 473-6384 NYS Department of Health Help Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
