Storage Boards Cleanup
To make it easier to find information about HPE Storage products and solutions, we are doing spring cleaning. This includes consolidation of some older boards, and a simpler structure that more accurately reflects how people use HPE Storage.
Tape Libraries and Drives
cancel
Showing results for 
Search instead for 
Did you mean: 

Driver & Device file for HP LTO 6/60 (Fibre) on HP-UX

Phani_4
Frequent Advisor

Driver & Device file for HP LTO 6/60 (Fibre) on HP-UX

Hi,

We have HP LTO 6/60 Library which was connected to the HP9000 servers over the SAN.

The device file robotic arm was created w.r.t drive "sctl"

Using "mc" command, i could able to manipulate the robotic arm on the library.

But using "uma" utility it is throwing an error as below..

"[Critical] From: UMA@suboz009.eur.gep.ge.com "(unnamed)" Time: 03/24/04 21:11:5
5
[90:59] /dev/picker
Cannot open exchanger control device ([12:1012] Cannot access the file.
System error: [2] No such file or directory"

Device file :
crw-rw-rw- 1 root sys 203 0x0d4000 Mar 24 21:30 /dev/picker

Can somebody please let me know that why the above error is occuring when i use "uma" utility.

Note: I have followed the document which was in the below link..
"http://openview.hp.com/sso/ecare/getsupportdoc?docid=OV-EN010365"

All the tests passed after creating the device file manually..but "uma" utility is getting failed.
2 REPLIES
Kurt Beyers.
Honored Contributor

Re: Driver & Device file for HP LTO 6/60 (Fibre) on HP-UX

Phani,

you should use the driver 'schgr' in the kernel to control the robot arm.

Add it to the kernel (and remove the sctl driver), rebuild the kernel and reboot the server with the new kernel.

Do now a 'ioscan -fnC autoch' to see if the autochanger is claimed and that a device file was created (/dev/rac/c?t?d?).

best regards,
Kurt
Leif Halvarsson_2
Honored Contributor

Re: Driver & Device file for HP LTO 6/60 (Fibre) on HP-UX

Hi,
Your devicefile seems OK, the sctl driver should normally be used. And as the mc command work I would suspect a problem with uma. Try to reinstall the media agent.