HP Insight Control for Linux 6.0 Release Notes

2.11.1.1 SLES 11 image deployment fails with GRUB error
In some situations, a SLES 11 image deployment will complete, but the node does not boot. A
GRUB error similar to the following appears on the console:
GRUB Loading stage1.5.
GRUB loading, please wait..
Error 21
In most cases, the deployment failure is actually a capture failure and requires a new image to
be captured.
Corrective action: Before capturing the image, examine the /etc/fstab and /boot/grub/
menu.lst files on the node to be captured, and look for /dev/disk/by-id/* entries.
Replace these entries with the appropriate /dev/sdNP file where N is the disk ID (such as a, b,
c, and so on) and P is the partition.
To find the replacement device, run the ls -l command on the /dev/disk/by-id directory.
The ID files point to the physical disk partitions.
After you make the substitutions, recapture the image and start the deployment again.
2.11.1.2 HP ProLiant DL180 G5 server cannot load captured SLES 10 SP2 image
A captured image does not load on ProLiant DL180 G5 servers, and you will see the following
message:
Error occured while finalizing deployment.
>> Output from log
>> df: `/old_root': No such file or directory
>> df: `/old_root': No such file or directory
>> Could not find device for /boot: Not found or not a block device.
The RAM disk recognizes the disk as an sda device (that is, the first registered device). SLES
recognizes the disk as an hda device (that is, the master device on the first ATA channel). The
two are incompatible; so, when the image is deployed, Insight Control for Linux cannot determine
the correct disk.
2.11.1.3 Deployment of SLES 10 SP3 fails when logical volumes span disks on multiple controllers
Deploying an image on a managed system, running SLES 10 SP3, with multiple disks (each on
individual controller) fails because the order of the disks observed by the RAM disk does not
agree with SLES 10 SP3. As a consequence, the image is deployed to the wrong disks.
Corrective action: Place both disks on the same controller.
2.11.1.4 Log file for deployment issues
During a deployment, most messages are written to /tmp/rct-debug.log on the target server.
If deployment does not complete, use the console to examine this file.
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.11.2 Using the Partition Wizard
This section contains notes about the Partition Wizard.
2.11.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.
22 Notes and corrective actions