HP Insight Control for Linux 6.0 Release Notes

• The following items are missing from Section 23.15.1, RHEL and SLES installations:
Corrective actionsCause/Symptom
Install the cpq-cciss driver option from the latest
supported PSP.
cciss: fifo full error on ProLiant ML350 G6 console
This error appears on the console of a ProLiant ML350
G6 installed with RHEL 4 Update 7 or RHEL 5 Update
2.
Ensure the correct storage device is selected during
this operation by disabling all other storage devices on
the target managed system before installing the OS or
specifying it in the installation configuration file
(Kickstart or AutoYaST file). See the appropriate
vendor documentation for more information on
Kickstart and AutoYaST files.
Installing an OS on systems with external storage
media might fail
Modern Linux installers might not reliably install the
Grub boot loader to the expected storage device if
external storage devices are available on the target
managed system during a non-interactive installation.
Use any of the following methods to correct this
situation:
• Power on the system and enter the BIOS Setup
utility (F9). Under the Advanced Settings section,
select Restore Settings/Erase Boot Disk.
• Try installing a Linux OS from a different vendor,
only to reformat the disk drive.
• 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
Installation hangs on boot or generates error message
about disk
When installing a Linux OS on a disk that previously
contained data, there may be circumstances in which
the data contained on the disk prevents the OS's
installer from properly configuring the disk. Although
the symptoms can vary, they include error messages
and instances of installations hanging on reboot.
• The following item is missing from Section 23.15.4, Deploying Linux images:
Corrective actionsCause/Symptom
Capture the multi-partition image, deploy it to a single
partition, capture that image, and then redeploy the
image using the number of required partitions.
Deploying an image with a multiple partition scheme
to another might fail. At times, when a disk has some
number of partitions already on it, and during an image
deployment you specify a different number of
partitions (either more or less) in the partition wizard,
the deployment fails because the partitions are not
sized as they should be.
In this instance, capture the multi-partition image,
deploy it to a single partition, capture that image, then
redeploy the image using the number of required
partitions.
Deployment might fail from one multiple partition
scheme to another multiple partition scheme
At times, when a disk has some number of partitions
already on it, and during an image deployment you
specify a different number of partitions (either more
or less) in the partition wizard, the deployment fails
because the partitions are not sized as they should be.
32 Documentation notes