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

    iPXE input/output error (since update SVN 7687)

    Scheduled Pinned Locked Moved Solved
    Bug Reports
    3
    7
    1.4k
    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.
    • H
      hernani
      last edited by

      Hi,

      Using FOG in my university. Until last week we used 1.2.0 (and everything was great) but because of incompatibility with new hardware (DELL Optiplex 7040, Dell AIO 7440), we had to move the server from 1.2.0 to SVN.
      It seems to be the only solution for our new hardware work with FOG, according many of the posts.

      After the update to SVN last friday, no longer renaming of our clients, and following the posts here, we updated again our server this morning. BUT since, it’s worse…
      No reaction on the menu and the same error as in this post appears:

      https://forums.fogproject.org/topic/5510/svn-ipxe-input-output-error

      What happens during the update? Which files changed during the update?

      our clients are in legacy mode, pointing to undionly.kpxe.

      thx

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

        Since update 7687?

        7687 wasn’t released until this morning. There is no possible way that you could’ve had these issues last week under this version.

        Because of the error, what’s in your apache error logs?

        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

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

          Found the issue and it is now corrected for in the latest pull (7691 now).

          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
          • george1421G
            george1421 Moderator @hernani
            last edited by

            @hernani said:

            Using FOG in my university. Until last week we used 1.2.0 (and everything was great) but because of incompatibility with new hardware (DELL Optiplex 7040, Dell AIO 7440), we had to move the server from 1.2.0 to SVN.

            Just for confirmation here, the above is true statement. You need to the FOS (the Fog Operating System that captures and deploys images on the target computers) kernels for new hardware support. These kernels are not available for 1.2.0 stable. If you plan on deploying win10, gpt disks, or uefi firmware you also need 1.2.0 trunk because the trunk version supports these features much better than 1.2.0 stable. So when you get there the trunk version gives you better client environment support all around.

            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
            • H
              hernani
              last edited by

              Solved thx to SVN 7695 😉

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

                Marking this thread solved.

                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
                • H
                  hernani @Tom Elliott
                  last edited by

                  @Tom-Elliott
                  Indeed, last week was 7575 i think (but not sure) but now everything is ok.

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

                  149

                  Online

                  12.1k

                  Users

                  17.3k

                  Topics

                  155.3k

                  Posts
                  Copyright © 2012-2024 FOG Project