Hello,
I am trying to install ESXi 8.0.1 through a USB and I continue to get the error:
UEFI Secure Boot failed at time <time-date-stamp>:
All vib signatures verified. Unrecognized tardisks: [<list of a bunch of scripts, i guess?>]
After doing some research I have found that the items listed withing the brackets are also items found in my boot.cfg file under modules=. I was hoping to get some kind of explanation for the error that I am seeing and maybe I can figure it out. A solution would be cool too.
To create the bootable disk I followed about two or three online guides that used the VMware powershell modules. Is there maybe an up to date guide for how to do this? I am working with an intel nuc 11 as well in case theres something I dont know about with that hardware.
Just disable the secure boot and and try to install ESXi. Once it installed then run the secure boot validation script to check if your setup supports secure boot. Please run the below command to check:
/usr/lib/vmware/secureboot/bin/secureBoot.py -c
Check the output that includes: "Secure boot can be enabled or Secure boot CANNOT be enabled"
Regards,
Sachchidanand
Ah I found a solution to that issue, if you try and build a custom copy of the iso and include the community network drivers it hangs up around vmkdevmgr. I actually tried the clean iso directly from vmware and created a bootable drive with it, and it booted just fine as is no additional items necessary.
Thanks,
Brandon
Just disable the secure boot and and try to install ESXi. Once it installed then run the secure boot validation script to check if your setup supports secure boot. Please run the below command to check:
/usr/lib/vmware/secureboot/bin/secureBoot.py -c
Check the output that includes: "Secure boot can be enabled or Secure boot CANNOT be enabled"
Regards,
Sachchidanand
Hello,
Thank you for the advice, I dont know why I was thinking there was a separate option within esxi to turn this off but it was just in the boot settings. Great work.
I do have a follow on question as of now, after it boots up into the installation media my device doesnt want to continue past something called: vmkdevmgr? I dont know what this is but its been hung up on that one spot all day. Do you have a solution for that too?
Ah I found a solution to that issue, if you try and build a custom copy of the iso and include the community network drivers it hangs up around vmkdevmgr. I actually tried the clean iso directly from vmware and created a bootable drive with it, and it booted just fine as is no additional items necessary.
Thanks,
Brandon
