#181 Bug found in GNU Parted by Clonezilla Live

[Rackbrane]

Attempting to create an image of a newly purchased Integral 4GB flash drive, I received the following bug report:

Starting /usr/sbin/ocs-sr at 2013-06-22 22:54:44 UTC...
*.
Clonezilla image dir: /home/partimag
Shutting down the Logical Volume Manager
Finished Shutting down the Logical Volume Manager
The selected devices: sdc
PS. Next time you can run this command directly:
/usr/sbin/ocs-sr -q2 -c -j2 -z1 -i 2000 -p true savedisk 2013-06-22-22-img-Integral-4GB-20130622-disk sdc*.
The selected devices: sdc
Searching for data partition(s)...
Searching for swap partition(s)...
The data partition to be saved: sdc1
The swap partition to be saved:
The selected devices: sdc1
The following step is to save the hard disk/partition(s) on this machine as an image:
*.
Machine: Inspiron 2200
sdc (3.9GB_USB_DISK_2.0USB_DISK_2.0_07012AA2F0647A55-0:0)
sdc1 (3.7G_vfat_USB2(In_USB_DISK_2.0)USB_DISK_2.0_07012AA2F0647A55-0:0)*.
-> "/home/partimag/2013-06-22-22-img-Integral-4GB-20130622-disk".
Shutting down the Logical Volume Manager
Finished Shutting down the Logical Volume Manager
Saving block devices info in /home/partimag/2013-06-22-22-img-Integral-4GB-20130622-disk/blkdev.list...
Checking the integrity of partition table in the disk /dev/sdc...
The partition table in this disk is illegal/invalid: /dev/sdc
It's not supported by parted. Parted is used in Clonezilla to parse the filesystem in the partition table. This partition table is detected as WRONG by parted!
The error messages from parted are:
*****.
Backtrace has 14 calls on stack:
14: /lib/i386-linux-gnu/libparted.so.0(ped_assert+0x29) [0xb76822a9]
13: /lib/i386-linux-gnu/libparted.so.0(+0x42acb) [0xb76b7acb]
12: /lib/i386-linux-gnu/libparted.so.0(+0x432e4) [0xb76b82e4]
11: /lib/i386-linux-gnu/libparted.so.0(+0x4682f) [0xb76bb82f]
10: /lib/i386-linux-gnu/libparted.so.0(+0x1180e) [0xb768680e]
9: /lib/i386-linux-gnu/libparted.so.0(ped_disk_add_partition+0x1d6) [0xb7689c56]
8: /lib/i386-linux-gnu/libparted.so.0(+0x448c0) [0xb76b98c0]
7: /lib/i386-linux-gnu/libparted.so.0(+0x462bf) [0xb76bb2bf]
6: /lib/i386-linux-gnu/libparted.so.0(ped_disk_new+0x61) [0xb768a171]
5: parted() [0x804e71b]
4: parted(non_interactive_mode+0x8e) [0x805625e]
3: parted(main+0x18d8) [0x804dd58]
2: /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xe6) [0xb74dee16]
1: parted() [0x804de25]

You found a bug in GNU Parted! Here's what you have to do:

Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:

Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:

http://ftp.gnu.org/gnu/parted/

Please check this version prior to bug reporting.

If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:

http://www.gnu.org/software/parted

for further information.

Your report should contain the version of this release (2.3)
along with the error message below, the output of

parted DEVICE unit co print unit s print

and the following history of commands you entered.
Also include any additional information about your setup you
consider important.

Assertion (head_size <= 63) at ../../../libparted/labels/dos.c:662 in function probe_partition_for_geom() failed.

*****.
If you continue, something strange might happen (E.g. dd is used, not partimage or ntfsclone, to save the supported file system), and the image you saved maybe not be complete!
Are you sure you want to continue? ? (y/N) Smart choice.
Program terminated!.

[Steven Shiau]

Which version of Clonezilla live did you use?
Could you please try Clonezilla live 2.1.2-20 or 20130703-raring?

BTW, next time please post your question in only one place. Either in the forum, or the bug report. Please do not duplicate that. Thanks.

Steven.

[Rackbrane]

I used i486 version 2.1.1-25.
I have now tried i486 version 2.1.2-20 and obtained the same problem again.

Apologies for the double posting. When I first tried creating a bug report, I seemed unable to post it. That was why I posted in the discussion forum. However, as no response was forthcoming from the forum, I tried the posting the bug report again, and that time I succeeded.