[quote=“Junkhacker, post: 27364, member: 21583”]FOG_BOOT_EXIT_TYPE is only relevant for .33+ versions of Fog.
does the computer boot properly when not connected to the network?[/quote]
If its not connected to the network, yes it will boot properly.
It tries the network for about 40 seconds because PXE is our first boot device, then it gives up and goes on normally to the local HDD.
If I press escape, it will exit trying PXE and go on normally as if it had given up on PXE too.
[quote=“Tom Elliott, post: 27259, member: 7271”]Change the exit type within the GUI. There are two types, exit and sanboot. For your setup, try with exit. It’s defaulted to sanboot.
Location is: FOG Configuration->FOG Settings->FOG Boot Settings->FOG_BOOT_EXIT_TYPE[/quote]
Hi Tom,
Thanks for the reply. I will try that on Monday. Would this FOG_BOOT_EXIT_TYPE affect all exits to the local disk boot – and not just boots-after-deploy? I have this same get-stuck “Booting from local disk…” when I choose “1” from the PXE menu.
Do I need to be concerned about that message during FOG Hardware Inventory about unknown BIOS ?
Sorry about not including the version info. I’m using… Fog Vers: 0.32 O/S: Ubuntu 12.04.04 LTS (Pangolin)
i found this thread while searching for my hardware. I’m not sure if my problem would be fixed by this kernel or not?
I have Lenovo M72z and it PXE boots ok, but if I choose (or it times out on the pxe menu) to the first option: “boot from local disk”… well, it doesn’t happen.
I get a black screen that says “Booting from local disk…” in the upper left corner, then it hangs there forever.
As far as I can tell, everything else seems to be ok. I can upload and deploy images. Sometimes when I multicast, one computer in the group (of five computers) won’t wake (for unknown reasons) and then the multicast will be stuck at “Please Wait” (blue screen) until I go power up the offending hardware. Then it takes off fine.
After I deploy an image, it tries to reboot and I get to the black screen “booting from local disk” hang (as noted above) again. When I hit ESC to skip the pxe menu, I can get in just fine… but then it will reboot once the first time after a deploy after a minute or so… I think this must be a delayed reboot command from FOG left over from the image deploy (because the black screen hang didnt ever complete successfully).
I did the hardware inventory option and I noticed a message fly by about unknown/unrecognized BIOS “please report”. Though I am not sure where to report this?
Here are the results from the hardware inventory of a typical machine:
System Manufacturer
LENOVO
System Product
3554CTO
System Version
ThinkCentre M72z
System Serial Number
PBG8GDG
System Type
Desktop
BIOS Vendor
LENOVO
BIOS Version
F6KT32AUS
BIOS Date
09/03/2013
Motherboard Manufacturer
LENOVO
Motherboard Product Name
MAHOBAY
Motherboard Version
NOK
Motherboard Serial Number
Motherboard Asset Tag
CPU Manufacturer
Intel
Corporation
CPU Version
Intel Core
i5-3470S CPU @ 2.90GHz
CPU Normal Speed
2900 MHz
CPU Max Speed
2900 MHz
Memory
3433056 kB
Hard Disk Model
WDC WD10EZEX-08RKKA0
Hard Disk Firmware
80.00A80
Hard Disk Serial Number
WD-WCC1S6883074