My friend has a V120 to which he has attached a DDS-4 tape drive. The 
V120 runs Solaris 10, but there are no device files for the tape (or if 
there are, they are not in  /dev/rmt). I've tried a reboot -r, and using 
defsadm, but neither work. Is there another step necessary ?

I *assume* the tape drive is seen on the SCSI bus. I don't have console 
access, so that is not a certainty, but I'll get that checked later. But 
the tape drive is known to work, and its on a unique SCSI ID, so I 
assume it is seen on the bus. Is there any way of interrogating the bus 
to find out if it seen? I have used cdrecord -scanbus (or similar) 
before, but don't have cdrecord installed. Perhaps there is a better way.

In article <4364adad@212.67.96.135>,
	Dave <nospam@nowhere.com> writes:
> My friend has a V120 to which he has attached a DDS-4 tape drive. The 
> V120 runs Solaris 10, but there are no device files for the tape (or if 
> there are, they are not in  /dev/rmt). I've tried a reboot -r, and using 
> defsadm, but neither work. Is there another step necessary ?

There shouldn't be. If those don't work, it's not being picked up.

> I *assume* the tape drive is seen on the SCSI bus. I don't have console 
> access, so that is not a certainty, but I'll get that checked later. But 
> the tape drive is known to work, and its on a unique SCSI ID, so I 
> assume it is seen on the bus.

Do you know what the SCSI id is?

By default, the Solaris st driver only recognizes targets 0-6. If it's
set to a higher target id you'll need to uncomment the last few lines of
/kernel/drv/st.conf to get it to work.

-- 
-Peter Tribble
L.I.S., University of Hertfordshire - http://www.herts.ac.uk/
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/

Peter Tribble wrote:
> In article <4364adad@212.67.96.135>,
> 	Dave <nospam@nowhere.com> writes:
> 
>>My friend has a V120 to which he has attached a DDS-4 tape drive. The 
>>V120 runs Solaris 10, but there are no device files for the tape (or if 
>>there are, they are not in  /dev/rmt). I've tried a reboot -r, and using 
>>defsadm, but neither work. Is there another step necessary ?

> Do you know what the SCSI id is?
> 
> By default, the Solaris st driver only recognizes targets 0-6. If it's
> set to a higher target id you'll need to uncomment the last few lines of
> /kernel/drv/st.conf to get it to work.
> 

Thanks, that was the problem - it is on SCSI id 10. I edited the file 
you suggested and the device files were created.


dave k