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

    "PXE-T00: File name too long" on some machines

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    6
    20
    5.2k
    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.
    • JunkhackerJ
      Junkhacker Developer
      last edited by

      could you try renaming the file to undionly.0 ?

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

      Y 1 Reply Last reply Reply Quote 1
      • Y
        yochaigal @Junkhacker
        last edited by

        @Junkhacker Done. Same problem:
        0_1463154351281_undionly.0.pcap

        1 Reply Last reply Reply Quote 0
        • Y
          yochaigal @Wayne Workman
          last edited by

          @Wayne-Workman I already did - it is using the “latest” release (late 2011).

          http://support.lenovo.com/us/en/products/Laptops-and-netbooks/Lenovo-V-Series-laptops/Lenovo-V570-Notebook/1066/A9U/downloads/DS027341

          1 Reply Last reply Reply Quote 0
          • Y
            yochaigal
            last edited by

            Here’s a more general question:

            I’ve setup FOG for my computer repair business; we install Win/Mac/Linux on a daily basis on all sorts of different hardware scenarios; we were originally looking into MDT until I found this amazing FOSS solution, that so far works great!

            However, In instances where I’m dealing with different hardware on a regular basis, what is the best “fallback” scenario? Is there an alternative PXE booting utility I could use in these cases? I’ve already tried PLOP but had the same issue.

            Thanks

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

              you could try this http://ipxe.org/download
              burn to cd or make a usb boot drive. this will load an ipxe network boot rom into memory and boot to it, instead of the network card’s onboard boot rom

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

              Y 1 Reply Last reply Reply Quote 1
              • Y
                yochaigal @Junkhacker
                last edited by

                @Junkhacker Yeah, this totally worked! That’s really all I need; I doubt I’ll see another of these machines for some time.
                Thanks so much you guys! Consider this thread solved. I really appreciate how quickly people here responded; I’ll try to help others in turn (at least, as much as I can!).

                1 Reply Last reply Reply Quote 2
                • S
                  Sebastian Roth Moderator
                  last edited by Sebastian Roth

                  Great to hear that you guys found a workaround to this. Thanks a lot for the pcap file anyway. It actually shows exactly what the error message is saying. I wouldn’t believe it if it wasn’t in the pcap! That machine is requesting not just undionly.kpxe but undionly.kpxe\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377....
                  Looks like it’s padding the string with EOL (end of line) symbols. I have no idea why that is. If PXE booting is working fine for you with all the other machines you are perfectly fine with booting this one via the iPXE cd image! Don’t bother about it.

                  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 2
                  • P
                    piercerob
                    last edited by

                    Simple solution to file name too long is Long Path Tool.

                    1 Reply Last reply Reply Quote 0
                    • S
                      Sebastian Roth Moderator
                      last edited by

                      @piercerob Can you explain what you mean? From my point of view there is no simple tool that can help you fix this.

                      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

                      Y 1 Reply Last reply Reply Quote 0
                      • Y
                        yochaigal @Sebastian Roth
                        last edited by

                        @sebastian-roth I worked around the issue using an iPXE boot ISO.

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

                        201

                        Online

                        12.0k

                        Users

                        17.3k

                        Topics

                        155.2k

                        Posts
                        Copyright © 2012-2024 FOG Project