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

    Images not being Deployed

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    6
    31
    15.1k
    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.
    • J
      Joe Schmitt Senior Developer
      last edited by

      https://forums.fogproject.org/topic/5963/unknown-response-datetimezone-__construct-unknown-or-bad-timezone

      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.

      1 Reply Last reply Reply Quote 0
      • J
        jquilli1
        last edited by

        @Jbob said:

        https://forums.fogproject.org/topic/5963/unknown-response-datetimezone-__construct-unknown-or-bad-timezone

        Thanks for the fix, back to the same issue of not being able to deploy.

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

          @jquilli1 Can you run a Debug Deploy and make sure everything is working?

          When you’re at the CLI (after hitting enter a few times), issue the fog command. Then just slowly press enter for each step.

          I want you to pay special attention to the NFS Mounting parts.

          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/

          1 Reply Last reply Reply Quote 0
          • J
            jquilli1
            last edited by

            Assuming I did this right. I ran an advanced task “debug” and then did this:
            debug.bmp

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

              @jquilli1 It should be created like this:
              upload-d64f25c0-cd7a-489c-8de0-8383bf913ca8

              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/

              1 Reply Last reply Reply Quote 0
              • J
                jquilli1
                last edited by

                Same issue 😕 everything finished with “done”

                debug.bmp

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

                  What image type do you use? Is the source disk bigger than the destination?

                  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
                    Sebastian Roth Moderator
                    last edited by

                    Please boot the machine you want to deploy to in debug mode again (as Wayne described) and run this command fogpartinfo --list-parts /dev/sda

                    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
                    • Wayne WorkmanW
                      Wayne Workman
                      last edited by

                      I’m linking this thread with this since I think the problems are the same: https://forums.fogproject.org/topic/5967/fog-server-4956-won-t-deploy-image-to-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/

                      1 Reply Last reply Reply Quote 1
                      • J
                        jquilli1
                        last edited by

                        @Uncle-Frank said:

                        What image type do you use? Is the source disk bigger than the destination?

                        @Wayne-Workman said:

                        I’m linking this thread with this since I think the problems are the same: https://forums.fogproject.org/topic/5967/fog-server-4956-won-t-deploy-image-to-host

                        Looks like it might have been the image size being bigger than the destination disk. As of right now it’s working but it doesn’t make any sense because the disk I created the image from was 80GB and the destination disk I’m deploying to is 80GB. I’ll report back if I run into anything else.

                        Thanks for all of the help!

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

                          @jquilli1 said:

                          the disk I created the image from was 80GB and the destination disk I’m deploying to is 80GB. I’ll report back if I run into anything else.

                          Are the two HDDs identical? Absolutely identical? Same model and everything?

                          Just a few KB smaller or a few sectors less will make a difference.

                          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/

                          1 Reply Last reply Reply Quote 1
                          • C
                            CosmoJoe
                            last edited by

                            I am currently doing PoC of FOG for image deployment at my company… testing currently with VMs prior to imaging laptops. I’ve run into this issue presented by OP twice now, once with a Windows 10 and then a Windows 8.1 captured image. Both times I fixed by blowing away the captured image, deleting the computer, re-registering and re-capturing. Not sure what the cause is… will try to recreate the problem.

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

                              The issue here was that the client which was meant to be deployed had a smaller disk than the client pulling the image from. Is this the case for you too? I doubt because this cannot be fixed by re-uploading and deploying to the same machine again.

                              Probably best if you open a new thread and tell us all about your situation. FOG version, OS version, error messages you see, steps you took…

                              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

                              J 1 Reply Last reply Reply Quote 0
                              • J
                                jquilli1 @Sebastian Roth
                                last edited by

                                @Uncle-Frank said:

                                The issue here was that the client which was meant to be deployed had a smaller disk than the client pulling the image from. Is this the case for you too? I doubt because this cannot be fixed by re-uploading and deploying to the same machine again.

                                Probably best if you open a new thread and tell us all about your situation. FOG version, OS version, error messages you see, steps you took…

                                I am having this issue again. I created a VM image and deployed it to a computer. Made changes and added software and then uploaded that image. I then went to deploy that image to a lab, but most of the machines gave the error and now are unable to boot as it erased the partitions. Some machines did take the image. I checked the HDD size of both computer that uploaded the image and the computers that gave the error and they are all 80GB hard drives. I doubt brand would have anything to do with it?

                                1 Reply Last reply Reply Quote 0
                                • J
                                  jquilli1
                                  last edited by

                                  So I decided to look at the hdd brands just out of curiosity. The computers are all the same model except the hdds. Everyone with a Western Digital took the image but not Seagates. The computer that uploaded the image was using a WD drive. Going to make an image on a Seagate and see if I can push that.

                                  Weird…

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

                                    @jquilli1 Not weird but pretty simple: 80GB is not always exactly 80GB with all vendors! Only a few more or less sectors make a difference. You might be able to make things work when using the Seagate (probably a little smaller) as your master disk. If you are really keen you can boot PC with the two different disk type in FOG debug mode and run fdisk to see the exact sector count:

                                    fdisk -l /dev/sda
                                    
                                    Disk /dev/sda: 80 GB, ....... bytes
                                    255 heads, .... XXXXXX sectors
                                    ...
                                    

                                    Compare the numbers of sectors and/or bytes

                                    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

                                    J 1 Reply Last reply Reply Quote 0
                                    • J
                                      jquilli1 @Sebastian Roth
                                      last edited by

                                      @Uncle-Frank said:

                                      @jquilli1 Not weird but pretty simple: 80GB is not always exactly 80GB with all vendors! Only a few more or less sectors make a difference. You might be able to make things work when using the Seagate (probably a little smaller) as your master disk. If you are really keen you can boot PC with the two different disk type in FOG debug mode and run fdisk to see the exact sector count:

                                      fdisk -l /dev/sda
                                      
                                      Disk /dev/sda: 80 GB, ....... bytes
                                      255 heads, .... XXXXXX sectors
                                      ...
                                      

                                      Compare the numbers of sectors and/or bytes

                                      I figured that was the case as I know not 80GB isn’t really 80 sometimes. I’ll give that a shot and see what I can find. So far it seems like that was the issue but will report back with actual results!

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

                                        @jquilli1 You know a very simple solution is just to use re-sizable image types… I find there is almost never a reason not use them.

                                        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/

                                        J 1 Reply Last reply Reply Quote 0
                                        • J
                                          jquilli1 @Wayne Workman
                                          last edited by

                                          @Wayne-Workman said:

                                          @jquilli1 You know a very simple solution is just to use re-sizable image types… I find there is almost never a reason not use them.

                                          I was told to use “Multiple Partition Image - Single Disk (Non-resizable)” if I’m capturing an image that’s Windows 7 or above. Have I been mistaken this whole time?

                                          Wayne WorkmanW george1421G 2 Replies Last reply Reply Quote 0
                                          • Wayne WorkmanW
                                            Wayne Workman @jquilli1
                                            last edited by Wayne Workman

                                            @jquilli1 Well, just try. See what happens. Fog trunk has made great advancements in this area. Maybe 1.2.0 has quirks… I know it has quirks with manufacturer MBRs and recovery partitions.

                                            I’ve uploaded resizeable images for Win7 MBR, Win7 GPT, Win8.1 MBR and Win8.1 GPT with zero problems. I’ve also uploaded resizable images of Fedora 21 & 22 Workstation, CentOS 7, and Ubuntu 15.04. When uploading resizeable Linux images, you just need to build the image using Ext4 for everything but the swap partition.

                                            I’ve also uploaded a resizable XP image once! lol

                                            But, I make my images from scratch, I format and Delete all existing partitions, and make my images from scratch. I vehemently resist the bloatware and poor configuration that manufacturer images ship with.

                                            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/

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

                                            207

                                            Online

                                            12.0k

                                            Users

                                            17.3k

                                            Topics

                                            155.2k

                                            Posts
                                            Copyright © 2012-2024 FOG Project