Thanks once again for your help John. You provided plenty of food for
thought.....
On Wed, 2 May 2001, John R. Jackson wrote:
> >So far I have tried the following :
> >- built and installed sst form the 2.4.2p2 source. I have a /dev/rsst1 and
> >running sstest '/dev/rsst1 rew' I get 'Device rewound, status =
> >0x0'. ...
>
> You tried to rewind a tape changer? I'm surprised it didn't stick its
> tongue out at you and drop all the tapes on the floor. :-)
I should have been paying a bit more attention ;)
> You might grab:
>
> ftp://gandalf.cc.purdue.edu/pub/amanda/atl_op
Got it.
> That's a little test program I use to exercise my ATL robot through the
> sst interface. After you chmod +x it, try these things:
>
> atl_op -h # to see the help message
> atl_op -f /dev/rsst1 -v inquiry
>
> But there are other problems you need to look at first ...
>
> >- I have built the latest mtx from sourceforge :
> > # mtx -f /dev/rsst1 inquiry
> > Product Type: Disk Drive
>
> Ummm, that would seem to be a very bad thing. You're talking to a disk
> drive, not your changer. :-)
>
> That, in turn, implies /dev/rsst1 is not pointing where you want it to.
>
> Were any other /dev/rsst* devices created? What does rsst1 point to?
Only /dev/rsst1 was created which as you say points to the drive not the
changer. I tried to change the sst.conf file as follows :
name="sst"
parent="/pci@1f,2000/scsi@1/sst@1,0:character"
target=1 lun=0;A
but this caused a kernel panic !
I created the link by hand :
ln -s ../devices/pci@1f,2000/scsi@1/sst@1,0:character rsst2
and now I can :
# ./atl_op -f /dev/rsst2 inquiry
atl_op: device type "CHANGER"
atl_op: removeable
atl_op: vendor "HP "
atl_op: product "C6280-7000 "
atl_op: revision_level "2.10"
but still get :
# ./mtx -f /dev/rsst2 status
mtx: Request Sense: Long Report=yes
mtx: Request Sense: Valid Residual=no
mtx: Request Sense: Error Code=0 (Unknown?!)
mtx: Request Sense: Sense Key=No Sense
mtx: Request Sense: FileMark=no
mtx: Request Sense: EOM=no
mtx: Request Sense: ILI=no
mtx: Request Sense: Additional Sense Code = 00
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
but doing an inquiry produces the same results as atl_op and inventory
causes some changer activity but nothing to stdin.
The following gets logged to /var/adm/messages :
unix: WARNING: /pci@1f,2000/scsi@1/sst@1,0 (sst2)
Error for Command: <undecoded cmd 0xb8> Error Level: Fatal
unix: Requested Block: 0 Error Block: 0
unix: Vendor: HP Serial Number: 99255B9697
unix: Sense Key: Illegal Request
unix: ASC: 0x24 (invalid field in cdb), ASCQ: 0x0, FRU: 0x0
> What do you get if you do this:
>
> find /devices -name 'sst*'
# find /devices -name 'sst*'
/devices/pci@1f,4000/scsi@3/sst@1,0:character
/devices/pci@1f,2000/scsi@1/sst@1,0:character
The top one is an internal disk drive (I think) and the bottom one is the
changer.
> What did the system reboot say (e.g. /var/adm/messages) when it scanned
> the devices, in particular about your changer or the sst devices?
unix: sst0: found Direct Access device at tgt1, lun0
unix: sst0: Vendor/Product ID = IBM DDRS34560SUN4.2G
unix: sst0 at glm0:
unix: target 1 lun 0
unix: sst0 is /pci@1f,4000/scsi@3/sst@1,0
unix: sst1: No response from target 1, lun 0
unix: sst2: found Changer device at tgt1, lun0
unix: sst2: Vendor/Product ID = HP C6280-7000
unix: sst2 at glm2:
unix: target 1 lun
unix: sst2 is /pci@1f,2000/scsi@1/sst@1,0
unix: sst3: No response from target 1, lun 0
What do I need to do ??
Thanks once again John.
Cheers, Adam.
