Quantcast
Viewing all articles
Browse latest Browse all 3345

Crash on loading boot.sdi

I am having problems PXE booting ESX VMs on 2017.3.  This morning I had VMs that would not provision, they could not get an IP address for the template.  I spent the morning working with various drivers and finally got that to work.  Then I went to reload a couple more VMs that happened to be on VM version 8.  Knowing that I have had previous lockup problems with Windows 10 on VM version 8, I opted to upgrade the hardware to currently available 11.  Now when I try to PXE that newly upgraded system, I cannot load the boot.sdi file.  It ends up crashing with the message that "A required device isn't connected or can't be accessed."  I went through all the postings about changing the TFTP block size, but unless it takes time for that change to replicate, those options didn't help.  At the moment, I am stuck in a pickle: Either stay on hardware version 8 which locks up machines randomly, or have machines that can't PXE.  Assistance is greatly appreciated.  Thanks.


Viewing all articles
Browse latest Browse all 3345

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>