Host won't boot in PXE



  • I’m new to FOG, just installed it today. Correct me if I’m wrong, but my understanding is that I need to boot the computer I wish to use as a host in PXE, register it for client use, then log in to my server and create an image and a host, and assign that image to the host, then log in to my server on another computer and begin to upload the image. I have a couple problems.

    1. The computer I am using as a test host will not boot into PXE. I have enabled 66 and 67 on the DHCP server, FOG is not running as a DHCP server, I have upgraded the BIOS, and I have PXE set as the first boot option. When I try booting, it returns nothing for TFTP and hangs on DHCP for a while. It then exits PXE and boots Windows.
    2. When attempting to upload my image, it hangs in queue and goes nowhere, but I think that’s due to number 1.

    Thanks in advance for any help you can provide!

    FOG Version: 1.01
    OS: Ubuntu 14.04 LTS
    [URL=‘http://pastebin.com/Jzgf5vTd’]Here[/URL] is my Apache log. I think the important thing here is about half way down (line 16):
    "
    [LIST=1]
    [][COLOR=#000000]ls: cannot access /images/test: No such file or directory[/COLOR]
    [
    ][COLOR=#000000]ls: cannot access /images/testestest: No such file or directory[/COLOR]
    [][COLOR=#000000]ls: cannot access /images/testimg: No such file or directory[/COLOR]
    [
    ][COLOR=#000000]ls: cannot access /images/testimg2: No such file or directory[/COLOR]
    [][COLOR=#000000]ls: cannot access /images/test: No such file or directory[/COLOR]
    [
    ][COLOR=#000000]ls: cannot access /images/testestest: No such file or directory[/COLOR]
    [][COLOR=#000000]ls: cannot access /images/testimg: No such file or directory[/COLOR]
    [
    ][COLOR=#000000]ls: cannot access /images/testimg2: No such file or directory[/COLOR]
    [][COLOR=#000000]ls: cannot access /images/test: No such file or directory[/COLOR]
    [
    ][COLOR=#000000]ls: cannot access /images/testestest: No such file or directory[/COLOR]
    [][COLOR=#000000]ls: cannot access /images/testimg: No such file or directory[/COLOR]
    [
    ][COLOR=#000000]ls: cannot access /images/testimg2: No such file or directory[/COLOR]
    [/LIST]
    [FONT=Consolas][COLOR=#000000][SIZE=12px]"[/SIZE][/COLOR][/FONT]


  • Developer

    If you read during the install of fog it tells you do do this. That is direct documentation.

    Would you just keep clicking next in an install of Java and install all the extra crap that comes along for the ride? No you untick the extras and just install java. Same goes for any other install. [SIZE=4][I][U][B]Read the output.[/B][/U][/I][/SIZE]



  • [quote=“BPSTravis, post: 27852, member: 22444”]Option 67 needs to be undionly.kpxe for any fog version past .32(AKA 1.0.1) If you installed Today, i’m assuming you installed 1.0.1.[/quote]
    [B]Where is this documented?[/B] No wonder I am not able to connect I never changed the prelinux.0. Is it any wonder there is frustration??? I just checked the wiki again and the only pages I could find all talk about older versions of FOG. The managing Fog page is version 0.29.



  • Ok, well I got some computers to boot in to FOG, but not others. Any suggestions?



  • [quote=“Tom Elliott, post: 27925, member: 7271”]Are you trying to upload or download an image?[/quote]

    And Upload, I guess, would be the answer there.



  • I’m currently trying to get to the host registry. So far I have not made it to that part.

    I just update undionly.kpxe to 1312 like you suggested. Waiting to see how that goes


  • Senior Developer

    [quote=“Jordon Rapp, post: 27923, member: 24302”]Ok, well good news and bad news. I got rid of the m0f error, which brought me to a PXE error, which was fixed by replacing undionly.kpxe with ipxe.pxe (per Tom’s suggestions here: [url]http://fogproject.org/forum/threads/040ee119-error-on-boot.10493/page-2[/url]) But now the FOG GUI appears and then quickly disappears and the maching boots into Windows.[/quote]

    Are you trying to upload or download an image?



  • Ok, well good news and bad news. I got rid of the m0f error, which brought me to a PXE error, which was fixed by replacing undionly.kpxe with ipxe.pxe (per Tom’s suggestions here: [url]http://fogproject.org/forum/threads/040ee119-error-on-boot.10493/page-2[/url]) But now the FOG GUI appears and then quickly disappears and the maching boots into Windows.



  • No, you had every right, that is my fault. The good news on the fog front is that I now need to figure out how to update my PXE…


  • Developer

    sorry to come down on you, it’s just hard enough to keep up without double postings.


  • Developer

    well, it kind of was, but the proper etiquette would be to either ask for the thread to be moved, or to post in your thread about how you have moved the conversation to a new thread.



  • Oh sorry, I thought maybe that other one was in the wrong place. My bad :/


  • Developer

    is there a reason you created a new thread instead of continuing the other one you started with the same statement?
    [url]http://fogproject.org/forum/threads/host-wont-boot-in-pxe.10582/[/url]



  • Darn, I knew that too. Let me change that and see where I get


  • Developer

    [QUOTE]67 is set to pxelinux.0[/QUOTE]

    Option 67 needs to be undionly.kpxe for any fog version past .32(AKA 1.0.1) If you installed Today, i’m assuming you installed 1.0.1.



  • Sorry, the word ‘here’ is a link to Pastebin with my Apache log. I have 66 and 67 both enabled. 66 is pointed to the ip of my fog server (172.16.0.35) and 67 is set to pxelinux.0

    Yes it does. It will take a while on DHCP then return 172.16.1.8 (My DHCP server), then It skip to “PXE-M0F - Exiting Intel Boot Agent”, then starts Windows normally


  • Developer

    I only see up to line 12 in your error log.

    What did you use for DHCP 66/67 settings?

    Does the machine ever get an IP address when PXE booting? if not it’s a network issue long before FOG is involved.


Log in to reply
 

364
Online

38982
Users

10712
Topics

101679
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.