Re: more with ADIC-1200 + SunOS 5.8 'sgen' driver and mtx problems
I have the same problem, but I doubt anyone will answer in the amanda forum, since I have asked about this issue before. Since it an mtx issue, I guess there's a different forum to discuss this. But I will post my message again... I have a SUN Enterprise 3500 with SunOS 5.7, a differential SCSI and a DLT L-280 SUN StorEdge array. I have attached the sst through add_drv successfully, and can issue a mtx command to eject, and the autoloader ejects one DLT tape and then loads another. That's the most I can do. Here is my output for the rest of the commands issued by mtx... # mtx -f /dev/rsst1 inquiry Product Type: Tape Drive Vendor ID: 'QUANTUM ' Product ID: 'DLT7000 ' Revision: '2560' Attached Changer: No # mtx -f /dev/rsst1 eject # mtx -f /dev/rsst1 inventory mtx: I/O error mtx:inventory failed # mtx --version mtx version 1.2.9 Usage: mtx --version mtx [ -f loader-dev ] noattach more commands\n mtx [ -f loader-dev ] inquiry | inventory | status mtx [ -f loader-dev ] first [drive#] mtx [ -f loader-dev ] last [drive#] mtx [ -f loader-dev ] next [drive#] mtx [ -f loader-dev ] previous [drive#] mtx [ -f loader-dev ] [invert] load storage-element-number [drive#] mtx [ -f loader-dev ] [invert] unload [storage-element-number][drive#] mtx [ -f loader-dev ] [eepos eepos-number] transfer storage-element-number storage-element-number mtx [ -f device ] eject # mtx -f /dev/rsst1 first mtx: No such device or address mtx: No such device or address mtx: Request Sense: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 mtx: READ ELEMENT STATUS Command Failed If I can get this simple problem fixed, I'm in buisness... -- Rhett Saunders National Office Operations email: [EMAIL PROTECTED] phone: (202) 693-3275
MTX Problems
Description of problem: Cannot get mtx to talk to my Sun StorEdge DLT-280 connected to a 64-bit platform Sun Enterprise 3500. Ok I downloaded MTX 1.2.9, and just attached sst from the contribs section of Amanda 2.4.2 to my tape device with the following /usr/kernel/drv/sst.conf configuration: name="sst" class="scsi" target=1 lun=0; I compiled the binary sst for 64-bit and placed that in my /usr/kernel/drv/sparcv9 directory. This was also added to my /etc/devlink.tab file: type=sample_driver;name=sst;minor=character rsst\A1 (to include the tab) My /dev/rsst1 was made with the add_drv command producing it's connection to: /devices/sbus@7,0/QLGC,isp@0,1/sst@1,0:character I am trying to talk to the SUN StorEdge DLT-280 (correct me if I'm wrong -- it's the same as the Quantum DLT7000 setup). Now here's what I get: hera# mtx -f /dev/rsst1 inquiry Product Type: Tape Drive Vendor ID: 'QUANTUM ' Product ID: 'DLT7000 ' Revision: '2560' Attached Changer: No hera# mtx -f /dev/rsst1 status mtx: Request Sense: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 mtx: READ ELEMENT STATUS Command Failed hera# mtx -f /dev/rsst1 first 1 mtx: Request Sense: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 mtx: READ ELEMENT STATUS Command Failed and this remains the sames for next, previous, last, and so forth... I have been ripping my hair out of my head to figure this one out. So what do I do to fix this problem? Any suggestions would be greatly appreciated! -- Rhett Saunders National Office Operations email: [EMAIL PROTECTED] phone: (202) 693-3275
Setting up L280's driver on a Sun 5.7 Platform
Ok I need help please. I have compiled the sst from the amanda-2.4.2 contribs using SUN C Compiler with the following command... cc -D_KERNEL -D_SYSCALL32 -xarch=v9 -c sst.c I did this because it's a 64-bit kernel running on a SUN Enterprise 3500. (Although I had errors during the compilation). So, I put the sst result from above into /usr/kernel/drv/sparcv9 and the sst.conf into the /usr/kernel/drv directories, respectively. Added the following entry to the /etc/devlink.tab file: type=sample_driver;name=sst;minor=character rsst\A1 Next, I had run the add_drv command on sst in the /usr/kernel/drv/sparcv9 dir. I insured the L280 StorEdge Array is hooked up and connected properly to the SCSI B differential port of the StorEdge D1000 Disk Array. After running the add_drv command, a couple of errors popped up, but the system stated it was attached, but not working properly. I added the entry into /etc/system: set sst:rsst=0 Then I rebooted to find no rsst0 in my /dev directory. If I need to unload and start over as the solution please let me know. If this is unnecessary, please let me know as well. Thanks for all your help in advance Rhett Saunders National Office Operations [EMAIL PROTECTED]
