KS.cfg issues with GPT

[Jholcombe]

Hello!

     I'm trying to install using a USB drive and I've found something I can't get around. I've verified that my ks.cfg file works.

Steps:
Rufus install 6.7u1

Copy ks.cfg to root

change kernelopt=runweasel  to kernelopt=ks=usb:/ks.cfg within efi\boot\boot.cfg

Doing this using the MBR setting within Rufus it works fine. I can boot and the kickstart runs without issue even within a UEFI boot

When I use the GPT option within rufus I get the following Error:

exception.HandledError: Error (See Log for more info)

cannot find kickstart file on usb with path -- /ks.cfg

I'm trying to figure out if anyone knows what i'm missing or what my issue is.

Attached:
image of errorboot.cfg in question

[Alex_Romeo]

Hi,

runweasel ks=usb:/<path_to_the_kickstart_file>/ks.cfg

Boot Options

If you are using a USB drive use it as below

runweasel ks=usb:/<path_to_the_kickstart_file>/ks.cfg

When you are modifying the kickstart file there are lots of options available in the deployment guide. You can find the vSphere Installation and Setup guide here.

https://www.techcrumble.net/2017/08/esxi-kickstart-installation-scripted-weasel-installation/

https://docs.vmware.com/en/VMware-vSphere/6.0/vsphere-esxi-vcenter-server-602-installation-setup-gui...

Enter Boot Options to Start an Installation or Upgrade Script

Alessandro Romeo

[Jholcombe]

Alessandro,

   Thank you for the reply. I have found the docs regarding the scripted install. I can get the automated install to work if I use an MBR based usb drive for BIOS or CSM bootable configurations. I'm having issues getting the system to find the file when I load or try to automate the install from a GPT based usb drive for UEFI based configurations. I've gotten it to work previously without the runweasel option, though for testing sake I did go back and test again with the following kernel option of: ks=usb:/KS_Script/ks.cfg

I've tried where my ks.cfg script was located both in root (kernelopt=ks=usb:/ks.cfg) and where it is in a folder within root (kernelopt=ks=usb:/KS_Script/ks.cfg).

Regards,

Jared H.

Edited: Clarity of GPT UEFI based install

[Alex_Romeo]

Hi,

try to do the same thing using UNetbootin instead of Rufus.

UNetbootin - Homepage and Downloads

Alessandro Romeo

[Jholcombe]

When I install to a thumbdrive using UNetbootin I can't even get my UEFI devices to boot from it. They recognize the drive, but fail to boot from the drive. I've verified by browsing into the drive that all the files are there. But still with no luck. Again, I'm using a GPT partition rather than MBR.

[continuum]

If you inspect an ESXi installer ISO file you may see that the files to load are specified like

modules=/b.b00 --- /jumpstrt.gz --- /useropts.gz

while the files in the ISO may appear as B.B00 and JUMPSTRT.GZ ...

So maybe the file is detected if you put it into the root and rename it to KS.CFG

By the way - rufus should do the job and dont use names with mixed capitol and small letters.

[Jholcombe]

Continuum,

     Rufus works for me just fine. I can get it to boot off that. I figured I'd give it a test in case it did something weird with the partitioning. But since Unetbootin failed all together I'm ruling out the idea that rufus was causing me issues. As of now I've tested the following with regards to naming and kernel options with still no success.

File name | kernel/boot options for Shift+o

ks.cfg | ks=usb:/ks.cfg

ks.cfg | ks=usb:/KS.CFG

KS.CFG | ks=usb:/ks.cfg

KS.CFG | ks=usb:/KS.CFG

[Jholcombe]

I also tried the following just now with no luck

KS.CFG | ks=usb

ks.cfg | ks=usb

all of these with the ks.cfg file within the root of the bootable thumbdrive

[continuum]

I would like to see a screenshot of the USB opened in Windows explorer

[Jholcombe]

see below:

[Jholcombe]

Following up again to see if you have any further insights on what may be causing me my issue.

Thanks,

-Jared

[continuum]

I tried to download your latest screenshot - but something with it is not working.

The ks.cfg file is missing so the screenshot did not help.

[Jholcombe]

Continuum,

     I've tested this on several different ks.cfg scripts. including the one I've attached below. As for the image from earlier, i suspect you were trying to look at the capitalization of the files? if so, they were all in lower case.