Error on Start from hard disk (HD)
-
hi,
I formatted a PC with windows 10 and when it boots from the network and falls into the fog options screen, I left the option “start from hard drive (HD)”, but after that, the pc is in a reboot loop and does not enter in the windows 10 installation.
In the bios the boot (legacy) is for:
- nic
- hd
fog version:
- 1.5.9
- bzImage Version: 4.19.145
- bzImage32 Version: 4.19.145
Any ideas or tips?
-
@eliaspereira I’m thinking that windows 10 you installed on that computer is broken. BIOS mode should go to fog menu and then exit to hard drive no problem. You can test this by changing bios setting to not pxe boot, but go to hard drive first. See if windows boots normally.
If yes it boots, then we need to look into fogs settings.
If no it does not boot, then you need to look into your windows installation.
Just as an unrelated thing. You should update your FOG Linux kernel to version 5.10.55 or later. You can do this from the web ui FOG Configuraiton -> Kernel update. This will give you support for the latest computer hardware and drivers.
-
If I change in BIOS or skip pxe boot, windows boots normally. I had already taken the test.
In which fog settings can we check?
-
In Boot Exit settings menu I changed “Exit to Hard Disk Type” to GRUB.
Apparently it worked.
-
@eliaspereira In the FOG Web ui, FOG configuration -> FOG settings hit the expand all button. Search the page for bios. Make sure the exit mode for bios is SANBOOT and for uefi its set to REFIND.
Bios mode SANBOOT should work 100% of the time since it is the most understood format for booting. UEFI is a bit more complicated to solve when things don’t work as they should.
EDIT: I see you change the exit mode to Grub. That will work too, but I’m surprised that grub works when SANBOOT didn’t
-
@george1421 said to @eliaspereira in Error on Start from hard disk (HD):
I see you change the exit mode to Grub. That will work too, but I’m surprised that grub works when SANBOOT didn’t
I find this a bit strange too but well you never know. Hardware can be a real pain and is doing weird things across the board. So I guess there is some hardware out that not able to chainload the OS via EXIT or SANBOOT but is happy with the GRUB method…
