Gigabyte board not booting to hard disk

[FuriousGamer065]

Hello!
I am having a issue with my computer where when it boots to fog, It will get to the GUI screen and when it tries to ‘boot to hard disk’ It loops the timer again. If I switch the exit boot, It will use it and sometimes it will hang, or it will say my bootmgr is corrupted, or something else.
I was wondering if there is a fix.

Fog Ver. 1.5.8
Motherboard. GA-AB350-Gaming 3

[Sebastian Roth]

@FuriousGamer065 Is your client system booting in UEFI mode or legacy BIOS?

[FuriousGamer065]

@Sebastian-Roth It is booting off BIOS, and I’m using the network MIX boot

[Sebastian Roth]

@FuriousGamer065 What exactly is “network MIX boot”?

[FuriousGamer065]

@Sebastian-Roth Sorry, I was on my phone, It auto corrected NIC to MIX

[george1421]

@FuriousGamer065 What mode is this mobo in?

That will change what boot file is needed in dhcp option 67.

For bios computers its typically undionly.kpxe ( unless the built in UNDI driver is broken, then its ipxe.kpxe (not very common) )

For uefi computers the boot file is ipxe.efi.

You can not mix them or the system will not boot.

[Sebastian Roth]

@george1421 As far as I get it @FuriousGamer065 is beyond that. The FOG menu seems to come up and chainloading to disk fails in this particular motherboard.

The BIOS implementation is usually causing the failure in chainloading from disk and there is not much we or you can do except die trying the different Exit Types and try to switch over and use UEFI mode. For that you’d need a complete new install and all that…

[FuriousGamer065]

@george1421 @Sebastian-Roth I am using dnsmasq for my Fog Server. I tried using all the exit types and they all don’t do anything, except give me different errors. I booted off only BIOS Network, Not UEFI Network.

[george1421]

@FuriousGamer065 Ok we can eliminate everything except undionly.kpxe (iPXE boot loader) then. This is a disagreement between your hardware and iPXE in BIOS mode.

95% of the time having a BIOS exit mode of SANBOOT will work perfectly. The alternate is grub first HDD.

So the question is how is your system configured?
How many hard drives do you have?
Is the first hard drive the drive where your OS is located?
Is it an NVMe disk or SATA disk?
Do you have a mix of nvme and sata disks in this computer?
Is your firmware up to date on this mobo?

[FuriousGamer065]

@george1421

1. I have 3 HDDs, 1 SSD, 1 NVMe
   2.Windows 10 is on my NVMe drive and it’s the first one
   3.NVMe Drive
   4.Yes
   5.Yes

[george1421]

@FuriousGamer065 First let me say I’m asking because I don’t know.

Does NVMe disks work in bios mode?

For SANBOOT you have to remember that is a bios only boot loader (built into iPXE). It references disks by their bios ordinal position.

For example with FOG it issues this command when you pick SANBOOT. sanboot --no-describe --drive 0x80 In bios syntax drive 0x80 is the first hard drive 0x81 is the second hard drive and so on. Since you have 3 drives 0x82 is the last bios referenced drive. Its possible because of the bios order 0x80 may not be your NVMe drive but a sata drive (I don’t know) but that will explain why SANBOOT is not working for you.

So you might ask how can well tell. Good question…

I think what I would do is create 2 new iPXE menus for testing.

The concept is based in this tutorial: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

But we are going to make a twist on this.

Make two new iPXE menus:
Menu Item: os.Sanboot.D2
Description: Sanboot Drive 2
Parameters:
sanboot --no-describe --drive 0x81 || goto MENU
Menu Show with: All Hosts

Menu Item: os.Sanboot.D3
Description: Sanboot Drive 3
Parameters:
sanboot --no-describe --drive 0x82 || goto MENU
Menu Show with: All Hosts

Now boot into the iPXE menu and see if either of the new sanboot menus work. It will be interesting to know if one of the alternate menus work correctly.