• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    PXE Boot Problems after upgrade to 1.0.1

    Scheduled Pinned Locked Moved
    FOG Problems
    4
    10
    3.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • hariskarH
      hariskar
      last edited by

      Everything was working fine with 0.32.
      Now I have PXE boot problems:
      TFTP.
      PXE-T01: File not found
      PXE-E3B: TFTP Error - File not found
      PXE-M0F: Exiting PXE ROM.

      I made a clean installation, but the problem still exists. Any help please?
      Thank you

      1 Reply Last reply Reply Quote 0
      • Jaymes DriverJ
        Jaymes Driver Developer
        last edited by

        [quote=“hariskar, post: 28848, member: 24448”]Everything was working fine with 0.32.
        Now I have PXE boot problems:
        TFTP.
        PXE-T01: File not found
        PXE-E3B: TFTP Error - File not found
        PXE-M0F: Exiting PXE ROM.

        I made a clean installation, but the problem still exists. Any help please?
        Thank you[/quote]

        Did you change option 067 to the current bootfile as instructed by the installer? Latest versions of FOG use the iPXE system and undionly.kpxe to serve the boot menu and options as opposed to the 0.32 version of pxe which used the pxelinux.0 file.

        Sorry it was early morning and I made type-o, I have fixed it!!!

        WARNING TO USERS: My comments are written completely devoid of emotion, do not mistake my concise to the point manner as a personal insult or attack.

        1 Reply Last reply Reply Quote 0
        • hariskarH
          hariskar
          last edited by

          No, I did not change anything. Which file should I change? Fog is on lubuntu. (newbie here)
          I use my Tomato router for dhcp service.
          Thank you for instant reply!

          1 Reply Last reply Reply Quote 0
          • Jaymes DriverJ
            Jaymes Driver Developer
            last edited by

            [quote=“hariskar, post: 28850, member: 24448”]No, I did not change anything. Which file should I change? Fog is on lubuntu. (newbie here)
            I use my Tomato router for dhcp service.
            Thank you for instant reply![/quote]

            You will edit the settings in Tomato, if available, if not you can use a DNSMASQ service to dole out dhcp information during pxe boot and to help resolve your boot file, for now, look at the settings in Tomato and see if you can’t find a setting for next-server (option 066), which will need to be set up as your FOG server ip address, and also look for the boot file name (option 067) which will need to be pointed at the undionly.kpxe file.

            WARNING TO USERS: My comments are written completely devoid of emotion, do not mistake my concise to the point manner as a personal insult or attack.

            1 Reply Last reply Reply Quote 0
            • B
              Baite
              last edited by

              I had the same problem. Fixed it replacing undionly.kpxe with the one found in undionly.kpxe.INTEL
              (rename undionly.kpxe to undionly.kpxe.ORIGINAL and then copy undionly.kpxe.INTEL to undionly.kpxe)

              I also changed option 67 filename in my DHCP server.

              1 Reply Last reply Reply Quote 0
              • hariskarH
                hariskar
                last edited by

                I replaced in [CODE]dhcp-boot=pxelinux.0,192.168.1.5[/CODE] pxelinux.0 with undionly.kpxe in Tomato router in DNSMASQ service field and now everything is OK! Thank you!!

                1 Reply Last reply Reply Quote 0
                • Tom ElliottT
                  Tom Elliott
                  last edited by

                  Glad you figured this out.

                  If you want, you can assign a hostname as well, by assigning the line as:
                  [code]dhcp-boot=undionly.kpxe,fogserver,192.168.1.5[/code]

                  I run dd-wrt but the methodology in assigning “option 67” is the exact same.

                  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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                  Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                  Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                  1 Reply Last reply Reply Quote 0
                  • hariskarH
                    hariskar
                    last edited by

                    Thank you Tom. Everything is fine now, will I gain something by assigning a hostname? (I can’t find any advantage with my limited knowledge)

                    1 Reply Last reply Reply Quote 0
                    • Tom ElliottT
                      Tom Elliott
                      last edited by

                      No, but it’s good to have so people aren’t staring at code thinking the problem is missing text.

                      In programming, typically it’s syntactically incorrect to have dhcp-boot=,

                      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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                      1 Reply Last reply Reply Quote 0
                      • Jaymes DriverJ
                        Jaymes Driver Developer
                        last edited by

                        [quote=“Tom Elliott, post: 28975, member: 7271”]No, but it’s good to have so people aren’t staring at code thinking the problem is missing text.

                        In programming, typically it’s syntactically incorrect to have dhcp-boot=,[/quote]

                        In some systems when using DNSMASQ you have to leave that field blank, like novell. If you supply the FOG host server name, the file will fail to resolve. I should have left a place holder in the documentation that explained that the blank is for the host name but I didn’t know it was going to drive you insane lol

                        WARNING TO USERS: My comments are written completely devoid of emotion, do not mistake my concise to the point manner as a personal insult or attack.

                        1 Reply Last reply Reply Quote 0
                        • 1 / 1
                        • First post
                          Last post

                        198

                        Online

                        12.0k

                        Users

                        17.3k

                        Topics

                        155.2k

                        Posts
                        Copyright © 2012-2024 FOG Project