HP Insight Control Server Provisioning 7.3 Update 1 Administrator Guide

Possible cause and resolutionSymptom
Disable all disks except the installation disk on System RBSU
or explicitly state in the ESXi answer file the disk number to
install to.
Linux Build plan failures
RHEL6.3 OS deployment fails on server with iSCSI or FCoE
Possible cause and resolutionSymptom
Target servers with iSCSI or FCoE require advanced configuration of the kickstart file;
the default files will not install to these systems. You need to create a custom kickstart
file with the required settings. See Red Hat documentation for details.
For both RHEL 6.3 and 6.4, autopart is broken and requires manual disk layout. This
happens even when installing via DVD ISO.
RHEL6.3 OS deployment fails.
Below is an example of what to include in your kickstart file to bypass this problem.
NOTE: Remember to comment out “autopart”.
Example 2 Example code
part /boot --fstype=ext4 --size=500
part pv.01 --grow --size=1
volgroup vg_01 --pesize=4096 pv.01
logvol / --fstype=ext4 --name=lv_root --vgname=vg_01 --grow
--size=1024
logvol swap --name=lv_swap --vgname=vg_01 --grow --size=1024
--maxsize=204800
OS deployment error: Could not find the SUSE Linux Enterprise Server 11 Repository
Possible cause and resolutionSymptom
The NIC is not ready when access to the Media Server
occurs, so the installation is unsuccessful. Set the
kernel_argument custom attribute and specify netwait=10.
OS deployment error: Could not find the SUSE Linux
Enterprise Server 11 Repository
Target servers unable to reach the Media Server Windows file share
Possible cause and resolutionSymptom
An OS Build Plan fails on the step Set Media Source when
trying to mount the Media Server Windows file share or
• Verify the Media Server settings specified on the Settings
Media Server panel are correct. One way to verify the
steps that access the Media Server report not being able
settings is to manually map the drive or access the http
to access it. This might occur during an OS installation
with reports occurring on the target server console.
URL from a system on the same network as your
appliance.
• Make sure the Media Server IP address is accessible
from your appliance network and the network your target
servers are on.
• If a gateway is required to access your Media Server,
make sure the gateway is properly defined in your
Settings Appliance and Settings DHCP panels.
Troubleshoot OS Build Plan and build plan step failures 87