2 custom os installations, 3 capturing linux images – HP Insight Control Software for Linux User Manual
Page 231
Corrective actions
Cause/Symptom
data contained on the disk prevents the OS's installer from
properly configuring the disk. Although the symptoms can
•
Try installing a Linux OS from a different vendor, only
to reformat the disk drive.
vary, they include error messages and instances of
installations hanging on reboot.
•
Boot the system to the Insight Control for Linux RAM disk
with the Diagnose
→Boot to Linux Rescue Mode... tool,
then use the dd command to write zeroes to the master
boot record and partition table, as follows:
# dd if=/dev/zero of=/dev/disk \
bs=16384 count=1
Where /dev/disk is the disk device.
If unsuccessful, zero out the entire disk with the following
command:
# dd if=/dev/zero of=/dev/disk
Reinstall the operating system with the following kernel
append line parameter:
Issue installing RHEL 5.5 on BL460c G7 and BL490c G7
Bladeservers (x86_64 architecture)
acpi=off
See the entry for Bare metal discovery returns "There are
no MAC addresses registered for this system." in
“Troubleshooting discovery problems” (page 213)
.
Capture operation returns "There are no MAC addresses
registered for this system."
25.15.2 Custom OS installations
Corrective actions
Cause/Symptom
Select an OS version that is compatible with the server
hardware architecture.
The selected OS is incompatible with the server hardware.
Correct the “kernel append” line and rerun the tool.
The selected OS does not support network based
installations.
Verify that the kernel and initrd file names as used in
the repository.
The kernel or initrd (RAM disk) names are not correct.
Verify that the configuration file is accessible over the
network from the target managed system and verify the
proper kernel append line syntax.
The installation configuration file could not be accessed at
the location specified on the kernel append line.
Copy the correct boot image and RAM disk files into the
appropriate /opt/repository subdirectory.
The correct boot image was not copied into the appropriate
/opt/repository/boot subdirectory.
Correct the installation configuration file and copy it to the
appropriate /opt/repository subdirectory.
The user-edited installation configuration file was invalid.
Ensure that the OS exists in the Insight Control for Linux
repository.
The selected OS has been deleted from the Insight Control
for Linux repository.
Copy the proper OS files into the appropriate /opt/
repository
subdirectories.
The proper files were not copied from the installation media
into the appropriate /opt/repository/custom
subdirectories
For the corrective action, see
The target server has lost association with its management
processor.
25.15.3 Capturing Linux images
Corrective actions
Cause/Symptom
Perform the appropriate action:
The CMS disk partition with /opt/repository is full.
•
Create a new disk partition with more space for /opt/
repository
on the CMS.
25.15 Troubleshooting OS installation and image deployment problems
231