SOLVED Problem with the resize (expanding) on a hard drive

  • Hi all !

    I come here because of a problem of resize of the hard drive. Fog don’t expand the hard drive and I don’t know why 😕

    For example here, my image made 40GB and the hard drive made 60GB (on a VM) and I have the same problem with physical machines with SSD of 256GB.
    Corners-Machine-Test - VMware Remote Console.jpg

    I read the documentation ( and I choose the type : “Single Disk - Resizable” like you can see here :
    Image Management - Google Chrome.jpg

    I use Fog 1.5.7 and the image is a Windows 10. In which log or file can I have more information on this problem ?

    I found eventually this solution : but it’s not a clear solution…

    Thank you for your answers !

  • Hi,

    i am not sure if it can simply deleted, It’s used in recovery cases and there are 12,5MB of data in it. I need to find out if Windows 10 is using it for what ever case.

    Best Regards X23

  • Moderator

    @x23piracy It’s safe to delete if you don’t need that partition.

    Alternatively, you could manually create the partitions in windows setup I suppose.

  • Hi,

    i thought the same but i can’t move the recovery partition in front of the system partition even if i shrink the beginning of the system partition…meh:

    Best Regards X23

  • Moderator

    @x23piracy Not sure what program you are using, but perhaps you need to shrink you windows partition first, move it to the right (into the unallocated space), then move the recovery partition in front of it, reallign and expand again.

  • Hi,

    i am currently trying to move partitions but it won’t let me:

    The marked part is “move partition” it’s greyed out.

    Regards X23

  • Moderator

    @x23piracy Yes, that should work. Hopefully we have a better solution by 1.6.0

  • Hi Quazz,

    thanks for your quick response after that deployment i could see the recovery partition is behind the system partition, if move this in front of the system partition and capture after that it works?

    Btw. i found out howto still use copyprofile with newer Win10 Versions if someone is interested.

    I was looking for my post and wondering with the post number has been extended but my post wasnt visible, forum changes to current post on top hehe 😉

    Best Regards X23

  • Moderator

    @x23piracy The newest W10 versions seem to create a partition after the Windows partition. This will be what’s blocking it.

    There are some ideas on how to resolve such things in the future, but currently you have to manually move the partition before capture.

  • Hi,

    i currently have this Problem with (Windows 10 2004) i created a new image thats not expanding after deployment. I am on an older FOG Version 1.5.0 and older Images (1703) expand correctly.

    Any idea?

    Best Regards X23

  • @Quazz

    Thank you, you found the solution !

    Here is the result of the tmpoutput.txt file
    Corners-Motherimage - VMware Remote Console.jpg

    Indeed, the problem came from a problem with the filesystem of my “mother” image. After several chkdsk (I had reboot only once the first time), the expand works well.

    Thank you guys ! The problem is so solve now.

  • Moderator

    @loutrage See it says Not shrinking (/dev/sda2) trying fixed size in the pictures. So there is an issue with trying to shrink that filesystem. I’d suggest you do another debug capture task and step all the way to the point where you see that message. Now press Ctrl+c to stop the script and get back to the shell. Now run cat /tmp/tmpoutput.txt to see all the messages the last command (ntfsresize) produced. Take a picture and post here.

  • Moderator

    @loutrage Looks the resize test fails, which automatically marks the partition as fixed size.

    Possibly the filesystem or disk is damaged causing the failure.

    Try and fix the filesystem by running chkdsk C: /f on the windows client you want to capture. (you’ll then need to confirm to schedule on reboot and then ofc reboot)

  • @Sebastian-Roth
    Here is 2 screens about SDA2. Everything seems good I think.


  • Moderator

    @loutrage said in Problem with the resize (expanding) on a hard drive:

    I also tried to see a message like this Not resizing filesystem /dev/sda2 (part too small) but it was too fast.

    The messages we see in the picture all seem fine up to that point. It detects sda1 as fixed because it has the boot flag set. Probably wait a little bit longer to see what it says when it tries to shrink sda2.

    It if’s all going to fast you can just schedule a debug capture task. Just as you would create a normal task bit just before you click the last button there is a checkbox for debug. Boot up the machine and hit ENTER twice to get to a shell. Key in fog as command and fire it up with ENTER. Now you step through the whole process with plenty of time to read and take pictures.

  • @Sebastian-Roth

    I replaced the files init.xz & init_32.xz with the last version then I made a new capture but I had always the same problem.

    Then I tried the “dirty fix” by editing the file d1.fixed_size_partitions but I receive this error :

    PrtScr capture_2.jpg

    Maybe because the file d1.fixed_size_partitions changed with my new image ?

    The content of the file is now :


    I also tried to see a message like this Not resizing filesystem /dev/sda2 (part too small) but it was too fast.

    I just saw thisCorners-Motherimage - VMware Remote Console_2.jpg

  • Moderator

    @loutrage Interesting, the second partition doesn’t have any flags set. This is how it should be and shouldn’t cause it to be seen as non-resizable.

    Do you keep an eye on the screen when the image is captured. Possibly the resize test fails with Not resizing filesystem /dev/sda2 (part too small)???

    As a dirty quick fix you can edit d1.fixed_size_partitions and make it look like this:


    Then try deploying again.

    I do remember that I made I change to the inits after 1.5.7 was release that is related to detecting which partitions can/cannot be resized. Though I didn’t think this would help in your situation. But still you can update to the latest inits and see if that helps. Login to your FOG server as root and run the following commands:

    cd /var/www/html/fog/service/ipxe
    mv -i init.xz init.xz.orig
    mv -i init_32.xz init_32.xz.orig
    chown www-data:www-data init*

    The last command fails if you are on CentOS. Use chown apache:apache init* instead…

  • @Sebastian-Roth

    Here is the information :

    Corners-Motherimage - VMware Remote Console.jpg

    Visibly, there is just the boot flag.

    @george1421 I let the “single disk resizable” option by default. I only changed 2 days ago to make a test.

  • Moderator

    @george1421 said in Problem with the resize (expanding) on a hard drive:

    We also need to confirm that single disk resizable was set BEFORE the image was captured and not changed AFTER the image was captured.

    Good point, but I don’t think that’s the case here because some of the files, like d1.minimum.partitions are only being created when you have resizable image type set on capture.

  • Moderator

    @Sebastian-Roth said in Problem with the resize (expanding) on a hard drive:

    For some reason FOS (FOG Linux OS) detects both your Windows partitions as non-resizable.

    We also need to confirm that single disk resizable was set BEFORE the image was captured and not changed AFTER the image was captured.

    It would be an interesting case if FOS misidentified the resizable partitions. I’d like to see the conditions that created this incorrect setting too.