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

Fog Upload Issues

Scheduled Pinned Locked Moved Solved
FOG Problems
4
16
3.3k
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.
  • W
    wlsnfmly
    last edited by Mar 21, 2017, 2:34 PM

    Tried to upload an image today and encountered an issue. Client error shows lack of diskspace, but we have 600gb free space on the system.

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by Mar 21, 2017, 2:44 PM

      What version of FOG are you running?

      Also upload is ambiguous, were you doing a capture or deploy?

      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!

      W 1 Reply Last reply Mar 21, 2017, 2:56 PM Reply Quote 0
      • W
        wlsnfmly
        last edited by Mar 21, 2017, 2:52 PM

        I’m doing a capture. here is the screen shot of the output for df -h
        0_1490107929955_Capture.PNG

        G 1 Reply Last reply Mar 21, 2017, 2:56 PM Reply Quote 0
        • G
          george1421 Moderator @wlsnfmly
          last edited by Mar 21, 2017, 2:56 PM

          @wlsnfmly You might also want to post a screen shot of how you have your storage node settings for this server. What you have is not standard. We need to have a clear picture of what is setup.

          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!

          W 1 Reply Last reply Mar 21, 2017, 2:58 PM Reply Quote 0
          • W
            wlsnfmly @george1421
            last edited by Mar 21, 2017, 2:56 PM

            @george1421 here is the image of the error0_1490108191117_123_1.jpeg

            1 Reply Last reply Reply Quote 0
            • W
              wlsnfmly @george1421
              last edited by Mar 21, 2017, 2:58 PM

              @george1421 0_1490108252686_Capture.PNG

              G 1 Reply Last reply Mar 21, 2017, 3:11 PM Reply Quote 0
              • G
                george1421 Moderator @wlsnfmly
                last edited by Mar 21, 2017, 3:11 PM

                @wlsnfmly My initial reaction is that your image path and ftp path should be the same.

                /storage1 != /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!

                W 1 Reply Last reply Mar 21, 2017, 3:19 PM Reply Quote 0
                • W
                  wlsnfmly
                  last edited by Mar 21, 2017, 3:15 PM

                  so I can just change the ftp path from image to /storage and that should work??

                  1 Reply Last reply Reply Quote 0
                  • W
                    wlsnfmly @george1421
                    last edited by Mar 21, 2017, 3:19 PM

                    @george1421 Tried that, still failed, same error

                    1 Reply Last reply Reply Quote 0
                    • W
                      wlsnfmly
                      last edited by Mar 23, 2017, 1:52 PM

                      Anybody have any other ideas on this? I’m drowning here.

                      1 Reply Last reply Reply Quote 0
                      • T
                        Tom Elliott
                        last edited by Tom Elliott Mar 23, 2017, 8:24 AM Mar 23, 2017, 2:24 PM

                        The only idea I have is your /storage1 folder is missing the dev folder?

                        Can you try:

                        mkdir /storage1/dev
                        touch /storage1/{,dev/}.mntcheck
                        chmod -R 777 /storage1
                        

                        Also your ftp patch should simply be /storage1 as your Image path.

                        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

                        W G 2 Replies Last reply Mar 23, 2017, 3:55 PM Reply Quote 0
                        • W
                          wlsnfmly @Tom Elliott
                          last edited by Mar 23, 2017, 3:55 PM

                          @Tom-Elliott I tried that, still failed. Same error. The system looks like it is going to work, it gets to about 1% on the progress bar, then goes haywire and fails.

                          1 Reply Last reply Reply Quote 0
                          • T
                            TaTa
                            last edited by Mar 24, 2017, 2:24 PM

                            @Tom-Elliott Does he needs to add /storage1 to /etc/exports?

                            1 Reply Last reply Reply Quote 0
                            • G
                              george1421 Moderator @Tom Elliott
                              last edited by Mar 24, 2017, 3:24 PM

                              @Tom-Elliott Sorry i should have updated this thread yesterday.

                              I remoted into the user’s computer and we set out to debug this issue. I checked the fog server and it is setup correctly (even with the /storage1 setup). The /storage1 share and mount point are connected to the OPs second hard drive /dev/sdb. As far as I can tell/check the FOG server is functioning correctly.

                              We setup a debug capture on the target computer and stepped through the capture process. On the second run through we caught a quick flash of an error from partclone indicating a bad sector on the target system hard drive which was aborting the partclone capture at 12% (or 2% I can’t remember) each time. Each run through the image would make it to the same percentage and abort.

                              (Guess)When partclone aborted because of a bad disk sector, FOS picked that up as the FOG server being out of disk space.

                              Wlsnfmly was going to inspect the target system more to try to determine what the root cause of the issue is/was. He saw locally that partclone reporting the disk being dirty and that’s why it aborted. The error was only on the screen for about 1/2 a second so it wasn’t easy to read the entire message.

                              That is the results of testing yesterday afternoon.

                              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 W 2 Replies Last reply Mar 24, 2017, 5:22 PM Reply Quote 0
                              • T
                                Tom Elliott @george1421
                                last edited by Mar 24, 2017, 5:22 PM

                                @george1421 The error message is just a “here is something you might be able to check” as the error codes returned by partclone don’t have any specificity. Meaning it’s always going to error with the same exit code regardless of the actual problem. This is why I now try to provide the partclone.log too.

                                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
                                • W
                                  wlsnfmly @george1421
                                  last edited by Mar 27, 2017, 5:29 PM

                                  @george1421 After further troubleshooting, we determined that the issue was due to a bad sector on the hd. Moved to a different HD and the system worked like a champ. Thanks George for assisting in finding that little blurb about faulty sectors during the timeout

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

                                  209

                                  Online

                                  12.0k

                                  Users

                                  17.3k

                                  Topics

                                  155.2k

                                  Posts
                                  Copyright © 2012-2024 FOG Project