Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Kingston 1gig usb with unknown partition. Tried to create a partition and it crashed. Version-Release number of selected component: parted-3.2-4.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: parted /dev/sdc crash_function: ped_assert executable: /usr/sbin/parted kernel: 3.19.8-200.fc21.x86_64 runlevel: N 5 type: CCpp uid: 0 var_log_messages: [System Logs]:\n-- Logs begin at Fri 2015-05-15 07:04:00 EDT, end at Thu 2015-05-28 18:14:26 EDT. -- Truncated backtrace: Thread no. 1 (5 frames) #2 ped_assert at debug.c:111 #3 ped_disk_get_partition at disk.c:1597 #4 command_line_get_partition at ui.c:1051 #5 do_name at parted.c:866 #6 interactive_mode at ui.c:1593
Created attachment 1031487 [details] File: backtrace
Created attachment 1031488 [details] File: build_ids
Created attachment 1031489 [details] File: cgroup
Created attachment 1031490 [details] File: core_backtrace
Created attachment 1031491 [details] File: dso_list
Created attachment 1031492 [details] File: environ
Created attachment 1031493 [details] File: limits
Created attachment 1031494 [details] File: maps
Created attachment 1031495 [details] File: open_fds
Created attachment 1031496 [details] File: proc_pid_status
That's pretty weird. It looks like dev didn't get setup properly and a bunch of other checks didn't catch it. Could you attach the first 34 sectors of the device? dd if=/dev/sdc of=disklabel.bin bs=512 count=34
Created attachment 1032322 [details] lsusb -v
I had already used fdisk to partition it. I did attach lsusb -v and did not see that I had to uncheck the providing information checkbox. If there's any test I can run on it I will. It may be a problem with my system or it's a fake Kingston stick since it came with our logo on it from 'a very cheap vendor'.
Does parted still crash after using fdisk on it?
I had intended to change to a clean install of Fedora 22 LXDE spin so did that. As long as I leave the fdisk work alone and just delete the partition and repartition it with parted it works fine. I just now did the following. I wiped it with dd stopping at an arbitrary place with CTRL-C. $dd if=/dev/zero of=/dev/sdd 122721+0 records in 122721+0 records out 62833152 bytes (63 MB) copied, 38.7635 s, 1.6 MB/s $parted /dev/sdd GNU Parted 3.2 Using /dev/sdd Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) p Error: /dev/sdd: unrecognised disk label Model: Kingston DataTraveler 2.0 (scsi) Disk /dev/sdd: 1000MB Sector size (logical/physical): 512B/512B Partition Table: unknown Disk Flags: (parted) n Error: /dev/sdd: unrecognised disk label Partition number? 1 Backtrace has 8 calls on stack: 8: /lib64/libparted.so.2(ped_assert+0x44) [0x7f41dc1912f4] 7: /lib64/libparted.so.2(+0x11a15) [0x7f41dc195a15] 6: parted(command_line_get_partition+0x4d) [0x40b63d] 5: parted() [0x4078a2] 4: parted(interactive_mode+0xff) [0x40c9ef] 3: parted(main+0x119f) [0x405f1f] 2: /lib64/libc.so.6(__libc_start_main+0xf0) [0x7f41db970790] 1: parted() [0x405f77] 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 (3.2) 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 (disk != NULL) at disk.c:1597 in function ped_disk_get_partition() failed. Aborted (core dumped)
Oh! I didn't realize you were trying to create a partition without first making a disklabel. That's less serious of a bug than I was thinking. You need to use mklabel msdos or gpt before you can create any partitions on it. But we should also be checking to make sure there is a recognized disklabel before allowing other commands.
parted-3.2-9.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/parted-3.2-9.fc21
parted-3.2-9.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/parted-3.2-9.fc22
Package parted-3.2-9.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing parted-3.2-9.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-11715/parted-3.2-9.fc21 then log in and leave karma (feedback).
parted-3.2-9.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
parted-3.2-9.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.