HP Insight Control Software for Linux User Manual

Page 242

Corrective actions

Cause/Symptom

Ensure that older operating systems were added manually
to the /opt/mx/icle/SupportMatrix.xml file.

For information, see the HP Insight Control for Linux
Installation Guide.

Can no longer install older OS after upgrade

Ensure that you removed the following two files:

•

autoInstallComplete_jsp.class

•

autoInstallComplete_jsp.java

Kickstart / AutoYaST install completes but task in SIM
UI still shows that it is running

See the HP Insight Control for Linux Support Matrix for
those servers that require a special initrd file. For more
information and a download web address, see

“Prerequisites to OS installations on managed systems”
(page 87)

Some ProLiant servers require a special initrd file

Support for certain Linux operating systems, such as
RHEL 4.7 and 5.2 and SLES 10 SP2, on newer HP servers
require that you replace the boot RAM disk (the initrd
file) that is supplied with standard the Red Hat Linux or
SUSE Linux distribution.

If you do not replace the initrd file, the installation of
these operating systems fails because the installation
program cannot find the NIC.

Reinstall the OS; make sure that you specify the
mem=60gb

kernel append line option during the OS

installation.

32-bit OS install fails; server has more than 64GB.

An attempt to install a 32-bit OS on a server that has more
than 64GB of memory fails.

Perform the following actions:

If installing to a SAN (Fibre Channel) device, ensure
that the boot order in the BIOS is correctly set to use
the SAN device controller first.

The existing Insight Control for Linux Kickstart and
AutoYaST templates are set up to use autopart and
will likely favor the internal disks. Therefore, if you
want to install the OS on an external disk, you will
need to customize your Kickstart or AutoYaST file
accordingly.

OS install failures on servers with SANs

Ensure that your server's BIOS settings (for example, Boot
Controller Order) that are correct.

Issues with servers that have a Fibre Channel card, use
SAN storage, or both.

Perform the following actions:

If installing to a SAN (Fibre Channel) device, ensure
that the boot order in the BIOS is correctly set to use
the SAN device controller first.

SLES 11 installation hangs at Grub loading… on Fibre
Channel device

242

Troubleshooting