ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

Proliant ML350. Addressing an Ultrium 215 Tape Drive With SCO Unix

 
Stuart1946
Visitor

Proliant ML350. Addressing an Ultrium 215 Tape Drive With SCO Unix

Hi

 

I have an HP Proliant ML350 running SCO Unix 5.0.7

 

The system has a SCSI board in slot 3 running my disc array with no problems.

 

However I also have an Ultrium 215 tape drive directly attached to a socket on the motherboard. This socket is labelled SCSI 2 (there is also a socket labelled SCSI 1 but this is not in use).

 

Question: How do I address this tape drive in SCO Unix? What is the adaptor id for the motherboard socket?

 

Thanks in anticipation.

2 REPLIES
Stuart1946
Visitor

Re: Proliant ML350. Addressing an Ultrium 215 Tape Drive With SCO Unix

Thanks to anyone reading this. I am making some progress albeit a little slow.

 

In the process of configuring the drive I am being asked to identify the drive type do you think "Genric SCSI Tape Drive" would suffice for an Ultrium 215, or would DAT drive be more accurate?

 

Thanks

Stuart1946
Visitor

Re: Proliant ML350. Addressing an Ultrium 215 Tape Drive With SCO Unix

I hope nobody thinks I've been wasting their time with this but I have managed to resolve the issue and thought I'd post the solution for others with the same problem.

 

As root use

 

sconf -v

 

This will list all the scsi devices on the system;

 

Mine were (my headings):

 

Type    Driver    Adaptor    Bus    ID   Lun

 

Sdsk    ciss           0                  0      0      0

Sdsk    ciss           0                  0      1      0

Sdsk    ciss           0                  0      2      0

Stp       lsil             1                  0      3     0

 

Using mkdev tape, first remove any existing configured tape drives then configure the new drive using the parameters

returned by sconf. I used a gerenic tape drive for the 'type' and this seems to work fine.

 

When I tried to use 1 for the adaptor I was told that it wasn't configured and did I want to update the link kit. I replied 'yes' and that semed to work fine.

 

Relink the kernel etc and reboot.

 

Be cautious using sconf (read the manual entry) use only the -v option.