@bordercollie Interesting one. From the figures you posted it seems like on the original system where you capture the image from the first partition is very full already. I say this because the size of sda1 in d1.minimum.partitions
is not much smaller than in d1.partitions
. Calculating the size: 44439108 * 512 byte per sector / 1024 / 1024 / 1024 ~ 21 GB for sda1, is that correct?
So just from the figures to me it looks like FOG is not shrinking your sda1 partition but would simply deploy it in a similar size but the partition itself is just pretty much full to begin with - maybe that’s not correct but that’s what the numbers make me think. Please run df -h
on the machine before capturing the image.
Sure we do a little bit of fiddling with the numbers on resizable images and therefore it is actually possible that you end up with sda1 being a tiny bit smaller than it was originally.
I fully understand your intention of having sda1 expanded to lets say 50 GB or some proportion of the destination disk size. Unfortunately we don’t have the functionality to adjust resize options manually using FOG image settings at the moment. It’s definitely something I would like to add in the future but there are so many other things higher up in the todo list I suppose.
I just looked at the figures again to come up with a quick fix for you and noticed something strange. Usually partitions follow one another pretty closely. So if sda1 starts at 2048 and has a size of 44439108 I would expect sda2 to start at 44441156 or a couple sectors further. But in your case sda2 starts at sector 390707200 - 186 GB from the start of the disk while sda1 only takes up good 21 GB of that space and the other 165 GB are just lost unused space between sda1 and sda2.
When you boot up your original machine to get the disk usage (df -h
), please run fdisk -l /dev/sda
as well and post the full output here.