• 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
    4.9k
    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

      i’ve heard that some pxe clients (especially old ones) have problems with filenames longer than the old 8.3 limit (8 characters, a period, and a 3 letter extension, like DOS), but it’s uncommon enough that i haven’t seen it myself.

      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
      • Y
        yochaigal
        last edited by

        Thanks everyone for the replies - I will follow some of your suggestions as soon as I am able - unfortunately I woke sick this AM so it won’t be until tomorrow!

        I really appreciate the help - what a great project!

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

          I’ve attached the tcpdump file - wireshark tells me that you’re right on the money, though:

          0_1463149698271_too_long.pcap

          I also tried changing the undionly.kpxe file to just u.kpxe (and updated my dhcp server) but had the same result; is there something else I need to do when changing the name?

          Thanks

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

            @yochaigal u.kpxe still has 4 characters after the period, that may be causing issues if it’s trying to adhere strictly to 8.3 format (disclaimer: i haven’t looked at the pcap file)

            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 Oh right, that makes sense!

              Well, I changed the name to undionly.pxe (8.3) - same issue. Uploaded new pcap file.
              0_1463151170763_too_long.pxe.pcap

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

                @yochaigal Can you check for a firmware update for this troublesome target host?

                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/

                Y 1 Reply Last reply Reply Quote 1
                • 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

                                    228

                                    Online

                                    11.6k

                                    Users

                                    17.1k

                                    Topics

                                    154.6k

                                    Posts
                                    Copyright © 2012-2024 FOG Project