Hide Forgot
Description of problem: I have a computer with four drives, and an attempted install on Fedora is almost impossible to do because of your partitioning tools. During install, because I want to preserve information on one drive which is to be used as /home I choose custom partitioning. Installer asks for biosboot partition, and keeps on asking even after one is added. It's impossible to view the partition layout and make necessary adjustments, because it's hidden for users, and you're reduced to hoping the installer does what is needed. After installing, when I've chosen to install grub on a drive that isn't the same as the one where / is, it still does not boot. How reproducible: Always Steps to Reproduce: 1. Start anaconda 2. Select custom partitioning Actual results: Impossible to view installation layout, or drive layout when you set up partitions. Can't delete biosboot partitions if you add more than one in error. Expected results: Being able to review and add/delete partitions on drives. Let me know if you need anymore info.
Please attach the logs from /tmp to this bug as individual, text/plain attachments. As to viewing the partitions on a particular drive, this is visible in the "Device(s)" section of the information for a mountpoint. Since Fedora 18 anaconda has presented a top-down view of partitioning in order to better facilitate the use of multi-device storage layouts.
Created attachment 1152415 [details] Anaconda log This time I didn't even get to perform the install, as the installer bugs out after I've added a biosboot and simply says there's something wrong with my storage configuration.
Also, the "devices" section is greyed out, so I can't view that. The older anaconda installer, flawed as they were, allowed me to view the drives and the partitions pertaining to the drives in a graphical matter. Small addendum as well; When trying to erase the drive from the custom partitioning menu, it will erase _all_ devices if I choose so, even I just want it to wipe that one drive.
I've uploaded some screenshots of the setup and how it looks like in the system when trying UEFI install as well. They can be found here: http://imgur.com/a/4uHA6
(In reply to Jon Jahren from comment #0) > Description of problem: > I have a computer with four drives, and an attempted install on Fedora is > almost impossible to do because of your partitioning tools. Perhaps a read through this will help: https://docs.fedoraproject.org/en-US/Fedora/23/html/Installation_Guide/sect-installation-gui-manual-partitioning.html
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.