TFTP Problems
-
Not sure if it was already mentioned, didnt see it in a quick scan but I had a similar issue. Make sure that DHCP Option 66 and 67 are enabled. 66 should be the IP address of your FOG server and 67 should be your undionly.kpxe file.
I struggled with it for a couple of hours, hopefully it helps you out.
-
So today I tryed call the company that takes care of the dhcp server and I don’t know what they did but I got one step forward in the fog server. know I get the following messeges:
PXE - EB: !PXE at 9B85:0070, entry at 9B85:0106
UNDI code segment 9B85:4120, data segment 9552:6330
UNDI device is PCI 00:19.0, type DIX+802.3then i get:
iPXE initialising devices…
Then:
iPXE initialising devices…ok
iPXE 1.0.0+ (3a02) – Open Source Network Boot Firmeware – http://ipxe.org
Features: NFS FTP HTTP HTTPS ISCSI DNS TFTP VLAN AoE bzimage ELFMBOOT PXE PXEXT
Configuring (net0 00:22:64:ba:2b:56)…and the the computer resarts and nothing
now what is wrong!!! -
@bacelo Well on the plus side your target computer is reaching a tftp server and downloading a iPXE boot kernel AND you got past the initializing devices. This is great!! The problem is the spontaneous reboot. This of course is unexpected.
Right after the “Configuring (net0 00:22:64:ba:2b:56)” it should boot into the FOG menu. From the MAC address I see this is a HP computer. What is the model # and what mode is it in, BIOS or UEFI? The undionly.kpxe is for BIOS mode computers. (Actually as I think about it, you would not get this far if you sent the computer the wrong ipxe kernel.
BUT you are having success and getting very close.
-
@george1421 the model is dc7800p how do I see if it’s on BIOS or UEFI??
-
Could it be that the boot file has any problem how can I see if everything is correct with it!??
-
@bacelo said:
iPXE initialising devices…ok
iPXE 1.0.0+ (3a02) – Open Source Network Boot Firmeware – http://ipxe.org
Features: NFS FTP HTTP HTTPS ISCSI DNS TFTP VLAN AoE bzimage ELFMBOOT PXE PXEXT
Configuring (net0 00:22:64:ba:2b:56)…Shortly after this part is when the kernel and init are downloaded.
Those are stored on the FOG server here:http://x.x.x.x/fog/service/ipxe/
The local path to them on CentOS 7 / Fedora would be:/var/www/html/fog/service/ipxe/This is what mine looks like:
Make sure those files exist. If they aren’t there or the file sizes look weird, re-run the fog installer.
Turn your firewall off for testing purposes.
CentOS 7 / Fedora:systemctl stop firewalld
Set SELinux to permissive for testing purposes.
CentOS 7 / Fedora:setenforce 0Try again.
If you have no luck then, then just re-run the fog installer and see what that does.
Also - a packet capture from the FOG Server during the attempted network boot would be really helpful.
-
@Wayne-Workman from what I can see I am missing the last two files.
-
@bacelo Well, I’m running FOG Trunk and you’re running 1.2.0 right? So it won’t be entirely the same.
-
@bacelo What you need to make sure is the bzImage files and in the init.xz files exist in this location. This part I’m a bit fuzzy on, since I don’t have a FOG server in front of me right now. I think the next thing that should load is the PXE menu. The linux kernel and inits are loaded once you make a selection on the pxe menu.
does the following url generate a text file (actually the pxe menu)
http://<fog_server_ip>/fog/service/ipxe/boot.php
(I did that from memory so it might be wrong) but once the ipxe kernel is loaded it should try to load the default.pxe config file that is redirected to the URL above. That is what creates the ipxe menu. Again I’m doing this from memory and the egg nog may be impacting what I thought I knew.
-
Ok so I got to this point and all the files are there I reinstalled linux and Fog server and it does the same when it should boot the menu the pc just restarts.
-
does the screen, during bootup, remain black for a long time? You don’t see the menu, or the menu times out before you see it? This is an important distinction.
-
@Tom-Elliott No, this appears:
iPXE initialising devices…ok
iPXE 1.0.0+ (3a02) – Open Source Network Boot Firmeware – http://ipxe.org
Features: NFS FTP HTTP HTTPS ISCSI DNS TFTP VLAN AoE bzimage ELFMBOOT PXE PXEXT
Configuring (net0 00:22:64:ba:2b:56)…
then it just restarts the pc. I am going to update the Bios to see if it could be something with the Bios. Other then that I just don’t know what to do or how to see if everything is correct with the boot file. -
@bacelo Are you willing to try trunk?
I think you’re seeing the “console” error that 1.2.0 users often times had.
-
@Tom-Elliott So what sould I do to fix that??
-
@Tom-Elliott I am willing to try anything to make this work
-
@bacelo Can you hit me up in chat?
I can maybe teamviewer?
-
@Tom-Elliott can it be in 1 hour you would save my life
-
it sure can be.
-
OK thanks to Tom Elliott I got the fog server to work kind of the only thing that is missing is on booting the network card it loses the connection to the lan link card and I have to press S and type dhcp and it gets back up and then o type exit and the menu boots up. The problem is that I have to be physically at the client PC for this to work so if I were to deploy the software it won’t go because I have to press S DHCP and then exit and then it will pop up the menu
-
@bacelo We’ve reworked the iPXE script lately. Seams like you are in a (DHCP) situation where our script does not properly work. Sounds like an interesting issue. Have you tried activating port fast setting on the switch? I guess Tom has talked about this as well.
Could you please take a picture with your smartphone of all the messages you see and the keys/commands you use to get to the boot menu? To me this sounds like a “timing” issue. When booting up the script does pretty much that (dhcp command). So I wonder why it works when you do this by hand.
