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

    iPXE fog boot menu error Could not boot: Results too large

    Scheduled Pinned Locked Moved Unsolved
    FOG Problems
    2
    4
    66
    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
      Jias94
      last edited by

      I think it’s about time I come to the forums for help. Recently I’ve upgraded our Master Fog server to 1.5.10.1660 using the fog kernel 6.6.69 and using Ubuntu 24.04.2 LTS version.

      A few days ago, I wanted to try and implement HTTPS for the master fog server and the storage nodes. The upgrade went well and everything was working just fine except for a few driver issues with the keyboard not working during the fog boot menu for certain models of computers we have, but that is a different problem.

      My main problem now is that every time I try and get to the fog boot menu, I get an error: “Could not boot: Results too large.” I have since rebuilt the binaries for iPXE, reinstalled fog a few times with HTTPS enabled, Reinstalled fog without HTTPS enabled, rebuilt the fog master from the ground up and I’m still getting this error. I even tried using chatGPT just to see what it would recommend, but it wanted me to completely redo the boot.php file. The two things I haven’t tried diving into was seeing if there are any residual iPXE stuff for HTTPS in the fog database ( which I don’t think there are any iPXE info stored in the database? ) and reinstall the storage nodes from the ground up. Fog boot menu error.png

      Here are the the amount of storage nodes we have currently connecting to the master node:
      Storage Nodes.png

      The amount of storage nodes might be irrelevant to the problem I’m having, but I’m grasping at straws here. I haven’t tried it yet but if I were to create a task for existing hosts on fog it would deploy an image just fine or capture an image. However, registering new hosts through the fog boot menu isn’t an option until this gets resolved.

      Any amount of suggestions or help would be much appreciated!

      george1421G 1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator @Jias94
        last edited by george1421

        @Jias94 Where I’ve seen this before is in a custom fog menu. The menu id has a minus sign in it and ipxe is thinking its a command not an id. Somewhere around the choose command its getting hung up.

        So how do you find this? Using a web browser and access the ipxe menu at http://<fog_server_ip>/fog/service/boot.php You need to replace <fog_server_ip> with the correct ip address. Since you are messing with https, you may need to change that so. You should end up with a screen full of text that makes up the ipxe menu. Looks for things you have entered that have a minus sign. If you can’t find it post the entire content of the ipxe menu here and we will take a look for you. But I would focus your attention around the choose command, one of its entries as a dash where it thinks is an internal command to the menu

        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!

        J 1 Reply Last reply Reply Quote 1
        • J
          Jias94 @george1421
          last edited by

          @george1421 Thanks for the reply! It was something to do with the custom boot menu. Shortly after I made this post and I had my team meeting. One of my co-workers admitted that he was explaining how to make a custom boot option to our field techs and got distracted and forgotten to add the parameters to the custom boot menu. He was going to delete it afterwards but yet again forgot to do it.

          I feel embarrassed as I saw that menu item multiple times, but it didn’t click that it was missing some important information to make it work properly… I’ve since removed the broken menu item and the boot menu works as intended.

          george1421G 1 Reply Last reply Reply Quote 0
          • george1421G
            george1421 Moderator @Jias94
            last edited by

            @Jias94 Hey no worries, I’ve created that error a few times myself so I had a good idea where to look. I’m glad you have it sorted out and can get back to imaging.

            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!

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

            179

            Online

            12.1k

            Users

            17.3k

            Topics

            155.3k

            Posts
            Copyright © 2012-2024 FOG Project