Got the same error , after installing in my Dell latitude E7440 for Lab testing , got it working by swapping to legacy BIOS, I tried as well a few combinations of UEFI (no secure boot), UEFI with secure boot, and legacy BIOS, and the only work that works is legacy BIOS.
After changing I could boot the server, and then got the error again , so i have to reinstall , delete all partitions and now is working fine
3 people found this helpful
We are one two month away from the U3, in meantime no patches or fixes for booting in UEFI mode?
We are waiting for the patch. On the server SuperMicro X9DR3-F, ESXi 6.7.0 U3 only works in Legacy mode.
now almost three……
and 6.5 release one patch several days before.
but may server cannot be updated online.
are there any updates related to an official fix?
We are stuck (with one host) on pre 6.7U3 as we cannot perform the upgrade due to the issues descriped in this thread.
I would appreciate any offical statement from VMWare related to this. Thanks
A patch release that includes a fix for this issue is coming soon.
My company lost about $3000 cause of this bullsh*t.
You better should include that patch into that U3 iso file. If i would look for a virtualization solution and run into that... bye bye vmware.
But at least, if you come from U2 and run...
esxcli software profile update -p ESXi-6.7.0-20190802001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
..the patch will be included in the update?
I said a patch that contains the fix is coming soon. That means it is not released yet, so no, you won't get the fix by upgrading to any currently released patch. Also the contents of already released patches or updates will not be retroactively changed. You will get the fix by upgrading to the patch that has the fix, when it is released. I can't give more details than that at this time.
sorry,you didnt get me right.
just wanted to know, if this issue can be fixed (in future) by running the esxcli software profile update command on U2 or if its necessary to take hand on every esxi machine.
i think this will be the different to make us switch to a different solution.
i tried to fix this issue 6 hours on my own homelab (no legacy boot) and figured out that your solution with "refit" was kind of a blind shot.
last update for that was 2010 and ist mostly mentioned to mac os. Tried, didnt work.
If you update directly from 6.7u2 to the upcoming patch that contains the fix, you'll never have the buggy bootloader installed and will never boot with it. I think that was your question.
Of course, if you have a machine that's already suffering from the bug (upgraded to 6.7u3 and won't boot), obviously you have to do something by hand to get out of that state. The easiest ways are (1) if possible, boot in legacy BIOS mode, or (2) boot an installer ISO from an unaffected release and use the installer to upgrade to it. I believe the upcoming patch will include an installer ISO. Patch releases normally don't, but I requested one for this patch to make it easier, so that you don't have to downgrade to 6.7u2 using its ISO and then upgrade to the patch.
In the procedure I gave for running 6.7u3 in spite of the bug, I suggested rEFIt exactly because it's old. rEFInd is newer, but that's not necessarily better, as it comes with a new enough EFI shell that it won't work on machines that are too old. The procedure is complex and has pitfalls, so I'm not surprised some people who tried it didn't get it to work. Fortunately it won't be needed anymore as soon as the new patch is out.
The statement that you put in quotation marks is not true and certainly is not a quote from me.
thanks for your fast reply.
We are looking forward to here from you soon.
Best from Germany,
Patch is up today FYI.