HP Insight Control Software for Linux - Manual (Page 230)

Corrective actions Cause/Symptom
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 on newer HP
servers require that you replace the boot RAM disk (the
more information and a download web address, see
“Prerequisites to OS installations on managed systems”
(page 92)
.
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
1. 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.
2. 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.
Verify that a proxy is not used to communicate between
the CMS and the managed system. OS Installations fail, cannot connect to managed system
OS Installations hang
Insight Control for Linux does not have proxy server
support; the Insight Control for Linux features do not
communicate through proxy servers, and require direct
network connectivity between the CMS and the managed
systems.
Proxy information can be defined using an environment
variable or various configuration files.
Examine the output of the env command and the contents
of the /etc/wgetrc file to ensure that you do not have
any proxy variables set in your environment that might
interfere with Insight Control for Linux.
Ensure the correct storage device is selected during this
operation by disabling all other storage devices on the Installing an OS on systems with external storage media
might fail
target managed system before installing the OS or
Modern Linux installers might not reliably install the Grub
boot loader to the expected storage device if external
specifying it in the installation configuration file (Kickstart
or AutoYaST file). See the appropriate vendor
storage devices are available on the target managed
system during a non-interactive installation.
documentation for more information on Kickstart and
AutoYaST files.
Use any of the following methods to correct this situation: Installation hangs on boot or generates error message
about disk
•
Power on the system and enter the BIOS Setup utility
(F9). Under the Advanced Settings section, select Restore
Settings/Erase Boot Disk.
When installing a Linux OS on a disk that previously
contained data, there may be circumstances in which the
230 Troubleshooting