Deployement failed on smaller drive (message "Target partition size smaller")

[Matthieu Jacquart]

Server

• FOG Version: 1.4.4
• OS: Debian 8

Client

• Service Version: 0.11.12
• OS: Win10

Description

Hi,

I have an image made on PC with SSD 128GB, I need to depoy this image on 2 laptop with SSD 60GB, and partclone give me error “Target partition size is smaller than source”

d1.fixed_size_partitions
:2

d1.minimum.partitions :
label: dos
label-id: 0x86308630
device: /dev/sda
unit: sectors
/dev/sda1 : start= 2048, size= 63840, type=7, bootable
/dev/sda2 : start= 1094144, size= 248975360, type=7

d1.partitions :
label: dos
label-id: 0x86308630
device: /dev/sda
unit: sectors
/dev/sda1 : start= 2048, size= 1092096, type=7, bootable
/dev/sda2 : start= 1094144, size= 248975360, type=7

Thanks for your help !
Matthieu

[Matthieu Jacquart]

Ok so I restart my image from scratch with usb installation key containing creators update and no problem to capture image with sysprep, resizing works fine and I can deploy on smaller SSD
So it was certainly a bug in my previous image, thanks for your help

[Quazz]

Looks like it put your second partition as non-resizable, but your first as resizable.

I’m guessing that should be the other way around, so edit d1.fixed_size_partitions and change 2 to 1

Though I’ll be interested in knowing how this happened.

edit: Looking at it, this probably won’t work due to the minimum size specified in d1.minimum.partitions

Under what version was this image captured? It IS set to resizable, yes?

[Matthieu Jacquart]

@Quazz Hi,
I test multiple modification, but always same result :

• I delete “:2” (empty file)
• I replaced by “2” (without ":)
• I replaced by “1”
• I replaced by “:1”

[Quazz]

@Matthieu-Jacquart The image size seems to indicated it being ~248GB large (it’s sectors not bytes facepalm) if I’m not mistaken.

It lists that as minimum size for the partitions, so obviously resizing won’t do anything.

Try to capture it again, I think something went wrong when this one was captured initially.

tl;dr Minimum partition size is the same as the total size, thus resizing is impossible.

[Matthieu Jacquart]

@Quazz I capture this image once again, on another config but still with SSD 128GB, and unable to deploy it on the 2 laptops, same error…

[Matthieu Jacquart]

Same problem on 3 other computers with SSD 120GB instead of 128GB, I need to fix this issue in one hour :(n

[Quazz]

@Matthieu-Jacquart Did you see it try to resize the second partition during capture? It seems like it’s not doing that for some reason.

[Matthieu Jacquart]

@Quazz No I didn’t see that, it appears on partclone screen during capture ?

[Quazz]

@Matthieu-Jacquart It should occur before and after capture, it’s just some text, but it should take some time, even on an SSD it will stay for a few seconds.

What do the partition labels look like? I know FOG ignores partitions with certain labels (to avoid resizing the partition with the boot information on)

And you’re sure the image type is resizable, yes?

[Matthieu Jacquart]

@Quazz I’m sure image type is single disk resizable, I’ve just check in fog.

Here is a capture on PC with SSD 128GB (in french, sorry ;))

I will try to look during capture if I saw text about resizing

[Quazz]

@Matthieu-Jacquart Your issue may be related to https://forums.fogproject.org/topic/10306/windows-10-resizable-image-system-partition-issue/13

At the very least it needs to be addressed since your system reserved partition seems to be getting resized currently, which should never happen. This might potentially (but I don’t think so) cause the second partition to not get resized, but I’m not sure about that.

[Matthieu Jacquart]

@Quazz Ok I’ll take a look to this topic.
But you’re right about resizing, usually I saw “resizing /sda2” (or something like that…) during few second just before partclone capture image, but on this image I don’t see this line, it’s too quick…

[Matthieu Jacquart]

No way, I create new image but once again sda2 is not resized… It’s a big problem for me, 3 pc of direction failed with deployment and people can’t work

[Tom Elliott]

Why is the “main” partition reserved?

[Matthieu Jacquart]

@Tom-Elliott I don’t know, it’s the 500 MB parttion created by windows at installation There’s the same on my own computer.
But I think I understood what happened : it’s directly related to my previous problem with this image : https://forums.fogproject.org/topic/10313/error-capture-windows-10-creator-update-sysprep-could-not-open-inode-xxxxxx-through-the-library
I have 3 image Win10, for 2 of them after upgrade to 1703 no problem, but for the one which give me some trouble, I already have problem to capture image due to “inode” errror message precisely when resizing sda2…
But no solution fot the moment

[Matthieu Jacquart]

Ok so I restart my image from scratch with usb installation key containing creators update and no problem to capture image with sysprep, resizing works fine and I can deploy on smaller SSD
So it was certainly a bug in my previous image, thanks for your help

[Quazz]

@Matthieu-Jacquart I find that Windows 10 upgrades mess up sysprep, I’ve made it a habit to just start over every time.

[Matthieu Jacquart]

@Quazz Yes, but this time I was lucky it was my smallest image with few software ! But it will be problematic for other images with dizains of software… Can you close the topic ? Thanks

[george1421]

@Quazz said in Deployement failed on smaller drive (message "Target partition size smaller"):

I’ve made it a habit to just start over every time.

We also find the same thing and create new every time.
FWIW: We use MDT to build the reference image, that way we have a consistent way to “start over every time”.