1833599 Members
3533 Online
110061 Solutions
New Discussion

tape driver

 
SOLVED
Go to solution
HDgio
Regular Advisor

tape driver

i have a dd3 instal on I70 server
I want use de st command for chech the tape but is impossible because the driver installed is tape2 and not stape.
I come modify that
8 REPLIES 8
Stefan Farrelly
Honored Contributor

Re: tape driver

You can use the mt command to change/eject the tape; mt -t /dev/rmt/Xm offline
Im from Palmerston North, New Zealand, but somehow ended up in London...
Pete Randall
Outstanding Contributor

Re: tape driver

You'll need to use the mt command: "mt -f /dev/rmt/Xmn status"


Pete

Pete
HDgio
Regular Advisor

Re: tape driver

is OK for a mt command
but can i use st whith a tape 2 driver ?
Stefan Farrelly
Honored Contributor

Re: tape driver

No, I dont believe you can. st is really only used on robotic tape libraries - DLT/DDS autoloaders and for these you need the scsi-pass through driver loaded in to the kernel (scsi_ctl)
Im from Palmerston North, New Zealand, but somehow ended up in London...
HDgio
Regular Advisor

Re: tape driver

dear friends
I have another identical dds3 installed on L1000 server and the kernel it recognizes stape.
The only differents is the hardware of server, the controller and HP-UX installed at 32 bit for a I70 and 64 for a Lclass.

I have used the command stcheckconf because
I thought was this the problem, but in the Lclass machine the configuration of the shared tape is not applied and the kernel know it how stape
Stefan Farrelly
Honored Contributor
Solution

Re: tape driver

tape2 applies to the old HP-PB bus type - on K-class, G/H/I etc. The stape driver applies to all HSC/PCI (new). Ive got a K-class with DLT drives on HP-PB (tape2) and HSC (stape) and st does not work on the tape2 DLT, I get;

> st -f /dev/rmt/c5t3d0BEST -s
st: invalid device file

But on the stape connected DLT I get;

> st -f /dev/rmt/1m -s
Device not ready

It looks like its simply not designed to work on the tape2 driver, sorry.
Im from Palmerston North, New Zealand, but somehow ended up in London...
HDgio
Regular Advisor

Re: tape driver

I don't remember.
The HSC port is only present in the K class
Robert DJ
Frequent Advisor

Re: tape driver

Hi,

Can you change the kernel, if yes let me know i shall give a procedure to carry through.

Take a complete backup before u start the procedure. This can help u in making the SCSI pass through drivers staple

this is on among the procedures, please run through this. If applicable change the required parameters and values for your tape library.

The Procedure is as below,

1. Verify that the unit has a SCSI interface compatible with the SCSI controller that is installed.

2. Determine the availability of SCSI Ids. use ioscan -f

3. Each SCSI bus must have a unique SCSI Id. Find out whether the Id is matched to one assigned.

4. Check out to configure using the utility of the backup, and set the tape library to SCSI.

5. try going to build area - cd /stand/build.

6. Create a system file from the existing kernel.

/usr/lbin/sysadm/system_prep -s system

7. check if the stape driver is already configured into your system. the stape sriver used for the DLT drivers can checked by -

#grep stape system

8. If no "stape" line printed, add a line to the "SCSI drivers" area of the system file (/stand/build/system)

stape

9.check if sctl SCSI pass-through driver is already confgiured into your current kernel.

#grep sctl system

10. If no "sctl" line printer, add a line to the "SCSI drivers" area of the system file (/stand/build/system)

sctl

A driver statement is needed since the system can't autoconfigure the SCSI pass-through driver.

11. Append the driver lines to the system file

driver sctl

Note : = Complete hardware path of derised device from ioscan

e.g - driver 8/4.6.0 sctl


12. save the old system file

mv /stand/system /stand/system.old

13. Build a new kernel

/usr/sbin/mk_kernel

14. Verify the pass-through driver has been built into the new kernel.

what ./vmunix_test | grep scsi_ctl

15. Save the old kernel

mv /stand/vmunix /stand/vmunix.old

16. Move the new kernel to the current one :

mv ./vmunix_test /stand/vmunix

17. Boot the system

/usr/sbin/shutdown -r 0

18. Once restarted

verrify using "ioscan -f"

19. Determine the major number for the SCSI pass-through driver.

lsdev -d sctl

The O/p might be,

Character Block Driver Class
203 -1 sctl ctl


20. Create the special device file to access the scsi_ctl perpheral

/usr/sbin/mknod /dev/<> c

- name of the special device file
- character major number (from lsdev cmd)
- minor number in the format 0xIITL00

II - 2 digit card instance number of "ext_bus" entry
T - target SCSI ID number (SCSI ID)
L - Lun number (SCSI LUN)
00 - Reserved fields, must be zero

E.g : /usr/sbin/mknod /dev/rmt/lxb c 203 0x006000

21. Type "ioscan -fd sctl"

Check whether the driver is configured.

22. Complie the scsi i/o test program

cc /usr/contrib/src/scsi_io.c -o /usr/contrib/bin/scsi_io

23. Run SCSI i/o test program

/usr/contrib/bin/scsi_io /dev/rmt/lxb

The display should some what similar to this,

OVERLANDLXB 032322-Oct-97

Thanx & Regards,

Roby
Robert DJ