Help: mtx -f /dev/rmt/0 inquiry and status L280
Leo Gonzales, Jr.
I'm just recently installed StorEgde L280 autoloader w/ DLT 7000 drive on
Sun 220R running Solaris 8. I also want to
use mtx / amanda to control the L280. I added the following lines to the
sgen.conf file and reboot -- -r:
device-type-config-list="changer";
name="sgen" class="scsi" target=0 lun=0;
name="sgen" class="scsi" target=1 lun=0;
'mtx -f /dev/rmt/0 status' command returns:
mtx: Request Sense: Long Report=yes
mtx: Request Sense: Valid Residual=no
mtx: Request Sense: Error Code=70 (Current)
mtx: Request Sense: Sense Key=Not Ready
mtx: Request Sense: FileMark=no
mtx: Request Sense: EOM=no
mtx: Request Sense: ILI=no
mtx: Request Sense: Additional Sense Code = 04
mtx: Request Sense: Additional Sense Qualifier = 00
mtx: Request Sense: BPV=no
mtx: Request Sense: Error in CDB=no
mtx: Request Sense: SKSV=no
READ ELEMENT STATUS Command Failed
and
'mtx -f /dev/rmt/0 inquiry' command returns:
Product Type: Tape Drive
Vendor ID: 'QUANTUM '
Product ID: 'DLT7000 '
Revision: '2560'
Attached Changer: No
Questions:
1. Are the lines I added in the sgen.conf correct?
2. Do I need to do something to st.conf or some other conf file?
3. Why do I get 'READ ELEMENT STATUS Command Failed'?
4. Shouldn't the 'mtx -f /dev/rmt/0 inquiry' return 'Attached Changer: YES'
instead of NO?
Thanks in advance,
Leo
Ben
What do you have for /dev/scsi/changer/cXtXdX, if anything? Do you have
any way to test changer-control from the system?
> 2. Do I need to do something to st.conf or some other conf file?
I'm presuming you've done this already but here it is anyway.
For the st.conf file, yes, if you haven't updated it, you should
uncomment a few lines regarding "DLT7K". *FOR EXAMPLE*:
tape-config-list =
"QUANTUM DLT7000", "Quantum DLT7000", "DLT7k-data";
"DLT tape data" = 1, 0x38, 0, 0x8639, 4, 0x82, 0x83, 0x84, 0x85, 3; <---
this has changed.
Use whatever's in the file currently -- these lines should exist
already. That should get you by.
Despite common belief, you don't have to reboot. Do this:
'modinfo | grep "st ("' <--- note the module number. Do command w/o
grep to see column headings.
'modunload -i <st-module-number>
'modload -p drv/st'
-- take a peek in the messages file to see if the system picked up the
new drive settings.
(you could probably do similarly for the sgen driver also -- although, I
haven't tried that)
> 3. Why do I get 'READ ELEMENT STATUS Command Failed'?
Did you load a tape? I have an L280 at work and it gives a "not ready"
status (mt -f /dev/rmt/0 status) when there's no tape loaded. Try
loading a tape through the L280's front control-panel and running the
status again.
Go to sunsolve.sun.com and see info doc #30. That's a good reference
there for using/troubleshooting the L280s and other drives.
> 4. Shouldn't the 'mtx -f /dev/rmt/0 inquiry' return 'Attached Changer: YES'
> instead of NO?
Well, ideally, yes (sorry, I know that was smart ;^) Your config looks
OK. Do you know what target ID the changer specifically responds to?
I'm pretty sure it's "1". You don't have any other changers or other
devices using sgen target ID "1", do you?
>
> Thanks in advance,
> Leo
No problem. Hope it helps.
Ben--
Leo Gonzales, Jr.
news:3B689D8D.7F7D892E@mail_and_news_._com...
Ben,
Thanks for the response. As it turns out I needed to specify the changer in
the mtx command as follows:
'mtx -f /dev/scsi/changer/c4t1d0 inquiry|status|load etc ...' instead of '
mtx -f /dev/rmt/0 ...' That solved the
problem I was having.
Leo
Ben Van Loock
Don´t touch the st.conf file if you don´t have too. All that´s in there
IS what is supportd by the st driver.
It will not make any difference it you uncomment these lines without
actually changing the values.
Ben wrote:
....
> For the st.conf file, yes, if you haven't updated it, you should
> uncomment a few lines regarding "DLT7K". *FOR EXAMPLE*:
>
> tape-config-list =
> "QUANTUM DLT7000", "Quantum DLT7000", "DLT7k-data";
> "DLT tape data" = 1, 0x38, 0, 0x8639, 4, 0x82, 0x83, 0x84, 0x85, 3; <---
> this has changed.
>
> Use whatever's in the file currently -- these lines should exist
> already. That should get you by.
.....
Ben, another one.