problem installing tape drives ..

[someone_4]

Hello everyone

I am trying to intall my tape drives and I have an issue with only my 2nd install ..

I plug up the hardware and then run insf -e

on the first server it worked fine . i see the device


Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 0 0/0/1/0.1.0 stape CLAIMED DEVICE HP C1537A
/dev/rmt/0m /dev/rmt/c0t1d0BESTn
/dev/rmt/0mb /dev/rmt/c0t1d0BESTnb
/dev/rmt/0mn /dev/rmt/c0t1d0DDS
/dev/rmt/0mnb /dev/rmt/c0t1d0DDSb
/dev/rmt/c0t1d0BEST /dev/rmt/c0t1d0DDSn
/dev/rmt/c0t1d0BESTb /dev/rmt/c0t1d0DDSnb


now the one i am having problems with is the 2nd one..
i did the same thing as above but it gives me


Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 1 0/0/1/0.0.0 stape CLAIMED DEVICE HP C1537A
/dev/rmt/1m /dev/rmt/c0t0d0BESTn
/dev/rmt/1mb /dev/rmt/c0t0d0BESTnb
/dev/rmt/1mn /dev/rmt/c0t0d0DDS
/dev/rmt/1mnb /dev/rmt/c0t0d0DDSb
/dev/rmt/c0t0d0BEST /dev/rmt/c0t0d0DDSn
/dev/rmt/c0t0d0BESTb /dev/rmt/c0t0d0DDSnb
tape 0 0/0/1/0.1.0 stape NO_HW DEVICE HP C1537A
/dev/rmt/0m /dev/rmt/c0t1d0BESTn
/dev/rmt/0mb /dev/rmt/c0t1d0BESTnb
/dev/rmt/0mn /dev/rmt/c0t1d0DDS
/dev/rmt/0mnb /dev/rmt/c0t1d0DDSb
/dev/rmt/c0t1d0BEST /dev/rmt/c0t1d0DDSn
/dev/rmt/c0t1d0BESTb /dev/rmt/c0t1d0DDSnb


is there a reasn why i am getting a differnt path .. and on the 2nd one hardware not found??

~ Richard

[Sandip Ghosh]

Scsi PATH depends on your SCSI ID. I think in the Second Server when you added first time the SCSI ID was 1 and Second time when you added the SCSI ID is 0. When you added first time it had created the device file with the address 0/0/1/0.1.0 but the second time when you added it created the device file with the hardware add 0/0/1/0.0.0 . Change the SCSI ID to 1. It should solve the prob. Remember to do it in power off condition.

Sandip

[Ashwani Kashyap]

Is there any scsi id conflict on the second machine ?

[Brian M Rawlings]

Richard, maybe some more info would help us:

What are these tapes going into, or connecting up to? On the second one, are there two tapes, or just one? On the second (failing) tape, what is the SCSI ID?

If there is just one tape drive in the second case, then something is confused about SCSI ID. This can happen due to termination (which can be one the drive, or an external terminator, depending on where it's going).

You might try swapping the two tape drives, to prove that one is not just bad.

Please respond, and we'll get you fixed up.

Regards, --bmr

[S.K. Chan]

In addition it's good to clean out "unused" device files with rmsf before you install the drive. That way there would not be any conflict. I would be more specific ..
# insf -H
instead of using "insf -e".

[John Dvorchak]

It looks to me like the drive was functioning enough to pass the ioscan. But looking at the output above, it is not working. I would look at the SCSI termination. If that and the cabling looks good then perhaps the tape drive is really broken. Can you swap it out with the other tape to confirm that it is bad?

[someone_4]

I will switch tape drives and and maybe even try this tape drive on another server. I will keep you guys updated and award points once we got it going ..

~ Richard

[Sridhar Bhaskarla · Accepted solution]

Richard,

For me, it looks like someone changed the scsi id of the tape drive. The path is not changed but the instance due to the fact that the instance was already assigned for the previous scsi id.

You can get rid of the device files using rmsf. But only a reboot will clean up the NO_HW entry in the kernel tables.

You can reset the instance number and get your familiar "0m" device by using ioinit command. Look at ioinit man page.

-Sri

[Michael Tully]

Hi Richard,

I had this problem as well, but I solved with the information in this link.

HTH

Michael

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xb5968cc5e03fd6118fff0090279cd0f9,00.html

[Kim Kendall]

Make sure the driver is loaded...

# Sam
-> Kernel Configuration
-> Drivers
-> [make sure the "stape" is "in" ]
to highlight it
-> Actions/Add Driver
-> Actions/Process New Kernel