512GB image not resizing for smaller drive

brianm

We FINALLY switched from our ancient CloneDeploy setup to Theopenem, and have been very happy with it until I hit a snag for the first time today. Our standard image was created on a system with a 512GB drive, but I'm trying to image an older laptop with a 256GB drive and I get an error "244198 MB is Less Than The Minimum Required HD Size For This Image (488386 MB)". Using WIE, and the profile's deploy options have the 'Create Partitions Method' set to dynamic. Not much else I can find in the way of options that would come into play here, neither on the deploy side or during image upload. What am I missing? Or did we just do it wrong? We used to always use a VM for image creation and updating with a pretty small virtual disk that was probably only 100GB, but for this new image we created to upload to our new toems system we just used a new Dell Pro laptop we were setting up, so maybe we just always sidestepped this issue by accident? Hoping for a quick fix but if need be we can just recreate the image and re-upload if that's the only option here.

theopenem_admin

This is very strange, because the WIE uses a file based image, so the required space is always just whatever is used on the hard drive. Can you attach the upload log for this image?

brianm

We may not have that log anymore, this was created weeks ago. If I can find it I'll post it. However, I think you identified the issue for us anyway - the image type is block. That's the default setting and we just left as-is because that's what we used before with CloneDeploy. We're doing a new upload with everything the same except the image type, we'll know if that's the issue soon enough.

brianm

Confirmed that the issue was with the image being created as a block type, working fine after recreating as a file type.

theopenem_admin

Yea the block image in the WIE cannot shrink, it needs to be made from the smallest VM possible. That's why the default WIE is file and default LIE is block.