Bug 1132237
| Summary: | boot device reverts to sda if custom partition (GPT/ EFI) chosen | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Hugh Sutherland <hfs98> | ||||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | low | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 20 | CC: | anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2015-06-29 22:10:12 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 928984 [details]
anaconda.log
Created attachment 928985 [details]
anaconda.storage.log
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. |
Created attachment 928983 [details] virtual appliance with sda already partitioned (install .iso not included) Description of problem: boot device reverts to sda when the manual partition screen is entered. Version-Release number of selected component (if applicable):20.25.15-1 How reproducible:seems repeatable Steps to Reproduce: 1. boot from Fedora-Live-Xfce-x86_64-20-1.iso (EFI mode) 2. format both sda and sdb as GPT 2a. include an EFI System partion on sda (may not be necessary) 3. start the installer 4. Select language and continue 5. Click Installation Destination 6. Select drives on both sda and sdb 7. Click "Full disk summary and bootloader" , set sdb as the boot device, then click Done. 8. Choose "I want to review/_modify..." and click Continue 9. On the Manual Partitioning screen, click "2 storage devices selected" Actual results: On my system, sda was selected as the boot device. After I set up my partitions, this resulted in messages You have not created a bootloader stage 1 target device You have not created a bootable partition Expected results: I expected anaconda to preserve sdb as the boot device Additional info: Workaround: (starting from the "You have not created a ..." 1. Choose Modify Storage Layout to close the error dialog 2. Click "Full Disk summary and bootloader" 3. Change the boot device back to sdb 4. Click Done 5. On the Installation Options dialog, ignore the warnings about insufficient space and choose Custom Partitioning 6. back in the Manual Partioning screen, optionally click "2 storage devices selected" to verify that sdb was retained as the boot device. (At least in my case, anaconda retained the custom partitions I had set up earlier). 7. Click Done, and Accept Changes Background: I wanted to install Fedora 20 to SSD on my shiny new UEFI system and use an HDD for data storage. After research I elected to put swap, /var, and /home on the HDD also, to reduce wear and tear on the SSD. then I thought it might be prudent to partition the HDD so it could contain a "rescue OS" in case the SSD failed. (I haven't chosen the OS yet). Anyway, I fully partitioned and formatted both disks before attempting installation. But in later experiments I left sdb un-partitioned because anaconda seemed OK in automatic partitioning mode. I'll attempt to attach a "virtual appliance" that already has step 2 completed. It behaves the same way in VirtualBox on my system. I'll also try to attach anaconda.log and anaconda.storage.log, but they are both huge and confusing because I "messed around" quite a bit during the install trying to understand and document the behavior.