IBM atdd LTO Tape device driver

[Alan Casey]

Hi,

I have atdd 1.15.0.10 installed on HP-UX 11.0
It has worked fine for 2 years but I now have a problem.

ioscan shows the paths to the tapes( 2 of them) an UNKNOWN and UNCLAIMED which should not be the case.

Is was showing as:
target 14 0/8/0/0.97.11.255.14.8 tgt CLAIMED DEVICE
tape 2 0/8/0/0.97.11.255.14.8.0 atdd CLAIMED DEVICE IBM
ULT3580-TD2
/dev/rmt/2m
/dev/rmt/2mb
/dev/rmt/2mn
/dev/rmt/2mnb

Its now showing as:

unknown 14 0/8/0/0.97.11.255.14.8.0 atdd UNCLAIMED UNKNOWN IBM U
LT3580-TD2
unknown 15 0/8/0/0.97.11.255.14.8.1 acdd UNCLAIMED UNKNOWN IBM U
LT3583-TL

A recompile of the kernel seems to have caused this to change.

I ran rmsf on the tape HW paths then atdd_claim and this also failed:

image1(root)/opt/atdd/bin> ./atdd_claim
unknown 18 0/8/0/0.97.11.255.14.8.0 atdd UNCLAIMED UNKNOWN IBM
ULT3580-TD2
unknown 19 0/8/0/0.97.11.255.14.8.1 acdd UNCLAIMED UNKNOWN IBM
ULT3583-TL
unknown 20 1/2/0/0.97.7.255.14.4.0 atdd UNCLAIMED UNKNOWN IBM
ULT3580-TD2
unknown 21 1/2/0/0.97.7.255.14.4.1 acdd UNCLAIMED UNKNOWN IBM
ULT3583-TL
#ERROR: unable to determine maj number
#ERROR: unable to determine maj number



Any ideas??

[Peter Godron · Accepted solution]

Alan,
as you have identified the kernel rebuild as a potential cause, why did you recompile the kernel (patch ?)? Can you boot to the previous kernel and check everything works.

[Alan Casey]

I had to recompile the kernel due to problems with our Optical Jukebox, there was a hardware failure on it and when the parts were replaces the H/W paths had changed so I had to edit the system file with these paths and driver info (spt) before recompiling the kernel.

I cant back out of the kernel as this will cause a critical problem, but I guess reinstalling atdd might do the same thing.

[DCE]

Alan

I had a similar issue last year. If I remember correctly, I wound up reoving the original devoce files with rmsf, and re-installing them with insf.

Don't know if this is of any help

[opronin]

could you try:
1) check os drivers:
#lsdev|egrep -e atdd -e stape
2) check your HBA's 0/8/0 and 1/2/0 with fcmsutil
3) power off/on your tapes and re-scan your devices

[Alan Casey]

Ok it does look like this is happening on the OS:##

image1(root)/opt/atdd/bin> lsdev|egrep -e atdd -e stape

205 -1 stape tape
248 -1 atdd unknown unknown

[opronin]

I would advise - reinstall atdd drive and review all your steps how did you rebuild the kernel what you mentioned before... one of your steps is harmful for your existing kernel..

[opronin]

sorry - I proposed "reinstall atdd driver", not drive