@Sebastian-Roth Yeah, that’s the VM I build the images on. I apologize, I misread your request.
On the plus side, I just did an upgrade from the trunk and everything worked perfectly. I was able to capture and deploy an image and everything expanded properly.
I really appreciate the work that you guys put into FOG, it’s a phenomenal project! I owe you guys a beer!
@Sebastian-Roth Hey Sebastian, I know you guys are probably super busy, but I just wanted to check in and see if any progress was made on this? or if you need any more info from me.
Hey Svein,
I work at a school district and we rely heavily on FOG and Ubuntu. We can now push down an Ubuntu image in about 50 seconds which is 10X faster than our previous proprietary imaging software. In my experience, using GIT to install and update FOG is an absolute breeze.
I have a little write up on my use of FOG on my website,
http://aaronprisk.com/2015/07/25/imaging-with-fog/
Hopefully that helps some 
~Aaron
@Sebastian-Roth Great, I’ll do whatever I can to assist!
On the partition thing, that’s my fault. I fired up the wrong vm where I had tried switching the ext and swap partitions to see if it would expand.
@Wayne-Workman I just tried setting the image to only upload the ext4 partition and it failed shortly after an error came up. I was able to snag a quick screenshot.
It may be a totally unrelated issue, but I figured id report it either way.
@Wayne-Workman I can’t remember the exact version, but it would have been around the first week of May.
I snapped some screenshots.
Here’s a machine imaged last week:
Here’s one from today:
Yessir, we have a pretty big deployment of Linux machines and up until recently they expanded without issue.
We recently pulled down the latest FOG build (8038 as of the moment) and noticed our image partitions weren’t properly expanding. Our table had ext4 at the start followed by our swap partition and after image the ext4 didn’t expand to fill the drive. The image is marked as single disk resizable which has worked flawlessly in the past.
I don’t believe it’s a corrupted image as we’ve imaged about 1000+ machines with this image, but just to be sure, I captured a clean Ubuntu 14.04 and 16.04 image (via VirtualBox) and ran into the same problem.
I did notice during one of the deployments an error prior to PartClone starting stating “Error on Logical Partition”
If anyone has any suggestions, please send them my way.
Thanks,
Aaron
