I am trying to configure an external SCSI DAT drive to an Ultra60 w/
Solaris 9. It is a Dell Powervault 100T, which I find to be a
re-branded Seagate STD6401LW.

I Google'd the config details I would need for the /kernel/drv/st.conf
entry and found:

tape-config-list=
"SEAGATE DAT 06240-XXX", "Seagate DAT Drive", "SEAGATE_DAT";
SEAGATE_DAT = 1,0x34,0,0xd639,4,0x00,0x8C,0x8C,0x8C,3;

Following a handful of usenet posts I found, I placed that detail into
st.conf, rebooted, used STOP-A, and at OK prompt used:

setenv auto-boot? false
reset
probe-scsi-all

Solaris gave:
-------------------
/pci@1f, 4000/scsi@3,1
Target 4
Unit 0 Removable Tape Archive Python 06408-xxx8071

/pci@1f, 4000.scsi@3
Target 0
Unit 0 Disk Seagate <my 1st hard disk info....>

Target 1
Unit 0 Disk Seagate <my 2nd hard disk info....>

Target 6
Unit 0 Sony CD-Rom <etc...>
-------------------

I was happy to see something recognized, but I suppose I was a little
suprised to see it listing "Python" rather than a Seagate device.
Nonetheless I carried on with:

setenv auto-boot? true
boot -r

I noticed a handful of entries in /dev/rmt/. I attempted writing to the
drive with:
tar cvf /dev/rmt/0 /export/home/my_name/test/*

and got back: tar: /dev/rmt/0: I/O error

Having a look in /var/adm/messages I see:
Sep 19 11:38:36 sunking scsi: [ID 365881 kern.info]
/pci@1f,4000/scsi@3,1/st@4,0 (st11):
Sep 19 11:38:36 sunking <Archive Python 4mm Helical Scan>
Sep 19 11:38:36 sunking scsi: [ID 193665 kern.info] st11 at glm1: target
4 lun 0
Sep 19 11:38:36 sunking genunix: [ID 936769 kern.info] st11 is
/pci@1f,4000/scsi@3,1/st@4,0

So, do you think the details above are pointing me at having the wrong
config lines in my st.conf? Or, are the details from probe-scsi-all
suggesting I am stepping on the same SCSI id? I have the switch on the
back of the DAT drive set to "4"...I don't know if the scsi@3 part in
the probe-scsi-all results is significant to my problem.

Thanks for any pointers.
Rob