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

mounting /images failed: Connection timed out

Scheduled Pinned Locked Moved
FOG Problems
3
81
30.6k
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
    sjensen @Tom Elliott
    last edited by Dec 22, 2016, 2:23 PM

    @Tom-Elliott OK i will do so. Do i want download debug or upload debug?

    T 1 Reply Last reply Dec 22, 2016, 2:24 PM Reply Quote 0
    • T
      Tom Elliott @sjensen
      last edited by Dec 22, 2016, 2:24 PM

      @sjensen I thought my information was specific enough, but ultimately either one or the other will work just fine. In your case, as you’re trying to upload a new image?: Use upload debug.

      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 Dec 22, 2016, 2:30 PM Reply Quote 0
      • S
        sjensen @Tom Elliott
        last edited by Dec 22, 2016, 2:30 PM

        @Tom-Elliott Ok it is waiting at the command prompt.

        T G 2 Replies Last reply Dec 22, 2016, 2:36 PM Reply Quote 0
        • T
          Tom Elliott @sjensen
          last edited by Dec 22, 2016, 2:36 PM

          @sjensen Try mounting the nfs: run->

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

          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 Dec 22, 2016, 2:51 PM Reply Quote 0
          • T
            Tom Elliott
            last edited by Dec 22, 2016, 2:38 PM

            Also, so we know the kernel version you’re running, can you get us the output of:

            uname -rm

            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 Dec 22, 2016, 2:44 PM Reply Quote 0
            • G
              george1421 Moderator @sjensen
              last edited by george1421 Dec 22, 2016, 8:40 AM Dec 22, 2016, 2:38 PM

              @sjensen The first thing I want you to do is this:

              On the console of the target computer key in

              1. ip addr show that will tell you the current IP address of the target computer (please post it here)
              2. I need you to give root a password so we can connect to it remotely (so you don’t have to sit in front of the target computer) passwd and give root a password it can be something as simple as Password-1 or complex, it is up to you. This password will exist until the target computer is rebooted so its only temporary.
              3. Install putty on your computer [ http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html ], its a free download and will allow you to connect to the target computer over the network. You will need this to copy and paste commands given by Tom or myself. The exe is not installed, but just run.

              I see Tom went in directly to the point.

              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 Dec 22, 2016, 2:44 PM

                @Tom-Elliott 0_1482417870908_Capture7.PNG

                G 1 Reply Last reply Dec 22, 2016, 2:51 PM Reply Quote 0
                • S
                  sjensen @Tom Elliott
                  last edited by Dec 22, 2016, 2:51 PM

                  This post is deleted!
                  1 Reply Last reply Reply Quote 0
                  • G
                    george1421 Moderator @sjensen
                    last edited by george1421 Dec 22, 2016, 8:56 AM Dec 22, 2016, 2:51 PM

                    @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!

                    T 1 Reply Last reply Dec 22, 2016, 2:55 PM Reply Quote 1
                    • S
                      sjensen @Tom Elliott
                      last edited by Dec 22, 2016, 2:53 PM

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

                      T 1 Reply Last reply Dec 22, 2016, 2:54 PM Reply Quote 0
                      • T
                        Tom Elliott @sjensen
                        last edited by Dec 22, 2016, 2:54 PM

                        @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
                        • T
                          Tom Elliott @george1421
                          last edited by Dec 22, 2016, 2:55 PM

                          @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

                          G 1 Reply Last reply Dec 22, 2016, 2:56 PM Reply Quote 0
                          • G
                            george1421 Moderator @Tom Elliott
                            last edited by Dec 22, 2016, 2:56 PM

                            @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!

                            T S 2 Replies Last reply Dec 22, 2016, 2:57 PM Reply Quote 0
                            • T
                              Tom Elliott @george1421
                              last edited by Dec 22, 2016, 2:57 PM

                              @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 Dec 22, 2016, 2:59 PM

                                @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
                                • T
                                  Tom Elliott
                                  last edited by Dec 22, 2016, 3:00 PM

                                  @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 Dec 22, 2016, 3:11 PM Reply Quote 0
                                  • S
                                    sjensen @Tom Elliott
                                    last edited by Dec 22, 2016, 3:11 PM

                                    @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 Dec 22, 2016, 3:18 PM

                                      @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 Dec 22, 2016, 3:47 PM

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

                                        G 1 Reply Last reply Dec 22, 2016, 4:29 PM Reply Quote 0
                                        • G
                                          george1421 Moderator @sjensen
                                          last edited by george1421 Dec 22, 2016, 10:32 AM Dec 22, 2016, 4:29 PM

                                          @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 Dec 22, 2016, 4:35 PM Reply Quote 0
                                          • 1
                                          • 2
                                          • 3
                                          • 4
                                          • 5
                                          • 3 / 5
                                          3 / 5
                                          • First post
                                            56/81
                                            Last post

                                          229

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project