topic Re: Tape drive error. in Operating System - HP-UX

Tape drive error.

Jeffrey F. Goldsmith — Mon, 14 Nov 2005 13:02:09 GMT

Over the weekend I had to down my server (L2000) and move it to another rack. When I powered the server up I found that one of my tape libraries (SureStore DLT Autoloader 1/9 LVDS (C7745NB)) wasn’t acting correctly. I have two tape libraries connected to my server via a PCI FWD SCSI-2 card (A4800A). The server has HPUX 11.0.

When I do an ioscan –fnC tape all the tape drives show up. Then when I go into Data Protector and check the second tape library and look at the tape drive it shows that it wants to use the same drive that the other tape library is using.

What do I need to do to fix this problem?

Re: Tape drive error.

Steven E. Protter — Mon, 14 Nov 2005 13:19:46 GMT

Hello Jeffery,

I would suggest seeing if everything is properly terminated and replacing the scsi cable.

Perhaps while moving the server the scsi id of something got inadvertantly changed. Check that there is no conflict.

Might be helpful if we saw your ioscan output too.

SEP

Re: Tape drive error.

A. Clay Stephenson — Mon, 14 Nov 2005 13:37:03 GMT

You will probably need to go into the DP Drives setup under the Library and change the "SCSI address or filename of data drive" value. You may also need to change the robot device node as well. This is rather surprising if you simply powered off the server and physically moved it. The first thing that I would suspect is that you swapped some of the cables. I'm sure that you did an ioscan -fn before and after the move so that you could easily resolve any problems. I'm also sure that you already had all of your SCSI cables labeled as a matter of course so that confusion or miscabling could never occur. I am right about these assumptions, aren't I?

Re: Tape drive error.

Jeffrey F. Goldsmith — Mon, 14 Nov 2005 13:37:58 GMT

Here is the ioscan -fnC tape:

root: /home/root ==> ioscan -fnC tape
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 4 0/0/1/0.2.0 stape CLAIMED DEVICE HP C1537A
/dev/rmt/4m /dev/rmt/c0t2d0BESTn
/dev/rmt/4mb /dev/rmt/c0t2d0BESTnb
/dev/rmt/4mn /dev/rmt/c0t2d0DDS
/dev/rmt/4mnb /dev/rmt/c0t2d0DDSb
/dev/rmt/c0t2d0BEST /dev/rmt/c0t2d0DDSn
/dev/rmt/c0t2d0BESTb /dev/rmt/c0t2d0DDSnb
tape 3 0/0/1/0.3.0 stape CLAIMED DEVICE HP C1537A
/dev/rmt/3m /dev/rmt/c0t3d0BESTn
/dev/rmt/3mb /dev/rmt/c0t3d0BESTnb
/dev/rmt/3mn /dev/rmt/c0t3d0DDS
/dev/rmt/3mnb /dev/rmt/c0t3d0DDSb
/dev/rmt/c0t3d0BEST /dev/rmt/c0t3d0DDSn
/dev/rmt/c0t3d0BESTb /dev/rmt/c0t3d0DDSnb
tape 1 0/0/1/0.4.0 stape CLAIMED DEVICE HP C1557A
/dev/rmt/1m /dev/rmt/c0t4d0BESTn
/dev/rmt/1mb /dev/rmt/c0t4d0BESTnb
/dev/rmt/1mn /dev/rmt/c0t4d0DDS
/dev/rmt/1mnb /dev/rmt/c0t4d0DDSb
/dev/rmt/c0t4d0BEST /dev/rmt/c0t4d0DDSn
/dev/rmt/c0t4d0BESTb /dev/rmt/c0t4d0DDSnb
tape 2 0/5/0/0.1.0 stape CLAIMED DEVICE QUANTUM DLT8000
/dev/rmt/2m /dev/rmt/c6t1d0BEST
/dev/rmt/2mb /dev/rmt/c6t1d0BESTb
/dev/rmt/2mn /dev/rmt/c6t1d0BESTn
/dev/rmt/2mnb /dev/rmt/c6t1d0BESTnb
tape 0 0/5/0/1.1.0 stape CLAIMED DEVICE QUANTUM DLT8000
/dev/rmt/c7t1d0BEST /dev/rmt/c7t1d0BESTn
/dev/rmt/c7t1d0BESTb /dev/rmt/c7t1d0BESTnb

