HP Insight Control for Linux 6.3 Release Notes
For example, if the source managed system has two disks, but the target managed system only
has one disk, you might see the following message in /tmp/rct-debug.log:
yyyy/mm/dd time: Waking up
yyyy/mm/dd time: Capturing GrubBootLoader loader
yyyy/mm/dd time: Image Service genDeployCmds
yyyy/mm/dd time: genDeployCmds Failed : Message = target does not have enough drives for the image
2.10.1.4 Captured Image could fail to deploy because of duplicate labels or pre-existing partition
information
Duplicate labels could cause a captured image deployment failure. A duplicate label can cause
the deployed OS to select an incorrect disk to mount or use during the boot processes. Duplicate
labels occur when a disk label from the image already exists on more than one disk on the target
system.
Also, if a disk was previously used as part of an LVM or RAID set, the partition information could
interfere with the partitioning code during deployment.
Corrective action:
1. Diagnose→Boot to Linux Rescue Mode to access the RAM Disk environment on the target
system.
2. Use the following command to clear the first 5120 bytes of the disk to remove any partition
or existing master boot record (MBR) information:
# dd if=/dev/null of=disk count=1 bs=5120
3. Rewrite the disk's partition table to remove any existing labels.
2.10.1.5 Timeout occurs during Linux image deployment
A timeout can occur when it takes an unusually long time to prepare a disk for imaging. The default
timeout is 30 minutes, but in rare cases, such as with a very large disk partition, the preparation
might exceed that limit. When this happens, you can manually increase the timeout value for this
operation.
Corrective action: Modify the /opt/mx/icle/icle.properties file by adding the following
parameter, where sec is the timeout value in seconds:
RAMDISK_DISK_CONFIGURATION_TIMEOUT=sec
For example, a value of 3600 specifies a timeout of one hour. You can specify whatever value
you believe is appropriate, but keep in mind, this increase should only be needed in unusual
circumstances.
2.10.2 Using the Partition Wizard
This section contains a note about the Partition Wizard.
2.10.2.1 Cannot create or rename swap partition
The Partition Wizard does not allow the creation or renaming of a swap partition. The Partition
Wizard insists that you specify a mount point, which swap partitions do not have.
Corrective action: HP suggests that you do not create the swap partition in an LVM volume, and
that you do not use the Partition Wizard for creating or renaming the swap partition.
2.11 HP Insight Control virtual machine management notes
The HP Insight Control Release Notes contain release notes specific to HP Insight Control virtual
machine management. You can access this document from the following web address:
www.hp.com/go/insightcontrol/docs
16 Issues and suggested actions