Sun StoreEdge DAT 72 Tape drive
hi all,
We have a Sun StoreEdge DAT 72 Tape drive installed internally in a Sun Blade 2500. When we do a probe-scsi-all from PROM we can see the tape drive but there are no directories created under /dev/rmt ?
We have tried boot -r, devfsadm, drvconfig;devlinks;tapes etc... but the OS (Solaris 9) doesn;t seem to see the tape drive?
Any ideas?
Isn't the driver for this Tape drive bundled with the latest Solaris 9?
If it isn't, where can we download it? Cant seem to find it on sun.com
Many thanks
[544 byte] By [
headachea] at [2007-11-26 23:55:49]
# 1
Just to add to our post above, the tape drive is installed internally, but we also have an external storage (external disk array) that we have connected to the scsi port on the back of the Sun Blade.
Is there any chance that the internal tape drive and external storage could be using the same controller, and hence only one is seen by the OS?
Any help is greatly appreciated.
Kind regards.
# 2
also, prtconf -D shows...
csi, instance #0 (driver name: glm)
disk (driver name: sd)
tape (driver name: st)
sd, instance #0 (driver name: sd)
sd, instance #1 (driver name: sd)
sd, instance #2 (driver name: sd)
sd, instance #3 (driver name: sd)
sd, instance #4 (driver name: sd)
sd, instance #5 (driver name: sd)
sd, instance #6 (driver name: sd)
sd, instance #7 (driver name: sd)
sd, instance #8 (driver name: sd)
sd, instance #9 (driver name: sd)
sd, instance #10 (driver name: sd)
sd, instance #11 (driver name: sd)
sd, instance #12 (driver name: sd)
sd, instance #13 (driver name: sd)
sd, instance #14 (driver name: sd)
scsi, instance #1 (driver name: glm)
disk (driver name: sd)
tape (driver name: st)
so can we assume the tapes driver is loaded?
cheers again
# 3
I have an external Sun StoreEdge DAT 72 connected to a SCSI card (not the built in SCSI) in a V240 running Solaris 9 4/04. It's been awhile since I installed it, but I do not remember the need to add any software.
here's parts of prtconf -D output:
SUNW,Sun-Fire-V240
scsi_vhci, instance #0 (driver name: scsi_vhci)
packages
SUNW,builtin-drivers
deblocker
disk-label
terminal-emulator
dropins
kbd-translator
obp-tftp
SUNW,i2c-ram-device
SUNW,fru-device
SUNW,asr
ufs-file-system
--
pci, instance #2 (driver name: pcisch)
scsi, instance #0 (driver name: glm)
disk (driver name: sd)
tape (driver name: st)
sd, instance #0 (driver name: sd)
sd, instance #1 (driver name: sd)
sd, instance #2 (driver name: sd)
sd, instance #3 (driver name: sd)
sd, instance #4 (driver name: sd)
sd, instance #5 (driver name: sd)
sd, instance #6 (driver name: sd)
sd, instance #7 (driver name: sd)
sd, instance #8 (driver name: sd)
sd, instance #9 (driver name: sd)
sd, instance #10 (driver name: sd)
sd, instance #11 (driver name: sd)
sd, instance #12 (driver name: sd)
sd, instance #13 (driver name: sd)
sd, instance #14 (driver name: sd)
st, instance #0 (driver name: st)
st, instance #1 (driver name: st)
st, instance #2 (driver name: st)
st, instance #3 (driver name: st)
st, instance #4 (driver name: st)
st, instance #5 (driver name: st)
st, instance #6 (driver name: st)
Glen
# 4
Hello,
can you please post the output of probe-scsi-all.
The Blade 2500 uses SCSI for the internal disks (in the backplane) and ATAPI (IDE) for the DVD-ROM.
Judging from the InfoDoc about Recognized Device Paths and the following notes from the SSH page of the DAT72, the internal SCSI controller is only single-channel.
- The Sun Blade 2500 requires a PCI Host Bus Adapter for internal support [... of the DAT72].
- The Sun Blade 2500 PCI Host Bus Adapter to DAT 72 cable is not available from Sun.
There is no connector on the system-board to attach additional internal SCSI devices. If you attached the internal and external DAT to the same SCSI channel, you have to assign different SCSI-IDs. A common choice is ID 5 for the internal and ID 4 for the external tape.
Michael
# 5
hi,For anyone who comes across the problem above we solved it by installing the following packages on the server:SUNWqus, SUNWqusu, SUNWqusux, SUNWqusx and then installed the patch 112706-05 and reboot the system with boot -r.hope this helps....
