Created attachment 664200 [details] screenshot showing the dupplicate biosboot entries Description of problem: This Guest is a replica of my main F17 system (with smaller disk sizes). So, there are two biosboot partitions (vda1, vdb1). But it is enough for anaconda to just install the bootloader into vda1. I normally setup vdb1 manually later. When i select the desired biosboot partition and mark it as 'reformat', it shows up twice in the 'New Fedora...' tree. Since there are two biosboot partitions (vda1 and vdb1) and i only intend to reformat vda1, it might cause confusion. Version-Release number of selected component (if applicable): anaconda 18.37.2 How reproducible: always Steps to Reproduce: 0. Boot anaconda with 'gpt' boot parameter. I don't know if it is requiered, since the disks are already partitioned, but just in case. 1. Select my favorite anaconda settings (spanish, buenos aires, kde) 2. Enter STORAGE: INSTALLATION DESTINATION and select only vda and vdb. 3. Perform MANUAL PARTITIONING (Do not chage the scheme). 4. Expand the 'unknown' tree and select vda1 (biosboot). Expand the 'customize' tree and check 'reformat' and 'apply changes'. 5. Expand the 'New Fedora 18...' tree and there will be two 'biosboot' entries instead of only one. 6. It is possible to perform the installation correctly. It looks like there are two duplicated entries. Actual results: it looks like a cosmetic issue. Expected results: no duplicated entries in the 'New Fedora...' tree. Additional info:
Please attach logs from /tmp/*log as individual plain/text files.
Created attachment 665822 [details] anaconda.log
Created attachment 665823 [details] storage.log
Created attachment 665824 [details] program.log
Created attachment 684034 [details] [18.37.11] screenshot showing duplicate BIOS Boot entries Reproduced with anaconda-18.37.11-1.fc18 using one disk and gparted. Create an empty disk image: $ qemu-img create f18-test-3.img 12G Start the Live image: $ qemu-kvm -m 2048 -hda f18-test-3.img -cdrom ~/xfr/fedora/F18/F18-Final/Final/Fedora-18-x86_64-Live-Desktop.iso -vga qxl -boot menu=on -usbdevice mouse Install gparted and configure the disk with one bios_grub partition: 1. Create a gpt partition table. 2. Create an unformatted, 1 MiB partition. 3. Set the bios_grub flag on the partition. 4. Quit. Start the installer. Proceed to Manual Partitioning. Click "+" to expand the Unknown installation. Click "+" to expand Customize. Click Reformat. Click Apply Changes. Click "+" to expand New Fedora 18 Installation. BIOS Boot is displayed twice. Both copies show sda1 as the name.
Created attachment 684035 [details] [18.37.11] anaconda.log
Created attachment 684039 [details] [18.37.11] program.log
Created attachment 684040 [details] [18.37.11] storage.log
anaconda-21.48.10-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/anaconda-21.48.10-1.fc21
Package anaconda-21.48.10-1.fc21, pykickstart-1.99.63-2.fc21, python-blivet-0.61.5-1.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 anaconda-21.48.10-1.fc21 pykickstart-1.99.63-2.fc21 python-blivet-0.61.5-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-12944/pykickstart-1.99.63-2.fc21,python-blivet-0.61.5-1.fc21,anaconda-21.48.10-1.fc21 then log in and leave karma (feedback).
anaconda-21.48.10-1.fc21, pykickstart-1.99.63-2.fc21, python-blivet-0.61.5-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.