Unsolved

2079

January 24th, 2020 14:00

Deploy OS 'Boot from ISO' sticks server in continuous boot to scripted ISO

I created a kickstart file for an unattended ESXi install. I create a "Deploy" job, and point the "Boot from ISO' to an NFS share that points at the newly customized ESXi.iso with the KS file in the root. Everything works great. I even scripted the BOSS VD to be the disk of choice for the installation in a system that has three different types of drives installed. The problem is, that once the installation is complete the server reboots, and goes right back into the KS file install that was pushed by the OME job. 

 

Is there a way for the ISO to boot, install, reboot, and just load the newly installed OS? It seems that once the image is pushed from OME it creates a boot device pointing directly at the vFlash Media ISOIMG in the UEFI boot options menu and prioritizes it above the disk that had the OS installed. The job created says that the mount point will be deleted after 24 hours, but I need it to remove after the first attempt.

 

Any advice is greatly appreciated. Thanks.

 

 

Copy of my ks.cfg file: 

#
# Sample scripted installation file
#

# Accept the VMware End User License Agreement
vmaccepteula

# Set the root password for the DCUI and Tech Support Mode
rootpw xxxxxxx

# Install on the first local disk available on machine
install --firstdisk=DELLBOSS\ VD --overwritevmfs

# Set the network to DHCP on the first network adapter
network --bootproto=dhcp --device=vmnic0

# A sample post-install script
%post --interpreter=python --ignorefailure=true
import time
stampFile = open('/finished.stamp', mode='w')
stampFile.write( time.asctime() )

 

11 Posts

February 8th, 2020 08:00

I have a very similar problem using ansible to automate an ESXi install.

 

Using the idrac_os_deployment module, it reboots the server, mounts the custom ISO, deploys the ESXi OS and reboots after install. However, like you pointed out in your example, it boots back into the "vFlash Media ISOIMG" and get's stuck in a loop until iDRAC is reset or the expose_duration times out.

 

I worked around the issue by setting the boot mode to UEFI instead of BIOS. Perhaps the same will work in your situation.

 

This is what the BIOS boot settings looks like if the boot mode is set to BIOS and the network mounted ISO is still attached.

 

For Dell devs, perhaps you can mount the network ISO and set it to boot once vs. altering the BIOS boot sequence.

Screen Shot 2020-02-07 at 10.50.45 AM.png

No Events found!

Top