Here is the info from the ioscan:
0/5 ba Local PCI Bus Adapter (782)
0/5/0/0 ext_bus SCSI C896 Ultra2 Wide LVD
0/5/0/0.0 target
0/5/0/0.0.0 autoch HP C7145-8000
0/5/0/0.1 target
0/5/0/0.1.0 tape QUANTUM DLT8000
0/5/0/0.7 target
0/5/0/0.7.0 ctl Initiator
0/5/0/1 ext_bus SCSI C896 Ultra2 Wide LVD
0/5/0/1.0 target
0/5/0/1.0.0 autoch HP C7145-8000
0/5/0/1.1 target
0/5/0/1.1.0 tape QUANTUM DLT8000
0/5/0/1.7 target
0/5/0/1.7.0 ctl Initiator

Re: Tape drive error.

Jeffrey F. Goldsmith — Mon, 14 Nov 2005 13:44:39 GMT

Clay,

Yes, I do have all my cables marked and I double checked them to make sure that I connected everything with the correct cables. As for these two tape libraries, they are both on the same SCSI card as it is a duel port card. There is one cable from each tape library to a SCSI port on the card.

Also, I did an ioscan before and after and they look the same. When I go into Data Protector and look at the tape drives of both the libraries they both see to want to use the same driver. I didnt change the one that was incorrect and started a test backup and it failed because it wanted to use the drive for the first library.

Jeff

Re: Tape drive error.

A. Clay Stephenson — Mon, 14 Nov 2005 13:51:52 GMT

Okay. Now post the output of "omnicellinfo -dev -detail".

Re: Tape drive error.

Jeffrey F. Goldsmith — Mon, 14 Nov 2005 13:58:16 GMT

Here it is. Picker_1 and Picker_2 are the two tape libraries connected to my server that I am having trouble with.

root: / ==> /opt/omni/bin/omnicellinfo -dev -detail
==============================================================================
NAME "AC_DLT"
DESCRIPTION "DLT Library at Animal Control"
HOST fnsbac1
POLICY SCSI-II
TYPE DLT
POOL "AC_DLT_Monthly"
LIBRARY "AC_DLT"
CLEANME
DRIVES
"Tape1:0:4:0C"
"1"
==============================================================================
==============================================================================
NAME "Diomede DDS3"
DESCRIPTION "Single DDS3 tape drive on Diomede"
HOST diomede.net1.fnsb
POLICY Standalone
TYPE DDS
POOL "Default DDS"
CLEANME
DRIVES
"/dev/rmt/c0t2d0BESTn"
==============================================================================
==============================================================================
NAME "MAINT_SDLT"
DESCRIPTION ""
HOST pwmaint1
POLICY SCSI-II
TYPE SuperDLT
POOL "MAINT_SDLT_Monthly"
LIBRARY "MAINT_SDLT"
DRIVES
"Tape1:0:4:0C"
"1"
==============================================================================
==============================================================================
NAME "NWL_1"
DESCRIPTION "DDS4 internal tape on nwlib1"
HOST nwlib1
POLICY Standalone
TYPE DDS
POOL "NWL_DDS_Monthly"
DRIVES
"Tape0:0:2:0N"
==============================================================================
==============================================================================
NAME "NWLsdlt"
DESCRIPTION "Overland SDLT drive"
HOST bookbarn
POLICY SCSI-II
TYPE SuperDLT
POOL "NWL_SDLT_Monthly"
LIBRARY "NWL_SDLT"
DRIVES
"Tape0:0:4:0C"
"1"
==============================================================================
==============================================================================
NAME "Picker_2"
DESCRIPTION ""
HOST diomede.net1.fnsb
POLICY SCSI-II
TYPE DLT
POOL "BAC_DLT_Monthly"
LIBRARY "Picker_2"
DRIVES
"/dev/rmt/c7t1d0BEST"
"2"
SANSTABLEADDR
DEVSERIAL ""
==============================================================================
==============================================================================
NAME "Picker_4"
DESCRIPTION "DLT320"
HOST nwlapp
POLICY SCSI-II
TYPE DLT
POOL "Default DLT"
LIBRARY "NWL_DLT"
CONCURRENCY 3
CLEANME
DRIVES
"scsi2:0:4:0C"
"1"
==============================================================================
==============================================================================
NAME "SW_SDLT"
DESCRIPTION ""
HOST landfill
POLICY SCSI-II
TYPE SuperDLT
POOL "SW_SDLT_Monthly"
LIBRARY "SW_SDLT"
DRIVES
"Tape1:0:4:0C"
"1"
DEVSERIAL ""
==============================================================================
==============================================================================
NAME "Tran_quantum8000"
DESCRIPTION "DLT tape drive in Transit exchanger"
HOST transit.net1.fnsb
POLICY SCSI-II
TYPE DLT
POOL "TRAN_DLT_Daily"
LIBRARY "TRANSIT_DLT"
DRIVES
"scsi3:0:4:0C"
"1"
SANSTABLEADDR
DEVSERIAL "RBD28P0016"
==============================================================================
==============================================================================
NAME "picker_1"
DESCRIPTION "DLT_1"
HOST diomede.net1.fnsb
POLICY SCSI-II
TYPE DLT
POOL "BAC_DLT_Weekly"
LIBRARY "Picker_1"
CONCURRENCY 5
CLEANME
DRIVES
"/dev/rmt/c6t1d0BESTn"
"1"
SANSTABLEADDR
DEVSERIAL ""
==============================================================================
==============================================================================
NAME "picker_3"
DESCRIPTION "DDS3 Autochanger (1M)"
HOST diomede
POLICY SCSI-II
TYPE DDS
POOL "Default DDS"
LIBRARY "Picker_3"
CLEANME
DRIVES
"/dev/rmt/c0t4d0BEST"
"1"
==============================================================================
root: / ==>

