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

Resize partition fails- Win 7- deploying

Scheduled Pinned Locked Moved
FOG Problems
2
6
1.5k
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.
  • N
    neodawg
    last edited by Jan 25, 2016, 8:49 PM

    Updated to the latest trunk version and tried pushing out an existing know good image. It gets to 80% and dies. I think this is the part where its done copying data and would expand the partition with blank data. I came from 1.2.0 and server is Centos 6.7.
    Fog version is 6096

    I canceled the task and the computer boots up fine, but the OS partition size is not the full 223gb. This is odd, because Windows Disk Management says its 223GB (which is correct and what it should be) but My Computer shows the drive as being 53.3GB.

    On a side note it appears the legacy client wont do domain join anymore so will probably have push off updating until summer so we can update to the new fog client when we update images.

    Screen shot here

    Thoughts?

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott
      last edited by Jan 25, 2016, 9:26 PM

      Does this same image fail on multiple systems? If it fails, is it always at the same point, or does it seem to randomly fail?

      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
      • N
        neodawg
        last edited by Jan 25, 2016, 9:37 PM

        I havent tested another computer, but i did run the task a couple of times and it failed at the same spot each time. I will go test another computer, they are Dell Optiplex 990s with a SSD in them.

        T 1 Reply Last reply Jan 25, 2016, 9:38 PM Reply Quote 0
        • T
          Tom Elliott @neodawg
          last edited by Jan 25, 2016, 9:38 PM

          @neodawg Well, the signs seem to point that the image is actually corrupted in some way.

          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
          • N
            neodawg
            last edited by Jan 25, 2016, 9:56 PM

            Same spot and same error on another computer. Seems odd considering I just used this image on 1.2.0 about a month ago, and the server it runs on is a virtual machine and there isn’t any errors on the RAID array.

            I will try and deploy a different image to see what happens…

            1 Reply Last reply Reply Quote 0
            • N
              neodawg
              last edited by neodawg Jan 25, 2016, 4:24 PM Jan 25, 2016, 10:22 PM

              Well its seems were both right (sort of) I reverted the server via snapshot back to 1.2.0 and it deploys fine to the 80.3% errors then it performs the after imaging tasks, such as change host name/resize FS/clear task. So its probably been corrupt for awhile but have never noticed it, since it works fine.
              It appears the trunk fog just errors out and then stops everything and reboots.

              EDIT: I did try pushing a different image to the same PC and that worked fine.

              Thanks for the help and sorry about wasting everyone’s time.

              On an off topic, how well is the legacy client going to work with the trunk fog? Is best to just plan to upgrade the client at the same time as the server?

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              1 / 1
              • First post
                4/6
                Last post

              154

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project