With clonezilla-live version stable - 2.5.0-25 i tried to make image of one hdd 320GB which had 3 partitions: /dev/sdb1 (boot,ext4),/dev/sdb2(root,ext4) and /dev/sdb3(swap) to a usb 3.0 external hdd 2TB (one partition ntfs).
When action is at second partition (/dev/sdb2) I got this message:
"extfsclone.c bitmap error at 89 group"
I checked all partition with fsck -f (all are clean),but cannot do the image of hdd.
What could generate that error?
I successfully made an image of 1TB hdd (3 partitions ntfs of Win10) with the same version of clonezilla-live to usb 3.0 external hdd 2TB (one partition ntfs).
Last edit: koni 2017-03-03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Does your issue still remain? If so, could you please give Clonezilla live 2.5.0-31 a try? http://clonezilla.org/downloads.php
It comes with updated Partclone (0.2.90) so the results might be different.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Had the same problem when I was trying to save the disk of a Debian stretch RC3 PC.
Fixed it like you said with the latest test version of clonezilla (2.5.1-23)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Clonezilla-3.19.17-noarch-2 also exhibited this behavior when cloning a drive that was automatically partioned by the Debian 9.3 (Stretch) installer. The Debian installer does not seem to adhere to the old fashioned MBR tradition of partitions starting on physical sector boundaries.
I confirmed the issue was not due to remnants of an invalid GUID partition map as I zapped (cleared) that partion map to rule that out.
I have confirmed that clonezilla-live-2.5.2-31-amd64 handles this partition map with no problem. I have not tried the latest arch linux version to see if it is resolved there.
The following is the partition map as printed by fdisk that caused the problem:
I realise this post is old but thought I would share my findings anyway.
Using Clonezilla 2.5.0-5 with Partclone 0.2.89.
I am using Clonezilla to make clone images of various Linux installations as I test them on an Acer CB5-571 Chromebook with a 16GB SSD.
1) After I install Fedora Linux 33 on the Chromebook, Clonezilla 2.5.0-5 WILL create an image and WILL restore the image to the Chromebook successfully.
But
2) After installing Gallium OS Linux 3.1 Broadwell (which is touted as being ideal for Chromebooks, and it is based on Ubuntu), Clonezilla 2.5.0-5 will NOT create an image of the SSD. It fails with the error "extfsclone.c: bitmap error bitmap error at 39 group".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
With clonezilla-live version stable - 2.5.0-25 i tried to make image of one hdd 320GB which had 3 partitions: /dev/sdb1 (boot,ext4),/dev/sdb2(root,ext4) and /dev/sdb3(swap) to a usb 3.0 external hdd 2TB (one partition ntfs).
When action is at second partition (/dev/sdb2) I got this message:
"extfsclone.c bitmap error at 89 group"
I checked all partition with fsck -f (all are clean),but cannot do the image of hdd.
What could generate that error?
I successfully made an image of 1TB hdd (3 partitions ntfs of Win10) with the same version of clonezilla-live to usb 3.0 external hdd 2TB (one partition ntfs).
Last edit: koni 2017-03-03
Does your issue still remain? If so, could you please give Clonezilla live 2.5.0-31 a try?
http://clonezilla.org/downloads.php
It comes with updated Partclone (0.2.90) so the results might be different.
Steven
Had the same problem when I was trying to save the disk of a Debian stretch RC3 PC.
Fixed it like you said with the latest test version of clonezilla (2.5.1-23)
@ForYit,
Thanks for confirming that this issue is fixed in Clonezilla live 2.5.1-23.
Steven
Clonezilla-3.19.17-noarch-2 also exhibited this behavior when cloning a drive that was automatically partioned by the Debian 9.3 (Stretch) installer. The Debian installer does not seem to adhere to the old fashioned MBR tradition of partitions starting on physical sector boundaries.
I confirmed the issue was not due to remnants of an invalid GUID partition map as I zapped (cleared) that partion map to rule that out.
I have confirmed that clonezilla-live-2.5.2-31-amd64 handles this partition map with no problem. I have not tried the latest arch linux version to see if it is resolved there.
The following is the partition map as printed by fdisk that caused the problem:
I realise this post is old but thought I would share my findings anyway.
Using Clonezilla 2.5.0-5 with Partclone 0.2.89.
I am using Clonezilla to make clone images of various Linux installations as I test them on an Acer CB5-571 Chromebook with a 16GB SSD.
1) After I install Fedora Linux 33 on the Chromebook, Clonezilla 2.5.0-5 WILL create an image and WILL restore the image to the Chromebook successfully.
But
2) After installing Gallium OS Linux 3.1 Broadwell (which is touted as being ideal for Chromebooks, and it is based on Ubuntu), Clonezilla 2.5.0-5 will NOT create an image of the SSD. It fails with the error "extfsclone.c: bitmap error bitmap error at 39 group".
First, it's recommended try to use the latest stable Clonezilla live when you encounter an issue:
https://clonezilla.org/downloads.php
Second, it seems the source machine has file system integrity issue, so you can choose "-fsck-y" when saving:
https://clonezilla.org/clonezilla-live/doc/01_Save_disk_image/images/ocs-10-4-check-source-fs.png
Steven