This chapter describes known issues and restrictions pertaining to the NHD4 kit, and includes notes on the following areas:
Documentation (Section 2.1)
Patch kit compatibility (Section 2.2)
Full Installation only on DS20L (Section 2.3)
DS20L startup with no IDE disks (Section 2.4)
Shell access during Full Installation (Section 2.5)
Installation messages (Section 2.6)
The files and their layout in the NHD4 kit are updated before production. Subsequently, the listings and messages documented in this manual may differ slightly from what you see on your system. This should have no effect on your installation.
Some listings have a backslash ( \
)
at the end of a line to indicate line continuation.
The backslash character
does not appear in the actual display.
2.2 Patch Kit Compatibility
This section describes issues related to Version 5.1A patch kits and NHD4.
2.2.1 Install Both NHD4 and Patch Kit
When you install NHD4, you also must install the most current Version 5.1A
patch kit before you return your system to production.
It does not matter
which one you install first.
2.3 Full Installation Only on DS20L
You must install the NHD4 kit during a Full Installation of
the operating system on a DS20L system.
The kernel modules to support the
DS20L are included in the NHD4 kit.
2.4 DS20L Startup with No IDE Disks
You may encounter the following behavior when starting up a DS20L system configured with SCSI disks but no IDE disks:
If you power on a DS20L system and it has no IDE disks installed, the IDE controller driver may detect and report a stray interrupt. Subsequent boots without cycling power do not exhibit this behavior. This is a known issue and can be ignored.
If you boot a DS20L system from a SCSI disk and it has no IDE disks installed, the system may report IDE probe errors during the boot process. Boot time may be increased as the system issues bus resets. This is a known issue.
2.5 Shell Acess During Full Installation
If you are installing NHD4 from the New Hardware Delivery CD during a Full Installation and you try to launch a shell window, it will fail. You see the following message in the console window:
Error acquiring pty slave as controlling terminal: Not a typewriter.
Perform the following steps to access the shell:
Exit the Full Installation process to access the shell from the console device.
At the shell prompt, perform the intended actions.
Enter
restart
and press
[Return]
to restart the Full Installation process.
This section describes messages related to installing the NHD4
kit and tells you whether to ignore them or take corrective action.
2.6.1 DS20L Boot Messages
During a DS20L system boot, you may see the following PCI table error message:
PCI device at bus 0, slot 3, function 0 could not be configured: Vendor ID 0x1000, Device ID 0x21, Base class 0x1, Sub class 0x0 Sub-VID 0x14d9 Sub-DID 0x8002 has no matching entry in the PCI option table
You also may see the following unrelated driver error message:
<FDI: FATAL ERROR #174 sra:000000ff dor:000000ff msr:000000ff> fd internal driver error: FDI PROBE FAIL (A,11).
Both of these messages reflect known errors and can be ignored.
2.6.2 DS20L daemon.log Error Messages
After booting a DS20L system, you may see error messages similar to
the following in the
daemon.log
files:
Sep 24 11:28:37 hpsq16 [616]: Initializing the threshold structure Sep 24 11:28:38 hpsq16 [616]: **ERROR svrsys_fru_parse.c line 1264: \ FRU Table TLV tag of 0 is not ISOLATIN1
These messages are generated when there is no FRU table available on
the system, and can be ignored.
2.6.3 Rolling Upgrade Setup Message
During the Setup Stage of a Rolling Upgrade, you may see the following message during tag file creation:
clubase: Entry not found in /cluster/admin/tmp/stanza.stdin.530756
This reflects a known error and can be ignored.
2.6.4 Rolling Upgrade Status Messages
If you check the cluster upgrade status during a Rolling Upgrade, you see output similar to the following example, done after the Setup Stage is complete:
# clu_upgrade -v Retrieving cluster upgrade status. Upgrade Status Stage Status Date setup started: Thu Oct 25 08:59:48 EDT 2002 lead member: 1 patch kit source: /mnt completed: Thu Oct 25 09:05:29 EDT 2002 Member Status Tagged File Status ID Hostname State Rolled Running with On Next Boot 1 member01.site.place.net UP No No No 10 member10.site.place.net UP No Yes Yes 20 member20.site.place.net UP No Yes Yes
This output incorrectly indicates
patch kit source
rather than
nhd kit source
.
The source information (in
this example,
/mnt
) is correct, the label is in error.
2.6.5 AlphaServer 8400 Error Messages
If you are installing NHD4 on an AlphaServer 8400 system that is running Version 5.4 of the console firmware, you may see error messages similar to the following:
*** Error (eia0.0.0.4.0), Bad Checksum on eeprom I82558 setmode failed: pid = 13, config_adap ei1, slot 5, bus 0, hose0 *** Error (eib0.0.0.5.0), Bad Checksum on eeprom I82558 setmode failed: pid = 13, config_adap
These messages will not be displayed after you upgrade your console
firmware to Version 5.5 or higher, and can be ignored.
2.6.6 Patch Kit Installation Error Messages
If you install NHD4 before you install the current Version 5.1A
patch kit, you may see error messages when you install the patch kit.
These
messages indicate that the patch kit cannot install files that already have
been installed with the NHD4 kit and can be ignored.
2.6.7 RIS Setup Error Messages
When you run the
update_ris
utility to install NHD4
into a RIS area, you may see messages similar to the following:
The /usr/var/adm/ris/ris6.alpha area already contains NHD support for the following product: 4 'Tru64 UNIX New Hardware for V5.1A' This product must be deleted from the /usr/var/adm/ris/ris6.alpha area before the new kit can be added. Use the /usr/sbin/ris command to remove the product and then run the update_ris command again.
Use the
ris
utility to remove NHD4 from the
RIS area, and rerun the
update_ris
utility to install NHD4
into the RIS area.
2.6.8 RIS Installation Error Messages
If you are installing NHD4 from a RIS server, you may see messages similar to the following before the system is configured:
The /usr/sbin/versw -setnew command failed. This error is not fatal, and the operating system installation will continue. The following message was received from /usr/sbin/versw -setnew: Failure to set the new version identifier
The kernel that is running at this point includes NHD bits, but NHD support has not yet been loaded or configured on your system. This reflects a known issue and can be ignored.