HP Insight Control for Linux 6.3 Release Notes

IMPORTANT: Only the 12-core version of these servers are affected. They are equipped with the

AMD SR5690 NB (PCI-E Gen2 and HT3) and AMD SP5100 SB (PCI-E Gen2 link to SR5690) chip

sets.

The servers are:

• DL165 G7

• DL385 G7

• DL685 G7

• SL165s G7

• SL165z G7

• BL465c G7

• BL685c G7

Use the following table to determine the boot parameter to enter in the Kernel append line text

field.

Use this kernel boot parameter:For this operating system:

pci=nomsiSLES 10 SP3 (x86)

pci=nomsiSLES 10 SP4 (x86)

apic=bigsmpSLES 11 SP0 (x86)

Not applicableSLES 11 SP1 (x86)

2.10 Linux image capture and deployment notes

This section contains notes about capturing and deploying Linux images and using the Partition

Wizard.

2.10.1 Capturing and deploying Linux images

This section contains notes about capturing and deploying Linux images.

2.10.1.1 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

>> 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.10.1.2 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.10.1.3 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.

2.10 Linux image capture and deployment notes 15