PXE Menu Problem - timeout and boot from HDD (menu option 1) -- doesn't happen
-
I am not sure I am putting this in the correct forum, so I apologize if I have placed this incorrectly.
I’ve just gone to Fog V1.2.0 and I haven’t deployed yet to the whole lab.
I’ve built my one Windows 7 machine that I will upload to Fog to be my master image for the lab.I’ve noticed the following situation:
-
If the client PC starts to boot, I can hit the escape key and the BIOS will stop looking for PXE. It will then boot as normal into Windows 7 from the HDD. All good and happy.
-
If Fog is running and I don’t press escape for BIOS to exit its PXE boot attempt, then the Fog PXE menu comes up. The first option is boot from the hard disk and there is a countdown timer until it takes that default action. If I just wait and let the timer run out, the PXE menu gets cleared off the screen and it goes to black. The cursor stays in the upper left hand corner of the screen and blinks. And nothing further happens, ever. No Windows startup, no error. End of the line.
-
No, I haven’t manually chosen option 1 from the PXE menu to see if manually choosing menu option 1 (boot from HDD) has a different effect than letting the countdown timer run out.
So, I’m not sure what to do to investigate this or resolve it.
Thanks much in advance!
-
-
Web interface -> FOG Configuration -> PXE Boot Menu -> Exit to Hard Drive Type
Default is ‘Sanboot style’. Try other settings an see if this solves your issue…
-
That fixed it, thanks. There are only two options, sanboot and grub. Grub worked.
-
Ooops. Shame on me. I spoke too soon. Neither value of Sanboot nor Grub for EXIT TO HARD DRIVE TYPE works.
However, I did get it to work if I choose NO MENU on that same iPXE boot menu configuration page… hmmm???
-
What model is the host you’re testing on?
-
The same hardware I used to use with Fog v.032 and then it worked no problem.
Here is the host info from the Fog v1.2.0 inventory:System Manufacturer LENOVO
System Product 3554CTO
System Version ThinkCentre M72z
System Serial Number PBG8GDL
System Type 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 Current Speed: 2900 MHz
CPU Max Speed Max Speed: 2900 MHz
Memory 3.68 GB
Hard Disk Model WDC WD10EZEX-08RKKA0
Hard Disk Firmware 80.00A80
Hard Disk Serial Number WD-WCC1S6814856
Chassis Manufacturer To Be Filled By O.E.M.
Chassis Version
Chassis Serial PBG8GDL
Chassis Asset -
I’ve been having the blues with Lenovo ThinkCenters at work recently…
Thus far, undionly.kkpxe and r3277 fixed it as far as I can tell.
It’s worth a try, for sure. Turn your menu back on and see how it goes.For more information on that, see this thread: [url]http://fogproject.org/forum/threads/lenovo-mt-m-9964-a1u-cant-register-fails-compatibility-test.12766/[/url]
Also, you’re particular model is listed in WorkingDevices using undionly.kpxe as of late last year: [url]http://fogproject.org/wiki/index.php/WorkingDevices[/url]
-
Hmmm… okay… These Lenovos worked perfectly fine under Fog 0.32…
but what do I need to do to try “…undionly.kkpxe and r3277…”?
-
You could just swap your boot file for now to undionly.kkpxe.
If that doesn’t work, I’d recommend trying the latest revision.
-
Umm… sorry for being dense… but is “undionly.kkpxe” something I download from the fogprohect.org website or ??
Next, when you say try the latest revision, you mean the most current release of Fog itself, right? I’m fine with doing that, if that is a better way.
-
undionly.kkpxe should already exist in your fogserver’s /tftpboot directory.
Either make a copy of this file as your current undionly.kpxe[code]mv /tftpboot/undionly.kpxe /tftpboot/undionly.kpxe_orig
cp /tftpboot/undionly.kkpxe /tftpboot/undionly.kpxe[/code] OR Edit your DHCP servers Option 67/Filename to look at undionly.kkpxe. -
Ok. I will try that in the morning. I will do the mv/cp way.
Do I need to restart anything to have this take effect? -
[quote=“mkstreet, post: 45916, member: 24215”]Ok. I will try that in the morning. I will do the mv/cp way.
Do I need to restart anything to have this take effect?[/quote]Nope.
-
Ok.
I did the mv/cp for the kpxe/kkxe. Here are the results:
Fog PXE Boot Menu Configuration.No-Menu=unchecked
Fog PXE Boot Menu Configuration.Exit-to-hard-drive-type=Sanboot
Result: after PXE menu, black screen with just an underline-style cursor blinking in the upper left cornerFog PXE Boot Menu Configuration.No-Menu=unchecked
Fog PXE Boot Menu Configuration.Exit-to-hard-drive-type=GRUB style
Result: after PXE menu, black screen with just an underline-style cursor blinking in the upper left cornerFog PXE Boot Menu Configuration.No-Menu=unchecked
Fog PXE Boot Menu Configuration.Exit-to-hard-drive-type=Exit Style (i.e. unselected)
Result: after PXE menu, black screen that says: Exiting PXE-M0F ROM and then the underline-style cursor blinkingFog PXE Boot Menu Configuration.No-Menu=**checked
Fog PXE Boot Menu Configuration.Exit-to-hard-drive-type=(any value)
Result: after PXE menu, Windows boots and it’s happyAgain, did I mention that this host worked just fine with Fog V0.32 ?
-
This looks to me like GPT structures are on the disk still, but the disk type is expecting to be MBR Only. Essentially, it looks like the system is trying to boot UEFI, but you can’t exit back to UEFI from a legacy system, nor can you jump to legacy from a UEFI setup.
-
So, you basically need to play around in the firmware settings on the system, I think.
Look at your HDD mode, BIOS vs UEFI, Legacy ROM support, things like that. Play around with it.
From my experience, sanboot works for the handful of machine types in my building.
-
I looked and these are the only BIOS things that seem like they might have something to do with it.
Under ATA DRIVE SETUP:
- SATA controller = Enabled
- Configure SATA as= AHCI
Under STARTUP:
-
Boot Mode
The description says: Sets the boot policy as to whether to try Legacy Boot devices first or UEFI Boot options.
The value is “AUTO”, which is says will prioritize as: UEFI, Legacy -
Boot Priority
The value is “Legacy First”, which it says means “the system will try to boot legacy OS first and then UEFI”
-
If I change the BOOT MODE from AUTO to Legacy or UEFI, then the BOOT PRIORITY disappears from the BIOS menu.
If I change the BOOT PRIORITY to UEFI, it goes into a rebooting loop.I’ve changed it back, and I also moved the origin kpxe file back… but now the situation is worse.
After the Fog PXE menu, it goes to a black screen with cursor and the error beep starts beeping in a constant stream and nothing happens after that.Even now when I do the NO MENU option, I can no longer get it to boot after PXE.
If I hit ESC to abandon PXE, then it will boot to Windows and is happy.As far as PXE Fog Menu, I’ve gone from something that was not ideal but functional by specifying NO MENU…to now something that is non-functional.
-
You may have made a mistake copying the old undionly.kpxe back into it’s place.
The command should have been:
[CODE]cp /tftpboot/undionly.kpxe_orig /tftpboot/undionly.kpxe[/CODE]And, you played around in the firmware, so maybe resetting it to defaults might help too.
additionally, if you’re brave, you might try the undionly.kpxe file from FOG 0.32 and see if the menu works then.
You’ll have to download it (or pull it from your old FOG server), extract that single file, and place it into your current FOG’s tftpboot directory… Maybe you’ll have luck? I’d recommend re-naming the old file to something like undionly-old.kpxe -
I didn’t make a mistake in the copying. I looked at the directory and the file that is undionly.kpxe matches (in number of bytes) to undionly.kpxe_orig, and those two are different in number of bytes from undionly.kkxe.
In the firmware, I only changed the BOOT PRIORITY and BOOT MODE values. Nothing else. I’ve restored those to their original values.
So, … I guess the only remaining thing is for me to be brave?
