DAT72 install problem in AlphaStation XP900 (DS10) with Tru64 4.0F

[Acanthis Support]

Hello,

To replace my dead DDS3 tape drive (TLZ10), I bought an HP DAT72 (Ref.: Q1525A) and a new required Ultra2 LVD SCSI controller (Ref.: 3X-KZPCA-AA). These references are listed by HP to work on my configuration. So in my server, I now have 2 SCSI controllers, the old one on which 2 hard drives are plugged, and the new one on which the DAT72 tape drive is plugged.

I installed them in the server, checking SCSI ID, and they are well detected at the console:
>>> show dev
(...)
pka0.7.0.15.0 PKA0 SCSI Bus ID 7 -> New SCSI card
pkb0.7.0.16.0 PKB0 SCSI Bus ID 7 5.57 -> Old SCSI controller
mka500.5.0.15.0 MKA500 HP C7438A V312 -> DAT72
dkb0.0.0.16.0 DKB0 COMPAQ BB01821AC3 3B05 -> First Hard-Disk
dkb100.1.0.16.0 DKB100 COMPAQ BB018222B8 B016 -> Second Hard-Disk
(...)

>>> show conf
(...)
Bus 00 Slot 15: NCR 53C895
- pka0.7.0.15.0 SCSI Bus ID 7

Bus 00 Slot 16: QLogic ISP10x0
- pkb0.7.0.16.0 SCSI Bus ID 7 5.57
- dkb0.0.0.16.0 COMPAQ BB01821AC3 3B05
- dkb100.1.0.16.0 COMPAQ BB018222B8 B016
(...)

For me everything seems ok at the console.
The latest console firmware is installed (6.8-9)

I then boot the OS (Tru64 4.0F with latest DUPatch Kit 8 BL 22), and try to use the drive, but it doesn't seem detected by the OS:
# mt status
/dev/nrmt0h: No such file or directory

What must I do now ? Create other special device ? How can I troubleshoot (I can't use "HP StorageWorks Library and Tape Tools" to help as my OS is Tru64 4.0F, and this tool only works on 5.x) ?

Thanks a lot for your help !
Michael

[Ralf Puchner]

Check if the tape is supported with your hardware AND software version!

Use the "file" command to check the device file for proper scsi detection. Use the "scu scan edt" command to be sure the scsi devices are seen. Recreate the tape device with MAKEDEV.

But why not using the troubleshooting section within the admin guide explaining in detail how to connect a tape to a machine?

[Acanthis Support]

Hello Ralf,

First, thanks for your help, and sorry for not having replied before.

- Yes, this tape drive is supported both by my hardware (Alphastation DS10/XP900) and software (Tru64 4.0F with DUPatch Kit 8 BL22), as can be seen here:
http://h18002.www1.hp.com/alphaserver/options/asds10/asds10_3r-a4544-aa.html
(I have added a 3X-KZPCA-AA SCSI controller just for this tape drive)

- # file /dev/nrmt0h
/dev/nrmt0h: character special (9/37891)
So it does not seem ok as there is no information about the SCSI device as should be.

- # scu show edt

CAM Equipment Device Table (EDT) Information:

Device: CDR-8435 Bus: 0, Target: 0, Lun: 0, Type: Read-Only Direct Access
Device: BB01821AC3 Bus: 2, Target: 0, Lun: 0, Type: Direct Access
Device: BB018222B8 Bus: 2, Target: 1, Lun: 0, Type: Direct Access

I only see the CDROM and the 2 Hard-Disks but not the DAT tapedrive, so it doesn't seem well detected by the OS.

- I've checked the troubleshooting parts of the admin guide, but it doesn't help as my problem is that the drive is well detected at the console prompt, but not in the OS when booted.
So, I think the hardware is correctly plugged and running, but the OS does not correctly detect it. Have you got some ideas ?

Regards,
Michael

[Michael Schulte zur Sur · Accepted solution]

Michael,

you will have to create a new kernel for the os to detect the new scsi controller.
Boot genvmunix and generate a new kernel.

greetings,

Michael

[Acanthis Support]

Hello Michael (Schulte),

Thanks for your reply, it helped point me in the right direction.
Indeed, the problem was that the SCSI controller was not detected by the OS.

I already built a kernel, but directly from the OS, not from genvmunix, and this is why it didn't work. I didn't know I had to boot from genvmunix to force the re-detection.

So, I first tried to boot from genvmunix, but it crahsed because he changed the device numbers, so he couldn't mount disk partitions :-(

Then, I booted from genvmunix in SINGLE user mode so I can do something. From there I could see that what was before /dev/rz16 was now /dev/rz24 and /dev/rz17 was now /dev/rz25. In fact it changed the SCSI bus number (hard disks were now detected on BUS 3 and not on BUS 2 like before).
Then, I changed the ADVFS domain references to link to the new disk devices, created the new tape device, rebuild the kernel, and rebooted.

Finally it worked ! (tape detected, backup test ok).

So many thanks for having helped me ! :-)

A last question: why booting on genvmunix changed the SCSI bus numbers ? It caused many problems... rather complicated just to add a new tape device !

[Michael Schulte zur Sur]

Hi,

The numbering of the devices are derived from the position of the controller within a pci bus. So, as you inserted a new controller all controllers above were moved in numbers. That caused the problem.

greetings,

Michael

[Acanthis Support]

Ok, I now understand.

I guess this is the kind of design "flaws" of such old hardware (hoping it's easier in 2005 ;-)).

Again, thanks !

[Saju a r s]

Hi ,

I found this topic matching my needs . Can any one please tell me how will i recreate my HP DAT72 HOT PLUG tape drive in my ES45 running 5.1B ?
The device location was /dev/ntape/tape1
But i am unable to make this device .
nrmt0h doesnt work .
saju

[Vladimir Fabecic]

Saju a r s
Please start a new thread and ask question.
By the way, also send output of:
# hwmgr -show scsi