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

    Correction: Why is FOG trashing file systems during partition resize?

    Scheduled Pinned Locked Moved
    FOG Problems
    4
    7
    3.7k
    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
      JTD
      last edited by

      So, in this thread: [url]http://fogproject.org/forum/threads/how-much-space-do-i-need-for-a-new-image.3897/[/url] I thought FOG was just insisting on imaging machines as RAW rather than NTFS. I was wrong. Instead what is happening is that when it performs the partition resize, it trashes the file system. It takes about 3 or 4 minutes to resize the 465GB partition to the size of the data (about 24GB), then starts the imaging process as RAW and attempts to capture the entire 465GB hard drive. This has now happened with two machines, both of which had single-partition maps, one of which was sysprepped, the other wasn’t. Both are Windows 7.

      I tried to change the subject line of my original post, but it wouldn’t let me and I’m sort of freaking out because I need this to start working this afternoon.

      1 Reply Last reply Reply Quote 0
      • B
        BryceZ
        last edited by

        First: Which version of FOG are you using?
        Second: When you say these are single partition are you saying you didn’t add any extra partitions or that you went into the advanced options when installing Windows and removed the recovery partition?

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

          [quote=“BryceZ, post: 9828, member: 2”]First: Which version of FOG are you using?
          Second: When you say these are single partition are you saying you didn’t add any extra partitions or that you went into the advanced options when installing Windows and removed the recovery partition?[/quote]
          Hi,

          I’m using 0.32 and I didn’t add any partitions and Disk Manager does not report any partitions other than the one. This was Win7 installed straight from installation media with no 100MB partition reserved for BitLocker.

          1 Reply Last reply Reply Quote 0
          • B
            BryceZ
            last edited by

            So you took out the Recovery partition during install of Windows? I think it’s listed as System Reserved under Disk Management.

            I want to say that FOG was written to handle that partition being there or not, but I have a sneaking suspicion that removing that partition could cause problems. I don’t know that it would cause your RAW problems. I’m just thinking out loud.

            I recall uploading raw to be a problem for someone a while back, so you might be able to dig through the forums and find some advice, but I don’t remember the resolution.

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

              [quote=“BryceZ, post: 9832, member: 2”]So you took out the Recovery partition during install of Windows? I think it’s listed as System Reserved under Disk Management.

              I want to say that FOG was written to handle that partition being there or not, but I have a sneaking suspicion that removing that partition could cause problems. I don’t know that it would cause your RAW problems. I’m just thinking out loud.

              I recall uploading raw to be a problem for someone a while back, so you might be able to dig through the forums and find some advice, but I don’t remember the resolution.[/quote]
              There’s definitely no System Reserved partition in Disk Management.

              1 Reply Last reply Reply Quote 0
              • W
                WaltWilcoxJr
                last edited by

                I am having the same issue. We manually partition our drives to avoid having the complication of the system reserved partition in windows 7. Altho in my case, the system does not try to upload anything, it just instantly passes through the upload process after resizing and reboots.

                Looking at the partition in gparted after fog messes it up shows that the partition has no flags set on it. Manually setting the flags still won’t allow the machine to boot, I’m assuming due to the MBR not being rewritten after the resizing/mangling.

                The odd part is these exact same machines worked with a previous image, but we rebuilt it from scratch to fix some deep rooted driver issues. And we have been using our method of partitioning the drives manually since windows 7 came out.

                1 Reply Last reply Reply Quote 0
                • R
                  RogueSpear00
                  last edited by

                  I encountered quite a few problems that were related to some of everything in this thread.

                  Here’s what I did to resolve my issue:
                  [LIST=1]
                  []Started with a fresh machine.
                  [
                  ]Booted to FOG PXE and went to Debug Mode.
                  []DD’d the drive for a minute to destroy any partition data.
                  [
                  ]Created a fresh image from install.
                  []Sysprep’d machine.
                  [
                  ]Uploaded image as Single Partition (NTFS Only, Resizable)
                  [/LIST]
                  After deploying images using this method, I was able to deploy several images without any problems.

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

                  191

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project