HP Insight Control for Linux 6.2 Release Notes

2.8.1 Kernel parameters required for installing x86 SLES 10 SP3 and SLES 11 on
BL465c G7 and BL685c G7 servers
Corrective action: To install an x86 SLES 10 SP3 or SLES 11 operating system on a BL465c G7 or
a BL685c G7 server, you must supply the appropriate boot parameter in the Kernel append line
text field.
Use this kernel boot parameter:For this operating system:
pci=nomsi
SLES 10 SP3 (x86)
apic=bigsmp
SLES 11 (x86)
2.9 Linux image capture and deployment notes
This section contains notes about capturing and deploying Linux images and using the Partition
Wizard.
2.9.1 Capturing and deploying Linux images
This section contains notes about capturing and deploying Linux images.
2.9.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.9.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.9.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.
14 Notes and corrective actions