Description of problem: Version-Release number of selected component: anaconda-18.6.4 Additional info: libreport version: 2.0.12 cmdline: BOOT_IMAGE=/images/pxeboot/vmlinuz nomodeset root=live:LABEL=CFL_17 kernel: 3.6.0-0.rc2.git2.1.fc18.i686
Created attachment 608846 [details] File: ifcfg.log
Created attachment 608847 [details] File: anaconda-tb
Created attachment 608848 [details] File: environ
Created attachment 608849 [details] File: type
Created attachment 608850 [details] File: storage.log
Created attachment 608851 [details] File: version
Created attachment 608852 [details] File: program.log
Created attachment 608853 [details] File: product
Created attachment 608854 [details] File: syslog
Created attachment 608855 [details] File: hashmarkername
Created attachment 608856 [details] File: anaconda.log
Created attachment 608857 [details] File: release
Created attachment 608858 [details] File: description
What steps did you take that led to this situation?
Steps are: 1. Have vmlinuz, initrd.img and squashfs.img on a USB. 2. Boot from this USB 3. In the central screen chose http-installation from a server in my network that has the tree for F18a TC5. 4. Chose minimal install and added base. 5. Came to the partitioning screen and selected drive. On this drive I have a disk layout from a previous F17. But as far as I recall the F17 was not on the system anymore. Layout: Boot partition Ext4 1024M, Root partition Ext4 30000M, Swap partition 4096M. 6. I do not exactly what I clicked and in which order, but I tried to create a partitioning scheme where anaconda was satified with. Then BOOM exception, that I send to bugzilla. With TC5 I have now tried several strategies to create a partitioning scheme to install on, but without exception I end up in an exception.
Can reproduce this one now. I ereased all partitions with the windows installtion program and installed a small win-partition. Then followed the steps from comment #15 clicked the destination icon, selected the only disc show in the menu, did not check the review field and selected "continue". Exception then comes after 2 or 3 seconds.
The same symptom is reproducible in anaconda-18.6.7 booted from DVD on a machine with exactly one harddrive that has a GPT disk label and no partitions. Ask to review layout, "Click here to make all mount points now" then [Continue].
(In reply to comment #15) > Steps are: > 1. Have vmlinuz, initrd.img and squashfs.img on a USB. > 2. Boot from this USB > 3. In the central screen chose http-installation from a server in my network > that has the tree for F18a TC5. > 4. Chose minimal install and added base. > 5. Came to the partitioning screen and selected drive. On this drive I have > a disk layout from a previous F17. But as far as I recall the F17 was not on > the system anymore. Layout: Boot partition Ext4 1024M, Root partition Ext4 > 30000M, Swap partition 4096M. This sounds like a known bug that will be fixed in the first beta trees. Removable devices containing install media are excluded from the initial disk selection, but not from custom partitioning. They should be excluded from both, especially since all selected disks are treated as fair game for partition allocation. There may be other issues related to GPT disklabels on BIOS systems. We'll have to wait and see.
(In reply to comment #17) > The same symptom is reproducible in anaconda-18.6.7 booted from DVD on a > machine with exactly one harddrive that has a GPT disk label and no > partitions. Ask to review layout, "Click here to make all mount points now" > then [Continue]. Please attach your logs.
Created attachment 612612 [details] anaconda-tb-* traceback and debuginfo Reproduced with anaconda-18.6.8: one drive [brand new, never used], GPT, no partitions.
Created attachment 612614 [details] storage.log One drive [brand new, never used], GPT, no partitions.
Created attachment 612615 [details] storage.state
Created attachment 612616 [details] syslog (/var/log/messages)
Thanks. So there's also a bug about whether to add a BIOS boot partition during automatic partitioning. I have a patch, so it should be resolved in the earliest beta trees as well.
anaconda-18.10-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.10-1.fc18
Package anaconda-18.10-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.10-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-14933/anaconda-18.10-1.fc18 then log in and leave karma (feedback).
anaconda-18.11-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.11-1.fc18
anaconda-18.12-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.12-1.fc18
This bug looks to have been fixed for many anaconda builds now but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug. (tested a gpt autopart install of Beta RC1 by passing 'gpt' on cmdline, worked fine, created a BIOS boot part.)