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

Images not deploying after update to 1.3.5

Scheduled Pinned Locked Moved Unsolved
FOG Problems
6
14
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.
  • R
    reprised
    last edited by Mar 28, 2017, 2:39 PM

    Hi all
    I’ve just updated our fog server from 1.3.3 to 1.3.5 on ubuntu 14.04 and it seems only 2 of our 5 images will now deploy. The three that don’t deploy give errors at the point “Attempting to expand/fill partitions” I’ve attached a screenshot:

    alt text

    I’m not great with linux, can anyone help.
    Thanks

    1 Reply Last reply Reply Quote 0
    • W
      Wayne Workman
      last edited by Mar 28, 2017, 11:22 PM

      Well, I’ll start this off by saying there are oh-so-many changes in Image resizing between 1.3.3 and 1.3.5. The changes are quite tremendous, so much so that the developers thought it best to go ahead and bump the version after 1.3.5 to 1.4 if that gives you any hints.

      My recommendation would be to try to recapture these images using 1.3.5, unless @Tom-Elliott has a better idea (he probably does).

      Do recapture these, you would first need to deploy them. There should be web interface backups and DB backups inside of /home on your FOG server. Restoring the web files is a simple removal of existing files, and copying of the existing files - and perhaps permission setting after the copy is done. Then importing the old DB. This would take you back to before you upgraded. Then you’d deploy these images without joining them to the domain, perhaps without even allowing the target machines to boot - and then upgrade the fog server and recapture.

      We should wait for Tom to weigh in though, he probably can come up with an easier plan.

      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
      • R
        reprised
        last edited by Mar 29, 2017, 8:00 AM

        I do have these images as vm’s so i guess i could recapture them (i did this when we upgraded from 1.2 to 1.3). I was just having a look in the image folder and one which is deploying contains just these files

        rec.img00
        sys.img.00

        and the other working one (captured with fog 1.3.3) has these:

        d1.fixed_size_partitions
        d1.mbr
        d1.minimum.partitions
        d1.original.fstypes
        d1.original.swapuuids
        d1.partitions
        d1p1.img
        d1p2.img

        In the folders of the 3 images that have errors, there are extra files:

        rec.img.000
        sys.img.00
        d1.fixed_size_partitions
        d1.original.fstypes
        d1.original.partitions
        d1.original.swapuuids

        G 1 Reply Last reply Mar 29, 2017, 9:56 AM Reply Quote 0
        • G
          george1421 Moderator @reprised
          last edited by Mar 29, 2017, 9:56 AM

          @reprised said in Images not deploying after update to 1.3.5:

          rec.img.000
          sys.img.00
          d1.fixed_size_partitions
          d1.original.fstypes
          d1.original.partitions
          d1.original.swapuuids

          In the past few days we are seeing an uptick in reporting that FOG 1.3.5 and 1.4.0-RC1 are having an issue deploying images that have the above image structures. From other posts images captured created with FOG 1.2.0 seem to be the most problematic. The developers are currently looking into why this is happening.

          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!

          F 1 Reply Last reply Mar 29, 2017, 6:19 PM Reply Quote 0
          • F
            Foglalt @george1421
            last edited by Mar 29, 2017, 6:19 PM

            I think I will check this topic often, as it is a really disturbing thing and need to find good way to solve. Especially that we have many images and recapturing them on version changes is closer to impossible (take hours actually) that if here we come to a problem solving trick that would be good. btw the less problematic is if images can be converted somehow.

            I think we can even accept tricks to make this steps rather than having 2 working sets of fog to retake images before and after such changes 🙂

            G 1 Reply Last reply Mar 29, 2017, 6:57 PM Reply Quote 0
            • G
              george1421 Moderator @Foglalt
              last edited by Mar 29, 2017, 6:57 PM

              @Foglalt No need to reimage anything. The developers are aware of this issue. At this point we are trying to collect as much info as possible to feed to them.

              Please stand by I hope to hear something soon.

              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!

              R 1 Reply Last reply Mar 30, 2017, 9:07 AM Reply Quote 2
              • R
                reprised @george1421
                last edited by Mar 30, 2017, 9:07 AM

                @george1421

                Thanks, if you require any further info from our fog server then let me know

                G 1 Reply Last reply Mar 30, 2017, 12:04 PM Reply Quote 0
                • G
                  george1421 Moderator @reprised
                  last edited by Mar 30, 2017, 12:04 PM

                  @reprised I just had a chat session with one of the developers. The recommendation is for you to update to 1.4.0-RC1

                  # Change to where your local git repository is:
                  cd /opt/fogproject
                  git checkout dev-branch
                  git pull
                  cd bin
                  ./installfog.sh -y
                  

                  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
                  • R
                    reprised
                    last edited by May 12, 2017, 9:17 AM

                    I’ve found a work around instead of upgrading you can remove the 4 extra files after backing them up of course:

                    d1.fixed_size_partitions
                    d1.original.fstypes
                    d1.original.partitions
                    d1.original.swapuuids

                    Leave the image files; i have these 2 files:

                    rec.img.000
                    sys.img.000

                    I tested this with all of the images that were not working and they now deploy.

                    T 1 Reply Last reply May 12, 2017, 12:00 PM Reply Quote 0
                    • T
                      Tom Elliott @reprised
                      last edited by May 12, 2017, 12:00 PM

                      @reprised Glad you have fixed it, but the reason we asked you to update is because 1.4.0 will be released soon and the problem we believe is addressed. Knowing if things are working properly before release is more important.

                      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

                      A 2 Replies Last reply Aug 2, 2017, 2:31 PM Reply Quote 1
                      • A
                        ale.com @Tom Elliott
                        last edited by ale.com Aug 2, 2017, 9:07 AM Aug 2, 2017, 2:31 PM

                        @tom-elliott I know that this topic is quite old, but I’ve the same issue on a freshly installed 1.4.4

                        Images has been captured with 1.2.0 (installed on an ubuntu 12.04)
                        1.4.4 has been installed on a new ubuntu 16.04 and /images folder copied from the old server to the new one

                        workaround proposed by @reprised doesn’t work for me (I don’t have rec.img.00 and sys.img.000)

                        should I deploy from old server and recapture every image or there’s another solution?

                        thank you!

                        G 1 Reply Last reply Aug 2, 2017, 3:58 PM Reply Quote 0
                        • A
                          ale.com @Tom Elliott
                          last edited by Aug 2, 2017, 3:57 PM

                          @tom-elliott wait, don’t waste your time with my previous post. It seems that something gone wrong during /images folder copy. I’m checking it. sorry.

                          1 Reply Last reply Reply Quote 0
                          • G
                            george1421 Moderator @ale.com
                            last edited by Aug 2, 2017, 3:58 PM

                            @ale-com said in Images not deploying after update to 1.3.5:

                            should I deploy from old server and recapture every image or there’s another solution?

                            Moderator note: You really should start your own thread because your conditions may not exactly match the OPs post.

                            But to your question, if you have the capabilities to do so, you will end up with a better solution. FOG 1.4.4 has a newer and faster compression engine called zstd. You can only take full advantage of this newer engine if you capture using it. Don’t forget to set your image format to partclone zstd (the default is still partclone gzip)

                            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!

                            A 1 Reply Last reply Aug 2, 2017, 5:04 PM Reply Quote 0
                            • A
                              ale.com @george1421
                              last edited by Aug 2, 2017, 5:04 PM

                              @george1421 I’m sorry, it really seemed (to me) that was the same issue (exactly same errors deploying an old image with a >1.3.x)

                              Now I can confirm that it was an issue copying the /images folder.

                              Thank you for your suggestion on zstd, I’ll change the compression method at the the next capture.

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

                              155

                              Online

                              12.0k

                              Users

                              17.3k

                              Topics

                              155.2k

                              Posts
                              Copyright © 2012-2024 FOG Project