Unregistered hardware (TL 891, TZ89)

[Jäger Helmut]

I have the following problem:
Tru64 Unix 5.1B, AS4100
On my installed system I cannot mount the tapes.
With: "hwmgr -show scsi" I can see this:
SCSI DEVICE DEVICE DRIVER NUM DEVICE FIRST
HWID: DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH
-------------------------------------------------------------------------
52: 0 blagussb cdrom none 0 1 cdrom0 [0/4/0]
57: 1 blagussb changer none 0 1 (null)
58: 2 blagussb tape none 0 1 (null)
59: 3 blagussb tape none 0 1 (null)

When I do the following:
"hwmgr -view devices"
I cannot see the tape devices (HW-ID's 57,58,59):
HWID: Device Name Mfg Model Location
------------------------------------------------------------------------------
5: /dev/dmapi/dmapi
6: /dev/scp_scsi
7: /dev/kevm
18: /dev/cport/scp0 SWXCR xcr0
19: /dev/disk/dsk0c SWXCR ctlr-0-unit-0
20: /dev/disk/dsk1c SWXCR ctlr-0-unit-1
45: /dev/disk/floppy0c 3.5in floppy fdi0-unit-0
52: /dev/disk/cdrom0c PIONEER CD-ROM DR-U06S bus-0-targ-4-lun-0
53: /dev/random
54: /dev/urandom
67: /dev/disk/dsk2c SWXCR ctlr-0-unit-2
68: /dev/disk/dsk3c SWXCR ctlr-0-unit-3

A command "hwmgr -scan components" gives no change.

With "hwmgr -show components -nregistered" I see, that the tape devices are not registered.
Why????

"hwmgr -locate component -id 57" (or 58, 59) gives also no change to me.

Who can help me?
Thanks for your advice!!

[Johan Brusche]

When were the tapes last seen on the system ?
Any events int eventlog or binary.errlog that indicates HW problems with the tapes and changer ? Where they visible in console mode ?(Are they switched on, is the SCSI controller still functional, is the SCSI cable properly seated.) etc...
Things to try:

hwmgr scan scsi
dsfmgr -vVF
dsfmgr -VK

Rgds,
__ Johan ./

[Jäger Helmut]

As you can see in my mail before, I can see the devices under "hwmgr -show scsi", so I think "hwmgr -scan scsi" takes no result.

I did also dsfmgr as you mentioned before!!

I can see the SCSI-Controller and the tape devices from the boot prompt (sho device).

It is very strange!!!

I applied the TL891 and the SCSI-Controller after I have installed the Unix-System.
I also built a new kernel, but no effect!!

In the logs I couldn't find some tips to resolve my problems!!

Kind regards

[Vladimir Fabecic]

That means tape devices were seen once. And not now!
What SCSI controller did you add?
What patches and NHD are installed?
And devices are not seen even when booting genvmunix?

[Jäger Helmut]

But why are the tape devices were seen only once and not now?
Because when I did add the TL891 I also added the SCSI-Controller (they were bought at the same time). And why can I see it on the boot-prompt (sho device)?

My Unix-Version:
# uname -a
OSF1 blagussb V5.1 2650 alpha

Patches installed on the system came from following software kits:
------------------------------------------------------------------

- T64V51BB25AS0004-20040616 IOS540
- T64V51BB25AS0004-20040616 OSF540

Kind regards
Helmut J.

[Jäger Helmut]

In addition:

I found this with the command
"strings /vmunix | grep 'tape'":

cam_tape
cam_tape
cam_tape - unable to register callback (status %d)
cam_tape - unable to register callback (status %d)
ctape_init
ctape_init(): registration failed
ctape_open: SCSI_PROTOCOL not valid!
Unable to register tape: %s
Unable to register tape: %s
ctape_online
ctape_strategy
ctape_strategy: READ case and density info not valid.
Blocking factor of tape is %D
ctape_ioctl
ctape_ioctl: SCSI_PROTOCOL not valid!
ctape_done
ctape_done: No CCMN_SPECIFIC structure
ctape_orphan_done
ctape_orphan_done: No pdrv structure
.............................

Probably this can give you some hint!!

Kind regards
Helmut J.

[Vladimir Fabecic]

Please check SCSI cables and termination, expecialy SCSI terminator. Once I had problem caused by contact on SCSI terminator. Devices were seen in console, but made problems under OS.

[Han Pilmeyer]

Those are just potential kernel messages containing the string "tape". It doesn't mean that you saw any of those.

If you say you can see the device with "hwmgr -show scsi", then I would do a "hwmgr -show scsi -full". Then if there are paths listed, I would test those with the "tur" command in "scu" to see whether the tapes are actually working.

You could try deleting the devices from the hardware database using "hwmgr -del scsi -did ". Then you could try scanning for the devices again using "hwmgr -scan comp -cluster". While doing this, I would run a "evmwatch -A" command in order to see all messages.

This is very curious. I would be interested in seeing the results of these steps.

[Jäger Helmut_1]

Now I deleted the scsi-id's 57,58 and 59 and after a "hwmgr -scan scsi" no ID's appear!!!
But on my boot-prompt I can see the devices!!

What to do???

[Vladimir Fabecic]

In that case that can be a kernel (driver) problem. What SCSI HBA is serving these devices? Did you install NHD 7?
Is there any difference when you boot with "genvmunix"?

[Jäger Helmut_1]

Until now I didn't boot genvmunix, but I will do it on Monday!!
What is NHD 7????
I found this in kern.log:
Nov 4 11:14:35 blagussb vmunix: Driver_support: Module pza failed to load. status:22
Can this be in conjunction with my problem?

Thanks!!

[Han Pilmeyer]

NHD7 is the New Hardware Delivery CD number 7. You would use this if you need to install on a system using devices that were not supported by V5.1A or V5.1B when it first shipped. That's not what's happening in your case.

cam_pza is the DEC KZPSA driver. I assumes that your tapes are connected to the this PCI FWD SCSI adapter, i.e. the KZPSA? That would certainly explain why you can't get to the tapes from Tru64 UNIX.

Can't think of a reason why loading that module would fail. So booting from a genvmunix and building a new kernel seems like a good next step.

You could try loading it manually first and hope that it would display a more elaborate error message. Something perhaps like:
sysconfig -c cam_pza
sysconfig -s | grep cam

[Vladimir Fabecic]

NHD is "New Hardware Delivery". This is kernel device drivers support for some hardware nor included in original OS distribution. You got this CD with OS distributions. Maybe you will not need it, but should install it.
Message could be in conjunction with your problem, but not sure since you did not say what HBA are you using.
What you should do is:
>>> boot -file genvmunix
then:
# doconfig (without any attributes)
See if your devices are seen.

[Jäger Helmut_1]

Thank you for your help!!
When I did >>>>boot -file genvmunix
and then
# doconfig
it really worked!!!
I was surprised, because before I often did build a new kernel with doconfig (but without genvmunix) and it never gave me success.
What's the difference between booting normally or with genvmunix???
But it doesn't matter, now it works and I'm happy!!

Helmut Jaeger

[Han Pilmeyer]

genvmunix is a kernel that has support for all supported devices. So if you use that kernel, it recognizes all devices and builds a config file for all devices it found on the system.