Re: Tape drive error.

Andrew Rutter — Mon, 14 Nov 2005 15:34:21 GMT

hi, two things to point out

1, you say they where connected to an A4800A scsi card initially, this is a single port FWD i/f
Your posted ioscan shows you are now connected to a dual port LVD i/f?

2, under this device

tape 0 0/5/0/1.1.0 stape CLAIMED DEVICE QUANTUM DLT8000
/dev/rmt/c7t1d0BEST /dev/rmt/c7t1d0BESTn
/dev/rmt/c7t1d0BESTb /dev/rmt/c7t1d0BESTnb

you are missing the first device files probably 0m/0mn ect as you seen to have 1-4 on the other devices.

Try to recreate these missing device files and then rescan for the tape devices in DP.

Andy

Re: Tape drive error.

Jeffrey F. Goldsmith — Mon, 14 Nov 2005 15:51:29 GMT

Andrew,

You are correct about the SCSI card. I had looked at my contract and saw two SCSI cards listed and picked one.
The two tape devices use the same SCSI card as it has two SCSI ports.
As for the tape device that doesnt have the /dev/rmt/2m when I setup this tape device last year, with the help of HP tech. support, this is the way it showed up. Couldnt get the other settings.

Maybe I should delete the device and start over. Before I do that I will have to search my notes to get the proper steps of how to do this.

jeff

Re: Tape drive error.

Jeffrey F. Goldsmith — Mon, 14 Nov 2005 17:45:58 GMT

I cant find my instructions on how I setup the tape drives and have spent the past hour searching ITRC website for the steps.

Can someone give me the steps that I need? Do I have to remove the tape and reinstall it?

Re: Tape drive error.

Andrew Rutter — Tue, 15 Nov 2005 04:03:26 GMT

hi geoff,

If you want to remove the device files for the tape drive
#rmsf -H 0/5/0/1.1.0 (hardware path of device)

Then do a full ioscan
#ioscan
and a tape ioscan
#ioscan -funC tape
Then recreate them with
#insf -H 0/5/0/1.1.0 (hardware path of device)

Then full ioscan to rescan system
#ioscan
#ioscan -funC tape

should now list the full device files

Not sure about how your DP is set up though, you amy need to change things if the device files generated a different instance number

Andy

Re: Tape drive error.

Jeffrey F. Goldsmith — Mon, 21 Nov 2005 13:40:41 GMT

My thanks to all that helped me with this call. I was able to get my tape device to start working correctly again after removing the devices. There was one thing that I needed to do after removing the tape device. That was to remove the special files in /dev/rmt for that device. Once they were deleated I was able to get new special files installed for the tape drive.