Hide Forgot
Created attachment 1140578 [details] Partitoning scheme. Description of problem: After installing F24_Alpha-1.7 on an Acer Aspire V nitro next to Windows 10, Fedora does not boot. Version-Release number of selected component (if applicable): F24_Alpha-1.7 How reproducible: Everytime, problem is even worse in F23 Steps to Reproduce: 1. Install F24 using Server product 2. Create partitions next to windows 3. Reboot. Actual results: Computer boots into windows Expected results: Computer show grub boot menu with choice between Fedora and windows. Additional info: When booting into grub from an USB drive, I can load the grub.cfg that was created during install and boot into fedora successfully. This computer has an SSD and an HD drive. Windows is installed on the SSD with an extra partition on the the HD. I install Fedora on the HD. Anaconda does not recognise the EFI-bootpartition created by windows on the SSD, but creates its own EFI-bootpartition on the HD. The EFI boottable does show an entry for fedora, but when I boot from there still windows is started.
Created attachment 1140579 [details] PCI output
Created attachment 1140580 [details] Anaconda.log
Created attachment 1140581 [details] Program.log
Created attachment 1140582 [details] Storage.log
Created attachment 1140583 [details] Dnf.log
Created attachment 1140584 [details] Lvm.log
Created attachment 1140585 [details] Packaging.log
Created attachment 1140586 [details] X.log
Created attachment 1140587 [details] Syslog
Created attachment 1140588 [details] Efibootmgr output
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.