PXE Boot environment crash

[alexwellslinden]

Hi,

Got an issue where the PXE boot screen loads, displays for about 2-5 seconds and then crashes out delivering me the error:

“Non-system disk or disk error replace and strike any key when ready”

Is there anything that could be causing this? Current system setup below:

FOG server running on Debian Jessie 8.5, latest update.
DCHP run via Windows 2012R2 DC

Any assistance is appreciated.

[Wayne Workman]

@alexwellslinden It sounds like the host is passing through iPXE successfully, and there is no task, so it’s sent to the HDD which has no valid OS on it, or the firmware is in the wrong mode (BIOS/uEFI) and can’t boot from the HDD.

[Tom Elliott]

What version of FOG?

Is the system trying to boot attempting to boot using UEFI or legacy? From the sounds of things, it’s network booting VIA bios but the system is expecting UEFI.

[alexwellslinden]

Currently running the stable release, which is version 1.20 I believe.

[Wayne Workman]

@alexwellslinden It sounds like the host is passing through iPXE successfully, and there is no task, so it’s sent to the HDD which has no valid OS on it, or the firmware is in the wrong mode (BIOS/uEFI) and can’t boot from the HDD.

[alexwellslinden]

@Wayne-Workman Yeah… that was it. Changed the timeout in the FOG Configuration settings now. Suddenly it works. Thanks for the assistance.

[Wayne Workman]

@alexwellslinden So it was the HDD exit type then?

[Tom Elliott]

@Wayne-Workman I think what he is saying is basically, the timeout default was timing out faster than the display could keep up with. So by the time the OP started seeing anything, it was already loading into Windows rather than giving a menu they could work with.

By upping the timeout value, it gave the system enough time to display the menu and allow the OP to perform the necessary actions.

Of course, if I’m wrong please let me know.