HP Insight Control for Linux 7.1 Release Notes

2.6 Linux image capture and deployment notes

2.6.1 Image capture/deployment issues with VID enabled setting on Gen8 servers

The Virtual Install Disk BIOS option on Gen8 servers, if set to Enabled, might cause image capture

and deployment operations to fail. Furthermore, a server running the SLES 10 SP4 operating system

could fail with a partitioning error.

Corrective actions:

• Set the VID setting to disabled as follows:

During the boot, select the F9 key to access the ROM-Based Setup Utility.1.

2. Select Advanced Options→Advanced System ROM Options.

3. Select Virtual Install Disk and set it to Disabled.

4. Exit the ROM Based Setup Utility.

• If there is an entry for the VID in the /etc/fstab as a result of the OS installation, remove

the mount point for the VID before you capture the image. Otherwise, the image might not

deploy.

The entry for the VID would resemble the following:

/dev/disk/by-id/usb-HP_iLO_LUN_00_Media_0_000002660A01-part1 /windows/C

vfat users,gid=users,umask=0002,utf8=true 0 0

2.6.2 Capturing and deploying Linux images

This section contains notes about capturing and deploying Linux images.

2.6.2.1 Partitioning fails on SLES 11 SP1 image deployment

An invalid partition captured in a SLES 11 SP1 image might cause Insight Control for Linux to fail

to partition a server during a deployment. The partition will have no filesystem type, no mount

point or other valid information.

Corrective action: Use a text editor to locate and remove the line resembling the following from

the image file in the /opt/repository/.icle directory on the CMS.

2.6.2.2 Deployment of SLES 11 image fails because RAM disk and OS interpret disk differently

A deployment could fail because the installed operating system interprets a disk as

/dev/cciss/c0dn, where the Insight Control for Linux RAM disks interprets the disk as /dev/

sda. Consequently, the disk might not be specified correctly in the /boot/grub/menu.lst file

and /etc/fstab files.

If disks are listed by their device names, the capture operation will succeed, but Insight Control for

Linux will be unable to determine which disks to use during deployment.

Corrective actions:

• Use a text editor to locate references to /dev/cciss/cmdn in the /boot/grub/menu.lst

file and /etc/fstab files and change them to either /dev/disk/by-id or LABEL=

references before capturing the image.

• If an image was already captured with the wrong disk device references, edit the image

description file in /opt/repository/.icle and replace the references to

/dev/cciss/cmdn with disk device names that the RAM disk understands.

2.6 Linux image capture and deployment notes 13