Bug 1022952 - Existing boot partitions are not recognized during GRUB2 installation
Existing boot partitions are not recognized during GRUB2 installation
Product: Fedora
Classification: Fedora
Component: grub2 (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Peter Jones
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-10-24 06:47 EDT by Marian Csontos
Modified: 2015-06-29 08:42 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-06-29 08:42:44 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Marian Csontos 2013-10-24 06:47:29 EDT
Description of problem:
I have a machine with another OS (linux) in a LV.
When installing grub2 boot loader the boot entries are not found.
However these are correctly recognized by grub2's os-prober once I boot into the installed Fedora.

I tried first without selecting disks containing the other OS (as I did not want installation process to touch them) and when existing OS was not recognized then with them still to no avail.

After I activated the LVs by hand they were finally recognized.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. install F20 in dual boot with another Linux installed on LV

Actual results:
- the existing system is not found

Expected results:
- installer should find other OSes (at least on all selected and/or local disks)

Additional info:

Final Requirements say:

> Windows dual boot
> The installer must be able to install into free space alongside
> an existing clean Windows installation and install a bootloader
> which can boot into both Windows and Fedora. 

Though I understand that is a common use case, sad it does not require other GNU/Linux distros as well. We should invest more into promoting Fedora to other distros' users too.
Comment 1 Fedora End Of Life 2015-05-29 05:37:37 EDT
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.
Comment 2 Fedora End Of Life 2015-06-29 08:42:44 EDT
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

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.