I'm having trouble hooking up a Solaris 2.5.1 SS1000E and an old 9
track tape drive. I read through some c.u.s postings and found out
about mtinfo, but am still not getting very far.
There are three (and only three) devices on this particular SCSI bus:
There are three other tape drives, but they are on different SCSI buses.
Here's what /usr/adm/messages has to say:
st36: <Vendor 'NCR ADP5' Product '6-02-01 '>
st36 at esp5:
st40: <Quantum DLT4000>
st40 at esp5:
st41: <Exabyte EXB-8500 8mm Helical Scan>
st41 at esp5:
I read the "st" man page and converted the single quotes to "\047" as
it said to. I made sure I entered blanks, not tabs, for the whitespace
(actually, I editor-copied the line from /usr/adm/messages to st.conf).
When I put the following in st.conf:
"Vendor \047NCR ADP5\047 Product \0476-02-01 \047","Aviv","AVIV",
this showed up in /usr/adm/messages:
WARNING: Character overflow detected.
which sounds like a parsing bug to me. So I looked at some more examples
and they seemed to indicate I could just do "\'". Now I have:
"Vendor \'NCR ADP5\' Product \'6-02-01 \'", "Aviv", "AVIV",
That makes the "overflow" error go away, but I still cannot access
the drive. Running mtinfo on /dev/rmt/4n with a tape loaded gives:
Cannot open /dev/rmt/4n
open device: I/O error
mtinfo V2.1 26-Mar-97
and I get this on the console:
st36: Fixed record length (512 byte blocks) I/O
There are no other messages being logged that I can find to give me any
clue what "I/O error" is supposed to mean in this case. I can access
the DLT and the ExaByte just fine.
If it matters, here are the other related entries from st.conf:
AVIV = 1,0x33,0,0x041d,4,0x02,0x02,0x03,0x03,2;
name="st" class="scsi"
target=0 lun=0;
name="st" class="scsi"
target=1 lun=0;
name="st" class="scsi"
target=2 lun=0;
name="st" class="scsi"
target=3 lun=0;
name="st" class="scsi"
target=4 lun=0;
name="st" class="scsi"
target=5 lun=0;
name="st" class="scsi"
target=6 lun=0;
So, three questions:
* Any ideas on how to get this to work or what I'm doing wrong?
* The machine with this drive is a production server and I'd like
to get more than a few minutes once a week to work on this problem.
What is the exact sequence to unload (and reload?) the "st" driver
so it will reread st.conf? The man pages are not sufficient and
I don't have (or need) the device driver writing documentation.
I do know a little about modinfo and modunload.
* We have a second AVIV box with two drives that I assume uses
different logical units (as compared to SCSI targets) to tell
them apart. Is it a simple matter of adding:
name="st" class="scsi"
target=1 lun=1;
to get access to the second drive (i.e. for "boot -r" et al to
find it and create a name I can use)?
Personal E-mail responses would be fine as I doubt this is of much
interest to anyone else.