Library 2/20

[Marcia Ferreira_2]

Hi guy

how can I extract the driver and class of a HW Path?
ex: I want to extract the class and driver of H/Path: 10/16/4.1.0
spt 0 10/16/4.0.0 spt SCAN DEVICE HP C7200-8000
target 88 10/16/4.1 target SCAN DEVICE
disk 166 10/16/4.1.0 disc3 SCAN UNKNOWN QUANTUM DLT8000

I?ve tried rmsf, but nothing happened ...

thanks

[Michael Tully]

Hi Marcia,

The class of the device is 'tape' and the
driver is 'stape'. You must have 'stape'
loaded into the kernel as a driver. Have
a look at the output of the 'lsdev' command
and you will see the above. You can't use
'rmsf' to do this. Once the correct driver
has been used the devices should be created
automatically. Even if you have to create
devices manually you need to use the 'insf'
or 'mksf' command. You can add this into the
kernel by using SAM or can at the command
line. Let us know if you need further help.

HTH
-Michael

[Marcia Ferreira_2]

Hi Michael

The driver/class stape/tape is already installed in kernel. The problem is: I?ve
2 scsis in my library. The first one is attached to stape/tape, but the second one isn?t. My last msg can show it.
How can I remove the driver to the system attach the driver correctly?

Thanks

[Sanjay_6]

Hi Marcia,

Can you attach your complete ioscan output.

ioscan -fn

Thanks

[Sanjay_6]

Hi Marcia,

Enable the "schgr" driver in the kernel. The "sctl" and "stape" drivers are also required but they should already be enabled in the kernel.

Try it out, might help.

thanks

[Michael Tully]

Hi Marcia,

You could try to this:

ioscan -M driver -H hw_path -I instance
to bind the device manually. Failing that
please post a *full* copy of your ioscan
as 'ioscan -fnk' This will read the
current status out of your kernel.

HTH
-Michael

[Torsten.]

Hi,

I think you connect the DLT 8000 drive to a HP-PB SCSI interface (10/16/...). As far as I know these drives are not supported on these interfaces, only on HSC cards in K-Class servers.

regards,
Torsten

[Marcia Ferreira_2]

Hi Torsten

you?re right. I did a call, and I hope there is an update Firmware to solve the problem.

thanks

Marcia