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

    TFTP PXE boot timing issue Could not start download: Operation not supported

    Scheduled Pinned Locked Moved
    FOG Problems
    4
    14
    8.8k
    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
      subtitling
      last edited by

      Installed the latest FOG 1.0.1 on Ubuntu 14.02 LTS using all the defaults advised. When we PXE boot to inventory a computer, we get an error: [B]Could[/B][B] not start download: Operation not [/B][B]supported[/B]

      If I pause at the point where it shows:[B] iPXE 1.0.0+(d28b) – Open Source Network Boot Firmware – Features: NFS HTTP HTTPS iSCSI DNS TFTP AoE bzImage ELF NBOOT PXE PXEXT Menu Configuring (net0 [I]my MAC address[/I])… [/B]then escape; I see the ‘FOG PXE menu’ as expected…

      This implies a timing issue. We have experienced this on several platforms, and despite not seeing anyone on here complaining of this, wonder if there might be a bug, or a TFTP setting that needs to be changed?

      Any help appreciated as this has caused as a considerable amount of wasted time. We didn’t have this problem on previous versions of FOG. Those version worked ‘out of the box’ with minimal changes.

      Many thanks in advance.

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

        This post is deleted!
        1 Reply Last reply Reply Quote 0
        • V
          vaughna
          last edited by

          I am having the same problem. Ever since I updated to 1.0.1 I have not been able to boot. I get the error e3b.

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

            Yes, this is so frustrating. 0.32 was easy, but this has cost me many hours now, and I only found it by chance. I tried to pause the screen to see the error, and when I escaped I saw the PXE menu.

            I think I’m going to have to use an alternative solution, my Linux skills are clearly not up to scratch. Life is too short. 😞

            1 Reply Last reply Reply Quote 0
            • V
              vaughna
              last edited by

              This fixed my problem: Option 67 should be pointing at: undionly.kpxe

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

                Thanks for that, but we are using the FOG server as the DHCP, but this isn’t our problem; if I pause the screen for a moment, it all works OK.

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

                  I’m going to be taking a look at the source code for how it goes into configuring and seeing if I can make a pause of about 3 seconds to hopefully “fix” the timing issue being reported. We know it’s a timing issue, but I’m not in charge of the ipxe source code. If this delay fixes it, maybe I can post it to somebody who’s willing to commit the change into the official source.

                  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
                    subtitling
                    last edited by

                    Thanks for posting Tom.

                    1 Reply Last reply Reply Quote 0
                    • JunkhackerJ
                      Junkhacker Developer
                      last edited by

                      [url]http://fogproject.org/forum/threads/040ee119-error-on-boot.10493/[/url]
                      thank you for your bug report. we now believe we have a fix.

                      signature:
                      Junkhacker
                      We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

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

                        Just an update to explain that this hasn’t fixed the issue, and I still have the same error. This wasn’t an issue with 0.32 and the same hardware.

                        Thanks.

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

                          [url]http://fogproject.org/forum/threads/040ee119-error-on-boot.10493/[/url]

                          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
                            subtitling
                            last edited by

                            Sadly, ipxe.kpxe or ipxe.kkpxe haven’t fixed the issue, so I’m relying on my ‘pause’ method for the moment. Using ipxe.kkpxe renamed to undionly.kpxe caused a red screen of death with an illegal upload message.

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

                              Interestingly, we tried to use our setup to image a VM and we get the same error as the OP.

                              Due to time constraints, we are going to retrograde to 0.32 (on another server hosting[COLOR=black]FOG[/COLOR]), but format the node to be cloned with Ext3… and hope that works OK!

                              Nevertheless, thank you for your effort in this.

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

                                We continue to face hurdles, but 12.04 with FOG 0.32, grub (not grub2) seem to work with DL360e Gen8, although we now have to figure out how to avoid eth0 disappearing after cloning.

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

                                182

                                Online

                                12.0k

                                Users

                                17.3k

                                Topics

                                155.2k

                                Posts
                                Copyright © 2012-2024 FOG Project