Description of problem: Preupgrade failed on reboot due to parted crash. Version-Release number of selected component (if applicable): How reproducible: Everytime Steps to Reproduce: 1. preupgrade 2. reboot 3. parted crashes Actual results: Expected results: Additional info:
Created attachment 500682 [details] ks.cfg
Created attachment 500683 [details] syslog
Created attachment 500684 [details] screenshot
Created attachment 500685 [details] anaconda.log
Created attachment 500686 [details] program.log
Created attachment 500687 [details] storage.log
Created attachment 500688 [details] X.log
(In reply to comment #3) > Created attachment 500684 [details] > screenshot Another screenshot is available at http://yfrog.com/i3100mediaimag0015j
That tiny image is really quite useless. Can you get a better one? Also, on the running system what does parted -l do? If this is the CHS guessing bug then it should blow up as well.
Created attachment 500711 [details] better screenshot? This one should be better. The original was compressed in size and resolution.
Does it matter if I do 'parted -l' or 'parted /dev/sda -s p | tee /mnt/usb/parted.sda'
Either is fine, if it is the CHS bug it will be obvious.
Created attachment 500722 [details] parted -l output
Created attachment 500723 [details] screentshot actual output
(In reply to comment #13) > Created attachment 500722 [details] > parted -l output Hi Kyle, thanks for the attachment. Please note, most developers aren't huge fans of attaching text/plain output as a word document. I've converted your attachment to a simple text document, and included it below to aid any other tests in finding this issue when searching for known failures. Number Start End Size Type File system Flags 1 1049kB 525MB 524MB primary ext4 boot 2 525MB 160GB 160GB primary lvm Backtrace has 13 calls on stack: 13: /lib64/libparted.so.0(ped_assert+0x2e) [0x7f2c8002babe] 12: /lib64/libparted.so.0(+0x3c036) [0x7f2c80055036] 11: /lib64/libparted.so.0(+0x3c41e) [0x7f2c8005541e] 10: /lib64/libparted.so.0(+0x3cae6) [0x7f2c80055ae6] 9: /lib64/libparted.so.0(ped_disk_add_partition+0x1a3) [0x7f2c80031873] 8: /lib64/libparted.so.0(+0x3e279) [0x7f2c80057279] 7: /lib64/libparted.so.0(+0x3ef95) [0x7f2c80057f95] 6: /lib64/libparted.so.0(ped_disk_new+0x58) [0x7f2c80031cd8] 5: parted() [0x4071b1] 4: parted() [0x407f7a] 3: parted(main+0x1483) [0x4063c3] 2: /lib64/libc.so.6(__libc_start_main+0xed) [0x7f2c7f83243d] 1: parted() [0x406411] 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 dos.c:661 in function probe_partition_for_geom() failed. Aborted (core dumped)
Can we get an update on this bug?
Do you have a USB flash drive plugged in? This error is usually seen with factory partitioned USB sticks, and in that case the work around is to erase the partition table using dd if=/dev/zero of=/dev/DEVICE bs=1M count=1 and re-partition it. I have a new build of parted for f15 in updates-testing that fixes this by removing the assertion when the CHS guess fails. *** This bug has been marked as a duplicate of bug 704669 ***
Yes I do have a a USB flash drive plugged in. If I unplug it the problem will go away?
Probably so.