topic Re: DLT7000 robotic libray help needed. in Operating System - HP-UX

DLT7000 robotic libray help needed.

Peter A. Berger Jr. — Mon, 09 Jun 2003 20:15:52 GMT

UNIX-newbie here.
I just connected an HP 1/6 DLT-Autoloaded (6 slots, 1 drive) to my RP7410.

I'm trying to make the device file but don't seem to be getting it correct.
ioscan produces:
1/0/10/0.8.0 HW path and device file c5t8d0.

I typed: mknod /dev/rac c 203 0x018000
and then to test I/O I ran:
/opt/omni/lbin/uma -ioctl /dev/rac
but get nothing...just a blinking cursor. I have to Ctrl-C to get my prompt back.
My lsdev -d sctl produces:
Char: 203 Block -1 Driver:sctl and Class:ctl.

Stumped. Any help would be great. Thanks. :)

Re: DLT7000 robotic libray help needed.

Bill Douglass — Mon, 09 Jun 2003 20:22:40 GMT

Can you attach the full ioscan -fnk? I wonder if you have the wrong device selected.

Re: DLT7000 robotic libray help needed.

A. Clay Stephenson — Mon, 09 Jun 2003 20:28:08 GMT

Best Guess: Minor device 0x018000 should be 0x058000

Re: DLT7000 robotic libray help needed.

Michael Tully — Mon, 09 Jun 2003 21:02:45 GMT

The problem is we need to know what the Bus Interface number is ... Please post the full ioscan output as suggested, or use this attached document to get assistance.

Regards
Michael
"When I have trouble spelling, it's called fat finger syndrome"

Re: DLT7000 robotic libray help needed.

Peter A. Berger Jr. — Tue, 10 Jun 2003 10:32:46 GMT

Appreciate the help. Enclosed is the latest IOSCAN dump.

Re: DLT7000 robotic libray help needed.

Zeev Schultz — Tue, 10 Jun 2003 10:50:27 GMT

The doc Michael has attached is a true gold of
HP(UX) libraries configuration.Wish we have more like this one on another issues :)
Anyway ...

In your particular case the picker is here:
unknown -1 1/0/10/0/0.9.0 UNCLAIMED UNKNOWN HP C6280-7000

So just build the /dev/rac with the 0x059000
(ext_bus=5,scsi target=9,lun=0).Continue later
with the manual.

Zeev

Re: DLT7000 robotic libray help needed.

Rita C Workman — Tue, 10 Jun 2003 10:50:43 GMT

The hardware path you mention is the drive...not the robotic arm.

I was just curious...did you load the drivers for the robotic arm. I would guess that the RP5410 is a HSC or PCI card...so you'd probably need the following:

schgr sctl

Do you have these drivers loaded?

Rgrds,
Rita

Re: DLT7000 robotic libray help needed.

Tom Danzig — Tue, 10 Jun 2003 11:52:13 GMT

It appears that the robotic arm is not binding to a driver:

target 18 1/0/10/0/0.9 tgt CLAIMED DEVICE

Make sure you have the schgr driver in your kernel.

Re: DLT7000 robotic libray help needed.

Tom Danzig — Tue, 10 Jun 2003 11:53:41 GMT

Pasted the wrong ioscan line above. Should be:

unknown -1 1/0/10/0/0.9.0 UNCLAIMED UNKNOWN HP C6280-7000

Re: DLT7000 robotic libray help needed.

Bill Douglass — Tue, 10 Jun 2003 12:04:38 GMT

Zeev and Michael are right (nice job, guys).

Delete your /dev/rac and re-create it with

mknod /dev/rac c 203 0x059000

and you should be good to go. Test is with uma to be sure. And let us know if it worked.

Re: DLT7000 robotic libray help needed.

Peter A. Berger Jr. — Tue, 10 Jun 2003 13:31:09 GMT

mknod /dev/rac c 203 0x059000 worked. I can now get into UMA and move the drive/tapes around. You guys UX are excellent.
Now I feel like a newbie moron for trying:
mknod /dev/rac c 203 0x018000. I thought this because I saw 1/0/10/0/0.8.0 as the DLT. How does one know that it should be 0x059000? I don't see any reason for this. Can someone help me understand this (I'm like a sponge...i want to learn how & why...not just how to get passed my issue) thanks a million.

Re: DLT7000 robotic libray help needed.

Zeev Schultz — Tue, 10 Jun 2003 13:44:37 GMT

Peter
The document Michael posted has it all :)
But...
HP as regarding to device files (like /dev/rac)
you created uses 2 special numbers,one called major ,second minor (I allways confuse which one is which :)).Anyway,major number sort of identifies the device driver.Can see major numbers with lsdev.The minor number usually (but not allways) specify device location.Like in your case with 0x050900.This is translated to bus N5,scsi target N9 and scsi lun N0.The device ext_bus in ioscan speaks for bus,so you
do ioscan search for bus N5 (ioscan -fnCext_bus),target N9 speaks for t9 on that bus and lun isn't used here.
Read man 1m mknod for more :)
I hope I put it in readable format :))

Zeev