Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX 11i Version 1 Installation and Update Guide: HP Servers and Workstations > Appendix B Known Problems and Troubleshooting

Install Known Problems

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

Kernel size is very large” Warning During Cold-Install

During a cold-install, the following warning message may appear in your swagent.log:

WARNING: Kernel size is very large. The kernel may not boot or
may show decreased performance in small memory systems.
Actual kernel size: 33118076 bytes
* Build_Kernel: Complete
* Boot_From_Client_Disk: Begin
* Rebooting machine as expected.

What To Do

Please disregard the above warning, the check for the kernel size limit incorrectly uses the 32MB value instead of the 64MB value supported on HP-UX 11i v1. PHKL_27447 will correctly set the kernel size limit that gets checked during the creation of new HP-UX 11i v1 kernels.

System Console "kthread table full" or "fork failed" Messages

NOTE: This section was modified in the March 2003 release to reflect how the maxusers tunable value varies depending on the type of system you have.

After a successful cold install, the system starts displaying console messages such as kthread table full or fork failed console. These messages are also logged in /var/adm/syslog.log.

This is caused by the maxusers kernel tunable not set at high enough value.

How Do You Know if This Affects You

An example of what you might see is the following message logged onto the system console:

kthread: table is full

You would also see the following message being logged in /var/adm/syslog.log:

Jan 30 09:21:39 sd2600 vmunix: kthread: table is full

The above example demonstrates table is full messages; however, you might see the similar “fork failed” messages.

What To Do

To correct this, increase the maxusers tunable:

  1. Log on as root

  2. Edit /stand/system and add the following value (depending on your system):

    • Large 64-way systems (Superdome): maxusers 400

    • 16-way systems: maxusers 200

    NOTE: Consult your HP Customer Engineer for information and assistance for setting the appropriate values on your system
  3. Run the following commands:

    mk_kernel -v -o /stand/vmunix

    kmupdate

    reboot -r

Kernel Build Fails on 64-bit Install

On J2240 workstations having an SCSI floppy drive, cold-installing 64-bit OS will fail during the kernel build with an “unsatisfied symbols” error.

What To Do

Edit the /stand/system file to delete the floppy driver:

  1. In the shell provided, use vi to edit the /stand/system file:

    vi /stand/system

  2. Delete the line: sflop

  3. Press Cntl D to close the window.

The install process should now rebuild the kernel and complete successfully. The SCSI floppy drive will be non-operational, and is not supported on this system with 64-bit 11i OS.

Known Issues With OE Media Install Tool and Network Depots

The Ignite-UX install tool on the OE media supports the use of network depots. However, network depots must match the media depots for the choices in the install tool to work properly.

The Ignite-UX documentation also explains the setup and use of network depots without using the OE media for each installation. See the following web site for information on the Ignite-UX product:

http://software.hp.com/products/IUX/

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© Hewlett-Packard Development Company, L.P.