(This is a re-send attempt as I seems to be failed to send to the
mailing list itself)
Hi, I have the similar symptom myself so I'd like to share some of my
details.
I recently bought an Intel SSDSC2BW240H6 240GB SSD and (probably)
formatted to a msdos partition table using GNOME Disks(which seems to be
Parted-based) then partitioned to "install" Ubuntu 16.04(and by
"install" I mean I formatted an EXT4 filesystem and rsync'd the entire
rootfs of my previously using Ubuntu 16.04 to the new filesystem then
re-install the bootloader) via an USB 3.0 USB-to-SATA interface on a
laptop. The "install"ation went normally.
Then after few days later, recently, I plugged the new SSD on my desktop
and working on a project which internally calls `parted` command for
some information I encountered this "bug".
``````````````
Backtrace has 14 calls on stack:
14: /lib/x86_64-linux-gnu/libparte
d.so.2(ped_assert+0x44) [0x7f653c3dcea4]
13: /lib/x86_64-linux-gnu/libparted.so.2(+0x1e45f) [0x7f653c3f045f]
12: /lib/x86_64-linux-gnu/libparted.so.2(+0xf8ba) [0x7f653c3e18ba]
11:
/lib/x86_64-linux-gnu/libparted.so.2(ped_disk_add_partition+0x25f)
[0x7f653c3e21af]
10: /lib/x86_64-linux-gnu/libparted.so.2(+0x1dd4f) [0x7f653c3efd4f]
9: /lib/x86_64-linux-gnu/libparted.so.2(+0x1dde0) [0x7f653c3efde0]
8: /lib/x86_64-linux-gnu/libparted.so.2(+0x1dd89) [0x7f653c3efd89]
7: /lib/x86_64-linux-gnu/libparted.so.2(+0x1ed75) [0x7f653c3f0d75]
6: /lib/x86_64-linux-gnu/libparted.so.2(ped_disk_new+0x48)
[0x7f653c3e1dd8]
5: parted/.libs/lt-parted() [0x407163]
4: parted/.libs/lt-parted(non_interactive_mode+0x92) [0x40cdb2]
3: parted/.libs/lt-parted(main+0x1082) [0x405ee2]
2: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)
[0x7f653bbba830]
1: parted/.libs/lt-parted(_start+0x29) [0x406089]
You found a bug in GNU Parted!(...)
Assertion (metadata_length > 0) at ../../../libparted/labels/dos.c:2313
in function
add_logical_part_metadata() failed.
```````````````
I can still reproduce on current master branch.
I'm a 100% Ubuntu/GNU/Linux user and I alway use Parted-based
application to do disk partitioning so I'm pretty sure it's not some
proprietary applications' issue. Here's the fdisk output:
```
Welcome to fdisk (util-linux 2.27.1).(...)
Command (m for help): print
Disk /dev/sda: 223.6 GiB, 240057409536 bytes, 468862128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xf2e75007
Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 19533297 19531250 9.3G ef EFI (FAT-12/16/32)
/dev/sda2 19533824 39065073 19531250 9.3G 83 Linux
/dev/sda3 39065600 468862127 429796528 205G f W95 Ext'd (LBA)
/dev/sda5 39067648 468858879 429791232 205G 83 Linux
/dev/sda6 468858880 468860927 2048 1M 83 Linux
```
Ｖ字龍 <vdragon.tai...@gmail.com <mailto:vdragon.tai...@gmail.com>>
