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

Host does not boot into PXE after reboot

Scheduled Pinned Locked Moved
Windows Problems
3
7
1.7k
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.
  • J
    Joe Gill
    last edited by Aug 11, 2016, 4:07 PM

    I’m running the new RC-8 release of FOG… I noticed this issue a couple weeks ago after I upgraded our server. I have had several hosts that will not boot up into FOG after reboot. I have added these hosts either via quick add or via perform full host registration in the PXE boot. I checked all the parameters in the BIOS and everything is just like I have set them up before. I have things set to boot Network boot into PXE. I have all my other power settings adjusted in the BIOS as well. I have had issues with new and old machines. The two primary culprits are Dell 3020’s and Dell 380’s. I also tried updating to the latest version of the BIOS with little success.

    Any ideas would be very helpful. In the past the 3020’s booted into PXE just fine after I made my BIOS setting adjustments.

    Thanks!!

    Cheers,

    Joe

    1 Reply Last reply Reply Quote 0
    • W
      Wayne Workman
      last edited by Aug 11, 2016, 4:09 PM

      If the computer is shut down and then turned on, does it boot to the network first?

      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!
      Daily Clean Installation Results:
      https://fogtesting.fogproject.us/
      FOG Reporting:
      https://fog-external-reporting-results.fogproject.us/

      J 1 Reply Last reply Aug 11, 2016, 4:11 PM Reply Quote 0
      • J
        Joe Gill @Wayne Workman
        last edited by Aug 11, 2016, 4:11 PM

        @Wayne-Workman No. The other admin thought that would make a management nightmare so I decided against it. Although I’m learning lots this Summer on what the Best Practice’s is versus what the other admin thinks. LOL!

        1 Reply Last reply Reply Quote 0
        • W
          Wayne Workman
          last edited by Aug 11, 2016, 4:12 PM

          If it doesn’t try to boot to the network from an “off” state, the problem is your boot order in firmware.

          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!
          Daily Clean Installation Results:
          https://fogtesting.fogproject.us/
          FOG Reporting:
          https://fog-external-reporting-results.fogproject.us/

          J 1 Reply Last reply Aug 11, 2016, 4:15 PM Reply Quote 0
          • J
            Joe Gill @Wayne Workman
            last edited by Aug 11, 2016, 4:15 PM

            @Wayne-Workman Ok. I’ll re-think this. I know it has worked for me in the past. Although that may be due to the boot order like you said. When I first started this process, some had the network as first boot. Then I adjusted things after the other admin complained. Hmmm…

            Thanks!!

            B 1 Reply Last reply Aug 11, 2016, 4:16 PM Reply Quote 0
            • B
              BedCruncher @Joe Gill
              last edited by Aug 11, 2016, 4:16 PM

              @Joe-Gill
              I would suggest setting network boot as first priority and then setting a timeout of 5 seconds on the menu so that if there is no task, then at most your boot time is impacted maybe 40 seconds.

              W 1 Reply Last reply Aug 11, 2016, 4:17 PM Reply Quote 0
              • W
                Wayne Workman @BedCruncher
                last edited by Aug 11, 2016, 4:17 PM

                @BedCruncher said in Host does not boot into PXE after reboot:

                @Joe-Gill
                I would suggest setting network boot as first priority and then setting a timeout of 5 seconds on the menu so that if there is no task, then at most your boot time is impacted maybe 40 seconds.

                You can also “hide” the fog boot menu. It’s an option inside Web Interface -> FOG Configuration -> iPXE Boot Menu

                There’s also the “no menu” option.

                There’s a hide timeout, and a regular timeout. The regular time out applies when hiding isn’t being used.

                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!
                Daily Clean Installation Results:
                https://fogtesting.fogproject.us/
                FOG Reporting:
                https://fog-external-reporting-results.fogproject.us/

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

                202

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project