Cool! I’ll give that a shot and report back once I test it.

No updates or anything on this? At this point we are regathering our images to deploy them which kinda sucks. But if that’s the solution, we’ll just keep trucking.

I hear you @george1421 . The resize didn’t work for us for awhile but the technician here that does the image uploads noticed that it was working so he started using it.

If we regather and redeploy the image with single disk resize with version 1.3.5, it works fine.

Here is the output from your cmd.

root@FoG-Deb:/# cat /images/Student/d1.original.partitions
# partition table of /dev/sda
unit: sectors

/dev/sda1 : start=     2048, size=   716800, Id= 7, bootable
/dev/sda2 : start=   718848, size=972513280, Id= 7
/dev/sda3 : start=        0, size=        0, Id= 0
/dev/sda4 : start=        0, size=        0, Id= 0
root@FoG-Deb:/# 

@george1421 Yeah, I just edited my response for clarity as well. Sorry about that.

Yeah, we did try that and the issue is the same. Did you want me to capture a screen shot of this as well with PartClone selected?

Edit: Sorry, I just reread your comment and realized you asked me to try partimage. That’s what we actually have selected. That’s what the default was set to.

I’m also having the exact same issue. We captured more info just from above the OP picture. See picture below. All our images are single-disk resize and once we upgraded to 1.3.5, they broke. All images were built in the 1.2.0 release. Thanks for the help.