FOG Partition Problem
-
Hi,
We noticed a change in the d1.minimum.partitions and d1.partitions files between 1.5.5 and 1.5.6.
In version 1.5.5 these 2 files are always identical but this is no longer the case in version 1.5.6Change in the code ?
thanks… -
@phil-dosi The files aren’t supposed to be identical! Please post the contents of those files of one of your images here so I can explain in detail what I mean.
-
Hi,
That’s the content of the files for the Ubuntu18 image captured
(with fog version 1.5.5)
We get the same result by copying to /var/www/fog/service/ipxe
the init_32.xz & init.xz files from 1.5.5 in our new 1.5.6 server…thanks for help
d1.partitions.txt d1.minimum.partitions.txt -
sorry I made a mistake in my comment…(the opposite actually)
the files are captured in v1.5.6 and are identical!
When I use the init_32.xz from 1.5.5 to 1.5.6 the files are differentsnew post : more simple i hope with the same image d1.minimum.partitions in v1.5.5 and
d1.minimum.partitions in v1.5.6d1.minimum.partitions1.5.6.txt d1.minimum.partitions1.5.5.txt
-
@phil-dosi What’s the content of d1.fixed_size_partitions ?
-
@Quazz Partitions are written twice…?
-
@phil-dosi
Hello,
Any news ?
in the end it’s the same behavior with fog server 1.5.5 when capturing an existing imagethanks for all
-
@phil-dosi Sorry, didn’t mean to leave you hanging, but don’t know exactly why this is happening. I can only assume that the resize test failed causing it to think it needed to be captured as is.
-
@phil-dosi You are right. There seems to be a difference between 1.5.5 and 1.5.6 in that it does not see the partition 2 as re-sizable. I am not sure why that is. The only way to find out I suppose is that you schedule a debug capture task. Boot the client machine up and step through the whole capture process and take pictures of the messages on screen. Especially at the point where it does the resize stuff before the blue partclone screens!
