Clonezilla 2.5.6-22 - Error with Restoring Image with Extended Partition

[Al Dorrington]

I have a CentOS system with 9 partitions.

sda   sda    465.8G disk         
sda1  |-sda1     1G part ext4                                                
sda2  |-sda2 304.8G part ext4                                                
sda3  |-sda3   100G part ext4                                                
sda4  |-sda4     1K part                                                     
sda5  |-sda5    16G part ext4                                                
sda6  |-sda6    16G part swap                                                
sda7  |-sda7    12G part ext4                                                
sda8  |-sda8     8G part ext4                                                
sda9  `-sda9     8G part ext4    

sda4 is an extended partition, that contains sda5,6,7,8,9.
When I try to restore this image to a second computer, it appears that the restore attempts to restore sda5,6,7,8,9, before creating the extended partition sda4.
I see errors after the attempts to restore sda5,6,7,8,9 of:

Informing the OS of partition table changes...blockdev: ioctl error on BLKRRPART: Device or resource busy.

Then at the very end:

Probing sda with blockdev before restoring EBR...
blockdev: ioctl error on BLKRRPART: Device or resource busy.
Finding extended partition(s) in parted table /home/partimag/2018-11-12-16-img/sda-pt.parted...
Restoring extended boot record (EBR) in extended partition /dev/sda4...
Unable to find target partition "sda4".
The disk and partiion in this system:
(this shows everything but sda4...)
Check if the partiion sda4 really exists, otherwise maybe the kernel is too old.
Program terminated!.

I do not see any attempt to create an extended partition for sda4 before restoring sda5,6,7,8,9.
Not sure if there is anything I can do manually to restore this image.
I do not see any options under the Expert mode to manage this either.

I have spent some time searching for similar issues, and it seems like Clonezilla has gotten the restore order wrong in the past, so maybe someone accidentally broke this again?

Any suggestions would be greatly appreciated, I have been struggling with this all morning.

[Al Dorrington]

I tried going back to Clonezilla 2.4.2-61, and that worked properly.
So something is definitely broken between 2.4.2-61 and 2.5.6-22

[Steven Shiau]

Is this issue reproducible with testing Clonezill alive, e.g., 2.6.0-24 or 20181128-*?

Steven