Want to skip "Booting... (Press Escape to access the menu)"
-
@DAHansen75 Ok that info is correct so we can rule out any of the iPXE booting stuff.
Have you inspected the FOG Configuration->FOG Settings and the FOG Boot settings section.
This is what I have in that section and my fog server boots directly into the FOG menu and then after 5 seconds exits to the hard disk boot (via sanboot)
-
@george1421 Mine looks exactly like yours, except for the first one, which is 3 on mine, instead of the 5 on yours.
-
@DAHansen75 well this is an interesting one then.
Does it act differently for a unregistered system vs a registered one?
Actually lets try this check.
open a browser and go to:
http://172.17.4.185/fog/service/ipxe/boot.php?mac=f8:b1:56:99:48:28That should send out a bunch of text, this is the configuration behind the iPXE boot menu. Please post the content of that action here. The mac address is the address from the picture you posted below.
-
@george1421 Here you go! It is WAY different from what I get doing the same thing using the Old Fog Server:
#!ipxe
set fog-ip 172.17.4.185
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
cpuid --ext 29 && set arch x86_64 || set arch i386
iseq ${platform} efi && set key 0x1b || set key 0x1b
iseq ${platform} efi && set keyName ESC || set keyName Escape
prompt --key ${key} --timeout 0 Booting… (Press ${keyName} to access the menu) && goto menuAccess || sanboot --no-describe --drive 0x80
:menuAccess
login
params
param mac0 ${net0/mac}
param arch ${arch}
param platform ${platform}
param username ${username}
param password ${password}
param menuaccess 1
param debug 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain -ar http://172.17.4.185/fog/service/ipxe/boot.php##params -
@DAHansen75 Well on the plus side, iPXE is doing exactly what its being told to do.
The next question would be why? What do you have under FOG Configuration -> iPXE Boot menu? This almost looks like someone hacked/created a custom boot menu. If it was something that someone did in the past with the boot.php file, it should have been overwritten when you installed 1.3.0RCx series.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
-
@george1421 if I had to guess this is remnants of the old 1.0.1 server, or as u like to refer it as ‘bleedover.’
Maybe try
sudo rm -rf /var/www/{html/,}fogand re run installer? -
@george1421 No one here has edited the boot.php. It was a clean install on a freshly formatted machine, with a fresh install of Ubuntu 14.04. I used GIT to install trunk. I think I figured something out though.
If I go to /fog/service/ipxe/boot.php - it looks nothing like what I copied/pasted. The actual file is different and looks correct.
I DID FIND, around line 598, in /root/trunk/packages/web/lib/fog/bootmenu.class.php the code that changes the menu. I just don’t why it’s doing it.
Perhaps I should have installed through SVN instead of GIT, and/or not as ROOT when installing trunk.
-
@DAHansen75 said in Want to skip "Booting... (Press Escape to access the menu)":
Perhaps I should have installed through SVN instead of GIT, and/or not as ROOT when installing trunk.
SVN and GIT repositories are identical, you will get no different version from either. You absolutely should be installing as root. The proper way to become root is
sudo -iand using other methods (esp. in Ubuntu) will cause you trouble. -
@Wayne-Workman I think I’m going to try a clean install again using sudo -i instead of logging in as root and see if that helps. I will report back soon!
OK! Still not working. I tried installing using sudo -i that still had the same problem.
I rm’d everything, and I tried installing using SVN (just in case) and still have the same problem.
I might try installing 1.2.0, see if I can get that to work, then try again.
UPDATE: I’m sticking with 1.2 for now. It’s working ok, and I’ll try again with Trunk in the Spring.
Thanks for the help!
-
Update: 1.2 works ok, so I’m sticking with that for now.
-
The developers have confirmed this is “an issue” with RC14 and a new install. When both conditions are met the database is not created properly. While I understand you have committed to 1.2.0 (actually if you upgrade from 1.2.0 to RC14 the upgrade would have worked correctly.). The issue has been resolved in RC15 for both upgrade as well as a new install.
-
@george1421 I just did an upgrade from a fresh install of RC-14 to RC-15 and I am still seeing this issue. I have tried turning “No Menu” on, same issue. I have tried all the different boot options under PXE Menu, same issue. The only workaround that works for me is setting the PXE Menu to “Hide” and then it blinks past the screen and boots the hard drive. I did not see this happening in RC-13, it started for me when I upgraded to RC-14, and doing a fresh install of RC-14. I just upgraded to RC-15 from RC-14 hoping it would fix it after reading your post. Mine does this for both registered and unregistered hosts, any recommendations?
Ubuntu 16.04
Fog Running Version 1.3.0-RC-15 upgraded from a fresh install of RC-14 -
@FlareImp Because you did a “fresh” install from RC-14, moving to 15 would not fix the issue.
You would need to run:
mysql -u root drop database fog; exit exitRe-run the installer.
If you have hosts, images, etc… make a backup of these definitions as you will be starting from scratch essentially.
-
@Tom-Elliott Awesome response time! I’ll give that a try now, thank you!
-
@Tom-Elliott said in Want to skip "Booting... (Press Escape to access the menu)":
mysql -u root
drop database fog;
exit
exitAll fixed, Thanks so much!
-
@FlareImp Sorry for giving you an incomplete answer before. I thought you revered and installed 1.2.0 which would upgrade to RC15 without issue. There would be no need to drop the database in this case.
I’m glad you have it all sorted out. The 1.3.0RC series is so much better than 1.2.0. You will be glad you are on this release.
