@Sebastian-Roth
Thanks for the information.

Using non-resizable solved this problem.

@Sebastian-Roth
I never noticed that problem with dual boot systems. Everything worked fine. I noticed it when upgrading the Linux system and having the error that there was not enough space on “/dev/sda5”. At that moment I was using the version 1.5.7 and now with the latest version 1.5.8.
The partition “/dev/sda5” has a normal size of 419 GB and the partition “/dev/sda6” has the size of 657 GB. When deploying the partition “/dev/sda6” expands to the normal size but the partition “/dev/sda5” just gets the size of 8.9 GB.

Looking at the disk structure then everything starts at the normal start offsets (as mentioned in d1.partitions and d1.minimum.partitions), just the gap between “/dev/sda5” and “/dev/sda6” is set as an unallocated space.

Why does the partition “/dev/sda6” expands to the normal size and the partition “/dev/sda5” not ?

Hi,

I have a hard drive with DOS table and 3 primary partitions and 1 extended partition. Within this extended partition there are 3 logical partitions (2 ext4 Linux and a swap).
I am using the compression method “Partclone Zstd” and “image type Resizable”.

After capturing the disk I want to deploy it to other machines but when all is done there is one partition which is not expanded as it should be. This is the first logical partition (/dev/sda5) which has the boot for the Linux machine.

d1.partitions
label: dos
label-id: 0x612b3879
device: /dev/sda
unit: sectors

/dev/sda1 : start = 2048, size = 1024000, type=7, bootable
/dev/sda2 : start = 1026048, size= 818176000, type=7
/dev/sda3 : start = 819202048, size = 819200000, type=7
/dev/sda4 : start = 1638404094, size = 2268624898, type=5
/dev/sda5 : start = 1638404096, size = 878899200, type=83
/dev/sda6 : start = 2517306369, size = 1379879424, type=83
/dev/sda7 : start = 3897185794, size = 9836544, type=82

d1.minimum.partitions
label: dos
label-id: 0x612b3879
device: /dev/sda
unit: sectors

/dev/sda1 : start = 2048, size = 1024000, type=7, bootable
/dev/sda2 : start = 1026048, size= 818176000, type=7
/dev/sda3 : start = 819202048, size = 819200000, type=7
/dev/sda4 : start = 1638404094, size = 2268624898, type=5
/dev/sda5 : start = 1638404096, size = 18920857, type=83
/dev/sda6 : start = 2517306369, size = 4269039, type=83
/dev/sda7 : start = 3897185794, size = 9836544, type=82

d1.fixed_size_partitions
1:4:7

What could be the problem ?

Thanks
Miguël

@Quazz
Problem is that the image/partition is not expanding to the full size after deploying. It worked in previous versions but from 1.5.7 until the latest version it just kept the schrinked/resized value.

This is just happening for 1 partition, all the others are expanding as they should do.

I have the same problem using version 1.5.7 and 1.5.8 (latest one).
My Linux partition of has the size of 500 Gb and over capturing and deploying the mage my Linux partition now has a size of 8.6 Gb.

Maybe this can be solved as quickly as possible ?

Thanks
Miguël

@Tom-Elliott
Will you post a message if the update will be ready ?

More info
“Check extfs volume --> Done”
“/^Block[”
“^ unterminated regexp”
“error : Invalid regular expression : /^Block[/”
"BEGIN {PRINTF “%.0f\n”, 2153085}"
“syntax error”
"BEGIN {PRINTF “%.0f\n”, 5/100}"
“syntax error”
“BEGIN {PRINTF “%.0f\n”, +}”
“syntax error”
“Init version 20200201”
“Error calculating the new size of extfs (shrinkPartition)”**

What went wrong and how can I solve this problem ?

Thanks
Miguël

Hi,

I just updated to version 1.5.7.103 and during capture I receive the syntax error on resizing ext partition. The syntax error is set on “awk : cmd line 1”.

Is it possible to solve that problem ?

Thanks
Miguël