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

    Certain machines not PXE booting after upgrade

    Scheduled Pinned Locked Moved
    FOG Problems
    3
    7
    3.3k
    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.
    • S
      scottmcmullan8
      last edited by

      Hi,

      Upgraded from fog 0.3.x to fog 1.1.2 - so far any issues have been solvable. Everything has now been set up and configured as I would want in my environment. The final issue that is happening now is that certain machines are unable to PXE boot that previously had no issues. Testing in same lab environment with 3 different machines:
      Dell OptiPlex, Viglen and a Shuttle.

      The Dell and Shuttle machines PXE boot without issue. I can then either perform full host registration or manually add in the mac address in fog to get the image to deploy.

      However the Viglen machines (which previously PXE booted on fog 0.3.x using pxelinux.0) no longer are working as should. I have received various different error messages. Sometimes it will get to the fog menu but then when trying to send the image it will display only a blinking cursor and not get any further just every couple of seconds will have another _ displayed and move further down the screen. Sometimes it will then come up saying no dhcp offers received or reopening network devices. Then I have also seen the error message displayed DHCP boot not for us. I am at a loss to why this is happening apart from the fact that maybe the network card or boot options are too far outdated for the new method being use for PXE?

      Any help would or advice would be appreciated.

      Thanks

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

        Have you tried other undionly/ipxe files?

        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
        • S
          scottmcmullan8
          last edited by

          Do you mean changing the options to boot from IPXE.PXE or UNDIONLY.KPXE etc.?

          I have changed this and tried a few different ones (all that came with the install of fog) and same result unfortunately. Last working method was the pxelinux.0 for these machines. Are there some older machines which these files are not compatible?

          1 Reply Last reply Reply Quote 0
          • S
            scottmcmullan8
            last edited by

            Have changed the options from Ipxe.pxe and nothing being received at all for the Viglen however the Shuttle and Dell get to Fog menu stage and can image fine. Changed back to Undionly.kpxe and the Viglen then gets to the fog menu and when I select perform full host registration I then get the loading bzimage etc. before screen changes to black with cursor blinking on the screen and that’s as far as it gets. 😞

            1 Reply Last reply Reply Quote 0
            • S
              scottmcmullan8
              last edited by

              Also as a follow up on this.

              Another machine that we have tested that is not working (black screen blinking cursor or reopening network devices or no DHCP offers received) is the Fujitsu ESPRIMO Q530E. So now we have the Fujitsu and Viglen machines not able to deploy image.

              However we have Shuttle PCS and Dell OptiPlex machines that we are able to send an image to using same network port and same configurations.

              Really not sure of any way around this after changing the boot file from ipxe.pxe, undionly.kpxe and the other options nothing seems to work.

              Any one else experienced this?

              1 Reply Last reply Reply Quote 0
              • S
                scottmcmullan8
                last edited by

                Another update - it appears when the machines that aren’t working are trying to PXE boot they are using Intel Boot Agent Version 1.3.24 however the machines that are working are using a Intel PXE boot agent?

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

                  [quote=“scottmcmullan8, post: 33863, member: 24964”]Another update - it appears when the machines that aren’t working are trying to PXE boot they are using Intel Boot Agent Version 1.3.24 however the machines that are working are using a Intel PXE boot agent?[/quote]

                  Look for Bios Updates/Firmware updates for the machines and see if that has any affect.

                  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

                  159

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project