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

    mounting /images failed: Connection timed out

    Scheduled Pinned Locked Moved
    FOG Problems
    3
    81
    32.7k
    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.
    • george1421G
      george1421 Moderator @sjensen
      last edited by george1421

      @sjensen OOoops you fell into the kernel hole. The kernels between 4.2 and 4.6 don’t work for FOG 1.2.0, if you upgrade to latest kernels for FOG 1.3.0 you will be in a better state.

      cd /var/www/html/fog/service/ipxe
      cp bzImage bzImage.old
      cp bzImage32 bzImage32.old
      wget -P https://fogproject.org/kernels/bzImage
      wget -P https://fogproject.org/kernels/bzImage32
      

      Now here is the part I’m not sure of, and Tom will need to answer. I was under the impression that FOG 1.2.0 was 32bit only? if that’s the case we need to rename the kernel file

      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!

      Tom ElliottT 1 Reply Last reply Reply Quote 1
      • S
        sjensen @Tom Elliott
        last edited by

        @Tom-Elliott this is what got
        mount: cant find images: in /etc/fstab

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

          @sjensen I need to see the exact mount command you used.

          The command should not run multiple lines.

          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
          • Tom ElliottT
            Tom Elliott @george1421
            last edited by

            @george1421 1.2.0 (1.0.0 and up really) all used 64 bit and auto adjusted for 32 bit.

            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

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

              @Tom-Elliott said in mounting /images failed: Connection timed out:

              @george1421 1.2.0 (1.0.0 and up really) all used 64 bit and auto adjusted for 32 bit.

              OK so the names bzImage == x64 and bzImage32 == x86 is still proper for 1.2.0?

              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!

              Tom ElliottT S 2 Replies Last reply Reply Quote 0
              • Tom ElliottT
                Tom Elliott @george1421
                last edited by

                @george1421 Yessir.

                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 1
                • S
                  sjensen @george1421
                  last edited by

                  @george1421 Ok gentleman do I need to upgrade 1.3.0 to fix my issue? Or do I need to do some additional debuging?

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

                    @sjensen All of the commands I’m asking you to run should be run on the Client machine, NOT the fog server.

                    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

                    S 2 Replies Last reply Reply Quote 0
                    • S
                      sjensen @Tom Elliott
                      last edited by

                      @Tom-Elliott I used the exact lines you posted on the client in debug mode as instructed. I can send a picture of what is being displayed on the clients screen.

                      1 Reply Last reply Reply Quote 0
                      • S
                        sjensen @Tom Elliott
                        last edited by

                        @Tom-Elliott version 4.8.11 x86_64 from the client

                        1 Reply Last reply Reply Quote 0
                        • S
                          sjensen @Tom Elliott
                          last edited by

                          @Tom-Elliott Thank you both very much for your help the last couple days. I really appreciate it.

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

                            @sjensen so on the fog client (target computer)

                            1. Can you attempt to ping the FOG server? ping <fog_server_IP> where you replace the <fog_server_ip> with the real ip address of your fog server.

                            2. What was the results of executing Tom’s commands to connect the FOG server from the target computer over NFS.

                            mkdir /images
                            mount -o nolock,proto=tcp,rsize=32768,wsize=32768,intr,noatime "192.168.28.10:/images/dev" /images
                            

                            Then I’ll add my bits

                            ls -la /images
                            

                            This should give you a listing of all of the files in the /images share on the fog server.
                            If you do this from the fog server console ls -la /images the values should be the same.

                            But, this is where your image capture is failing.

                            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!

                            S 2 Replies Last reply Reply Quote 0
                            • S
                              sjensen @george1421
                              last edited by

                              @george1421
                              kernel version on client version 4.8.11 x86_64 from the client

                              mkdir /images
                              mount -o nolock,proto=tcp,rsize=32768,wsize=32768,intr,noatime “192.168.28.10:/images/dev” /images

                              result from above commands
                              mount: cant find images: in /etc/fstab

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

                                @sjensen Strange…

                                Lets try this mount command (sorry I’m old school here, we don’t need all them fancy options where I’m from)

                                Make sure the /images directory exists on the target computer with ls -la /images (ran from the target computer).

                                Then mount the local /images on the target computer to /images/dev on the FOG computer
                                mount -t nfs 192.168.28.10:/images/dev /images

                                If that one doesn’t work I have another command, but ideally the simple mount command should work.

                                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
                                • S
                                  sjensen @george1421
                                  last edited by

                                  @george1421 think i may have found the issue. I cannot ping the fog server from the command prompt on the client. I cannot ping anything on the same network from the client. I don’t get it.

                                  Tom ElliottT george1421G 2 Replies Last reply Reply Quote 0
                                  • Tom ElliottT
                                    Tom Elliott @sjensen
                                    last edited by

                                    @sjensen What is the IP of the client?

                                    ip addr

                                    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

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

                                      @sjensen said in mounting /images failed: Connection timed out:

                                      @george1421 think i may have found the issue. I cannot ping the fog server from the command prompt on the client. I cannot ping anything on the same network from the client. I don’t get it.

                                      Well in a way this is GREAT NEWS. No pingy means no mounty.

                                      The ip addr show should give you a listing of network interfaces, you want to look for the line with eth0 in it.

                                      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
                                      • S
                                        sjensen @Tom Elliott
                                        last edited by

                                        @Tom-Elliott Strangely enough there is not an ip address

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

                                          @sjensen Do you see a line for eth0? There will be one for the loop back interface lo or something like that.

                                          Part 2 of the question is what type of ethernet adapter is in this computer? Is it a usb ethernet adapter or a built in one on the motherboard?

                                          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!

                                          S 1 Reply Last reply Reply Quote 0
                                          • S
                                            sjensen @george1421
                                            last edited by

                                            @george1421 0_1482431860070_IMG_0089.JPG

                                            Pretty sure it is an intel adapter

                                            the Ethernet is built on the motherboard

                                            Tom ElliottT 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 4 / 5
                                            • First post
                                              Last post

                                            140

                                            Online

                                            12.1k

                                            Users

                                            17.3k

                                            Topics

                                            155.3k

                                            Posts
                                            Copyright © 2012-2024 FOG Project