@george1421 1. Yes, I’m sure it is specifically configured for Uefi mode.
2. I have a w2012 dhcp server and thought I had it configured for dynamic support. I’ll go through all the settings again to make sure. The thing is, I can PXE boot in UEFI just fine when it’s a physical machine, it’s just the VM which is giving me trouble, but I’ll make sure to check all the settings on my DHCP server.
My FOG server is running on CentOS.
@vanopy said in Hard Disk not found after Deployment:
@george1421 Ok, I think this may have been helpful, George.
What I’m seeing is the following:
But shouldn’t it be referring to ipxe.efi instead of undionly.kpxe?
Maybe this isn’t making any sense what I’m saying…
Anyway, this is the output I get when I perform tcpdump -i any port 67 or port 68 or port 69 or port 4011
When I enter the command which is in your tutorial, I’m getting the following error:
NFLOG link-layer type filtering not implemented.
@george1421 Ok, I think this may have been helpful, George.
What I’m seeing is the following:
But shouldn’t it be referring to ipxe.efi instead of undionly.kpxe?
@george1421 Already removed it when I saw it, thank you!
I will give it a try and get back to you.
@george1421 So I’m looking into this again…
I’ve adjusted everything on the DHCP as I believe it should be.
I also found an article saying that I should use vmxnet3 as the network adapter instead of the E1000, which could have difficulties with PXE Booting.
I’m now getting a different error message when I’m trying the UEFI PXE Boot, I’m getting the following:
succeed to download nbp file unsuccessful
Any idea what else could be going wrong for me?
Thanks again.
@george1421 Yes, I’ve done it earlier today in BIOS mode and that worked fine.
Ok, I see, I will also add those.
@george1421 Yes, several times. Never a VM though… dhcp option 67 is already ipxe.efi
@george1421 May I ask for your assistance one more time please?
I believe I have everything ready, but now I would need to know how to get my UEFI VM to PXE boot.
I’ve tried the boot option EFI Network, but it just sits as this screen and nothing happens:
@george1421 The flash based… Just tried to login directly on the client and now I see the option…
Was always used to work this way and didn’t even realize I was lacking quite some options by doing so.
Seems that it was an ID10T error, sorry about that 
I’ll give it another try now, thank you!
@george1421 I’m using the vSphere Client, and it’s not there for me unfortunately:…
@george1421 Yes, I saw those settings, but strange enough it seems that I don’t see all these options in the VM options.
I only see General Options, VMware Tools and Advanced. I’m also running on vsphere 6.5 though…
@george1421 Did you also do this in VMWare?
If so, how did you do the install in VMWare, to make sure the disk was in UEFI?
Was it also by editing the .vmx file?
Yes, I also saw this article, but by adding the UEFI option, I wasn’t sure if this would be sufficient and if the disk would already be in GPT during the installation process.
Anyway, I will give this a try, thanks for looking into this!
After browsing through the forum, I think I have found the issue.
I have never created an image via VMWare and apparently when installing the W10 iso, it is by default in MBR.
If I’m not mistaken, it should be in GPT to get it working in UEFI.
Is there any guide/procedure to get the image captured in GPT, while it’s a VM in VMWare?
I can’t seem to get the disk in GPT by default, Windows seems to be always installing on the disk in MBR…
Another update:…
When I deploy an older W10 image which I captured from a physical machine instead of from a VM, it deploys just fine on the Optiplex 5070.
What am I doing wrong with this VM image for the 5070?
Update on this problem:
Seems that the image is working fine on a different model: Dell Optiplex 3040 is working fine.
I keep having the loop problem on several Dell Optiplex 5070’s. Any idea why that might be idea?
Hi guys,
Looking for some help here.
I have captured a new image today via a Virtual Machine, no errors, seems to be working fine.
Deployed the image to several machines, no errors, seems that deployment was successful.
But… When I try to boot, it can’t find the Hard Disk, only thing which is there is the Windows Boot Manager and the PXE Boot options. When I boot into fog again, and select boot from hard disk, it just brings me to rEFInd Boot Manager page.
Almost looks like the hard disk is completely gone for some reason. When I try adding it in the Bios, I get the error no file system found…
Has anyone seen something like this before and how can I get this fixed?
Thanks for your assistance, much appreciated!
