HP Insight Control Software for Linux User Manual

Page 228

Corrective actions

Cause/Symptom

Verify that the OS exists in the Insight Control for Linux
repository.

The selected OS has been deleted from the Insight Control
for Linux repository.

Perform the following actions:

The proper files were not copied from the installation media
into the appropriate /opt/repository/os
subdirectories.

•

Copy the proper OS files into the appropriate /opt/
repository

subdirectories.

•

Verify that the correct subdirectories were created in
the appropriate /opt/repository subdirectory, if
required (SLES only, CD1, CD2, DVD, and so on).

Correct the installation configuration file and copy it to the
appropriate /opt/repository subdirectory.

The user-edited installation configuration file was invalid.
(RHEL Kickstart and SLES AutoYaST installation only)

For the corrective action, see

Section 25.20 (page 236)

The target server has lost association with its management
processor.

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

Can no longer install older OS after upgrade

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

Ensure that you removed the following two files:

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

•

autoInstallComplete_jsp.class

•

autoInstallComplete_jsp.java

See the HP Insight Control for Linux Support Matrix for
those servers that require a customized initrd file. For

Some ProLiant servers require a special initrd file

Support for certain Linux operating systems, such as RHEL
4.7, on newer HP servers require that you replace the boot more information and a download web address, see

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

RAM disk (the initrd file) that is supplied with standard
the Red Hat Linux or SUSE Linux distribution with a
customized initrd file provided by HP.

If you do not replace the initrd file, installing 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:

OS install failures on servers with SANs

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 Insight Control for Linux Kickstart and AutoYaST
templates are set up to use autopart and thus favor
the internal disks. Therefore, if you want to install the
OS on an external disk, you must customize your
Kickstart or AutoYaST file accordingly.

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:

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

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.

228 Troubleshooting