The NetWare 6 installation hangs on a Hot-Plug PCI Server that uses an I2O-compliant Host Bus Adapter
(Last modified: 09Jul2003)
This document (10066676) is provided subject to the disclaimer at the end of this document.
goal
The NetWare 6 installation hangs on a Hot-Plug PCI Server that uses an I2O-compliant Host Bus Adapter
fact
Novell NetWare 6.0
Server Hang
Server Abends
Hot-Plug PCI supported by the PC Server
I20-compliant Host Bus Adapter
Novell's I2OPCI and IOPX NLM modules loaded
Novell's BKSTROSM (Block Storage Manager) NLM module loaded
Novell's NCM (Novell Configuration Manager) module loaded
symptom
At the point where the preliminary file copy ends and the Graphical portion of the install starts the operating system halts and reports:
Error: "ABEND: CPU Hog Detected by Timer".
Prior to the error occurring manual intervention may be necessary, in order to load LAN controller drivers detected by the installation. In normal circumstances these LAN controller drivers will loaded automatically after they have been detected.
change
If the I2O-compliant Host Bus Adapter is removed from the system the installation is successful.
cause
The issue occurs due to a duplicate HIN (Hardware Instance Number) residing on the HWNodeList. This only happens when the I2OPCI and IOPX modules are loaded after the registry key for the InstanceInfo has been cleared.
The registry key gets cleared during the Installation process for upgrade issues. When NCM loads it issues a GetNextHin call and ends up in an endless loop trying to get the next HIN, which is the same as the previous HIN. It is this loop that eventually causes the ABEND to occur.
fix
There are currently two ways to solve this problem.
1. Force the installation so that it does not load NCM.NLM
To stop NCM loading during the installation use the following procedure:
a. Create a directory called C:\NWUPDATE on the servers bootable drive.
b. In this directory create a zero-byte 'dummy' file called NCM.NLM.
- Use the DOS command "COPY CON NCM.NLM".
- Close and write the file using 'CTRL-Z'
c. Re-start the installation.
d. The installation will automatically load the dummy NCM file in preference to the real NCM located on the NetWare 6 CD. Because the file is zero-bytes NCM will not get loaded.
2. Manually unload NCM.NLM during the installation
To unload NCM.NLM during the actual installation use the following procedure:
a. Start the installation as normal.
b. Select a 'Custom Install'
c. After a hardware detect process the will stop on the 'Device Driver' screen. This screen shows the detected Platform Support Module, HotPlug Support Module, and Storage Adapters.
d. Before continuing switch to the System Console screen using the CTRL-ESC or ALT-ESC control key sequences.
e. Unload NCM.NLM ("unload NCM").
f. Switch back to the 'Device Driver' screen and continue.
g. The installation will now continue normally.
INFORMATION ONLY
When Novell release Support Pack 1 for NetWare 6 there will be a full fix to this issue. This fix will be released in the form of a new NBI.NLM (Novell Bus Interface). To implement this fix for any new NetWare 6 server installation use the following procedure:
a. Create a directory called C:\NWUPDATE on the servers bootable drive.
b. Copy NBI.NLM from the \STARTUP directory on the Support Pack to C:\NWUPDATE.
c. Start the installation.
d. The new NBI.NLM will be loaded in preference to the one located on the NetWare 6 CD.
e. After the installation has been completed please install Support Pack 1 immediately.
document
Document Title: | The NetWare 6 installation hangs on a Hot-Plug PCI Server that uses an I2O-compliant Host Bus Adapter |
Document ID: | 10066676 |
Solution ID: | NOVL65706 |
Creation Date: | 10Dec2001 |
Modified Date: | 09Jul2003 |
Novell Product Class: | NetWare |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.