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

FOG deployment problem (partition)

Scheduled Pinned Locked Moved Unsolved
FOG Problems
2
2
191
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.
  • ?
    A Former User
    last edited by Feb 8, 2024, 1:37 PM

    Hello,

    We usually use FOG where i work
    At the moment, i create a new image under Windows 11 on Nvme 512GB

    After working on it, installed some softwares,… i wanted to deploy the image on a computer room which are 256bg disk, and are under windows 10

    But i ve got the following error “partition 4 is too big”

    Btw, I deploy with resizable single disk
    I dont know what to do exactly to solve this kind of problem…

    I d would be very grateful if someone know what to do

    Alex

    G 1 Reply Last reply Feb 8, 2024, 4:30 PM Reply Quote 0
    • G
      george1421 Moderator @A Former User
      last edited by Feb 8, 2024, 4:30 PM

      @alexpolytech94 The shrinking of the disk when using single disk resizable is a bit of black magic. Sometimes because of the actual data size or location of the data on the disk its not possible to shrink the volume down enough to make it fit on a disk that is 1/2 the size of the source disk. I won’t go into too much detail, but if you have a partition that is fixed in size that can’t shrink, but a partition just before it on the disk that can shrink, fog will shrink the one that can be shrunk but leaves the one that can’t be shrunk as it were. If you were to deploy that image to a computer with half the size that non shrunk partition would be technically beyond the last sector on the 1/2 size disk.

      To put it another way, always build your mother image on the smallest disk possible, because it can expand to a larger target disk more often than shrink your image to fit on a smaller disk.

      When I was building golden images I would build them on a VM with a 50GB hard drive (smaller than anything I would deploy it to) and then let FOG expand the disk to match the target disk size. That always worked.

      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 1
      • 1 / 1
      1 / 1
      • First post
        1/2
        Last post

      253

      Online

      12.0k

      Users

      17.3k

      Topics

      155.2k

      Posts
      Copyright © 2012-2024 FOG Project