Hiya,
Ok, I've reconfigured my system now so that all SCSI devices except the
autochanger are attached to the wide SCSI controller my SunSwift card. The
autochanger is the sole occupant of the standard narrow scsi bus.
My setup is - Sparc 20, Solaris 8, mtx-1.2.10, SunOS 'sgen' driver for changer
I've typed a series of commands using 'mtx' to talk to the autochanger,
and the results are not good:
# ls -sal /dev/scsi/changer
total 6
2 drwxr-xr-x 2 root root 512 Mar 24 10:13 .
2 drwxr-xr-x 3 root root 512 Mar 24 10:13 ..
2 lrwxrwxrwx 1 root root 95 Mar 24 10:13 c0t5d0 ->
../../../devices/iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sgen@5,0:changer
This was to confirm that the sgen driver had detected the autochanger and
attached properly.
# mtx -f /dev/scsi/changer/c0t5d0 inquiry
Product Type: Medium Changer
Vendor ID: 'ADIC '
Product ID: 'DAT AutoChanger '
Revision: '0461'
Attached Changer: No
This caused the 'sgen' driver to initialise itself and print the usual
messages in the console window, and the autochanger responded correctly.
So far, this is good, but I'm not quite sure why it reported the last
piece of information as 'No'.
# mtx -f /dev/scsi/changer/c0t5d0 status
mtx: no Data Transfer Element reported
Starting to be a problem. I don't know what the error message means, but
my presumption is that mtx didn't get a response where one was expected.
# mtx -f /dev/scsi/changer/c0t5d0 inventory
mtx: Invalid argument
mtx:inventory failed
I tried this since it shows up as a valid option with 'mtx --version' in
the usage report.
# mtx -f /dev/scsi/changer/c0t5d0 inquiry
mtx: I/O error
mtx: Request Sense: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
mtx: INQUIRY Command Failed
This is the first clear failure. After this I cycled the power to the
autochanger, and tried these commands:
# mtx -f /dev/scsi/changer/c0t5d0 first
mtx: no Data Transfer Element reported
Strange, since the autochanger had just been power-cycled.
# mtx -f /dev/scsi/changer/c0t5d0 inquiry
mtx: I/O error
mtx: Request Sense: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
mtx: INQUIRY Command Failed
Once again, a clear failure of SCSI communication. Now since I'd just
cycled the power to the autochanger, this, to me, points to a problem with
software on this machine since the ADIC unit should have come back with
a valid response.
>From here, I can take a few different course of action. The one I'm
thinking of trying the most is to discontinue use of the 'sgen' driver and
install the 'sst' driver from the amanda-2.4.2p1 source tree to see if
that reacts correctly when 'mtx' send commands to the autochanger.
Another possibility is that 'mtx' itself is broken as far as working with
the 'sgen' driver is concerned. I had it talking fairly successfully to
one of the HP 6-tape autochangers before when I was using 2.4.1p1 with the
'sst' driver. Are there any known problems with v1.2.10 of 'mtx' that
might affect it's performance with the SunOS 'sgen' driver?
Regards,
Craig.
--
Craig Dewick. Send email to "[EMAIL PROTECTED]"
Point a web browser at 'http://lios.apana.org.au/~cdewick/sun_shack.html' to
access my archive of Sun information and links to other places. For info
about Sun Ripened Kernels, go to "http://www.sunrk.com.au"
