Chainloading Failed

[Wayne Workman]

@Buddy Try a different HDD Exit type (host’s general page). Or, disconnect your USB adapter to allow the device to boot on it’s own. FYI Surface Pros are UEFI, so you only need to play around with the Host EFI Exit Type field.

[Buddy]

After unplugging from the network and trying to boot, we just get the bios screen wanting us to select a boot method. I am wondering if the GPT partition is not correct.

We went through all of the EFI Exit types and no luck.

Any way to verify the partitions that fog is pushing down to it? We use this image on 200+ desktops just fine.

[Junkhacker]

are those 200+ desktops configured to boot to UEFI or Legacy?

[Wayne Workman]

@Junkhacker My thoughts exactly.

[Buddy]

Ok just to check and make sure we have loaded a fresh copy of windows 10 on the surface. Now when we try to upload the image it gives us the Chain Loading Failed. Before it would deploy image but not boot to it.

We must be using legacy on the desktops.

[Wayne Workman]

@Buddy just checking basics here, do you have has_usb_nic=1 set as a kernel argument?

[JJ Fullmer]

@Buddy
I’m assuming you are using efi for this, since that is the way of the surface.
In efi I’ve had the best luck with refind_efi as the exit type.
You may also want to play with the bootfile. Which bootfile are you using?
i.e. ipxe.efi, snponly.efi, etc

[Buddy]

@Wayne-Workman

Yes we have the has_usb_nic=1 in there.

[Buddy]

@Arrowhead-IT

I have tried the refind_efi exit type with no luck.

We are using the ipxe.efi as our boot file.

[Wayne Workman]

@Buddy so what happens if after imaging you unplug the NIC adapter and power cypower the tablet?

[Buddy]

@Wayne-Workman

It does not boot. Just goes to the bios screen.