HP Insight Control Server Provisioning 7.3 Update 1 Administrator Guide

◦ From a server running Linux or the Linux service OS enter the following:
mkdir /mnt/ms
mount —t cifs —o username=<username>,sec=ntlmv2,noserverino
//<media-server-ip-address>/<file share name> /mnt/ms
You can ignore mkdir command, if /mnt/ms already exists. The command will prompt
for password. Enter the Media Server password and see whether the file share is mounted.
If it is successful you should be able to go to the /mnt/ms folder and see the file share
contents (Images, Media and so on).
If the command fails then try one of the following mount commands and see which one
works. If you find one that works, update your Build Plan to use the specified options.
mount —t cifs —o username=<username>,sec=ntlmvssp,noserverino
//<media-server-ip-address>/<file share name> /mnt/ms
mount —t cifs —o username=<domain/username>,sec=ntlmv2,noserverino
//<media-server-ip-address>/<file share name> /mnt/ms
mount —t cifs —o username=<username>,sec=ntlmv2i,noserverino
//<media-server-ip-address>/<file share name> /mnt/ms
Create Stub Partition error
Linux or ESXi Build Plan error: create stub partition
The Symptom in all cases is the inability to create a stub partition. Possible causes and resolutions
are shown in the right-hand column.
Possible cause and resolutionSymptom
Linux or ESXi Build Plan error: create stub partition. 1. No physical disk found on target server.
• Add a disk to the target server. Insight Control server
provisioning requires either a local disk to install to,
or a single SAN disk that has been properly
configured as the boot disk.
2. Smart array is not configured properly.
• A logical drive has not been defined on the target
server’s Smart Array. Create one manually, or
customize the Smart Array configuration Build Plan
to configure the Smart Array and run that Build Plan
against the target server.
3. Storage Controller is not enabled in the BIOS
• Enable the storage controller in the BIOS manually,
or customize the System ROM configuration Build Plan
and then run that Build Plan against the target server.
Device busy error on create stub partition
Possible cause and resolutionSymptom
The Create stub partition step sometimes returns a Device
busy error. If the Build Plan does not fail on this step, this
is normal and can be ignored.
1. There is a previously installed Windows OS on multiple
disks.
• The boot disk and one or more other disks on the
target server contain a previously installed Windows
Errors from step 8 'Create Stub
Partition': umount: /mnt/local_root/dev:
operating system. Edit the Build Plan and add the
Unmount all Boot Disk Partitions step before the Create
stub partition step. Re-run the Build Plan.
device is busy. (In some cases useful info
about processes that use the device is
found by lsof(8) or fuser(1))
Troubleshoot OS Build Plan and build plan step failures 93