Bug 253924 - Fedora 7.90 Test - Appears to be boot loader problems
Fedora 7.90 Test - Appears to be boot loader problems
Product: Fedora
Classification: Fedora
Component: grub (Show other bugs)
x86_64 Linux
low Severity low
: ---
: ---
Assigned To: Peter Jones
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-08-22 18:43 EDT by Ben Merembeck
Modified: 2009-01-08 23:51 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-08 23:51:21 EST
Type: ---
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 Ben Merembeck 2007-08-22 18:43:10 EDT
Description of problem:

In Fedora 6.90 test 1 - Installed with boot loader in the root partition. It
seemed to install OK, but would not boot when using the chain loader from the
main Fedora 7 installation on this machine. It gets to GRUB and hangs. This
happens with both X86_64 and IA32 install DVDs.

The Machine uses an ECS KN1 lite MB, an Athlon 64 4600 dual core processor with
2 GB of main memory.

How reproducible:

Both X86_64 and IA32 install DVDs broke - so it

Steps to Reproduce:
1. Install to a partition and have Grub install to that partition's boot record.
2. Try to boot the partition with the chain loader from another installation.
Actual results:

The boot process gets to GRUB and hangs
Expected results:

Additional info:
Comment 1 Ben Merembeck 2007-08-22 18:46:16 EDT
That is 7.90 - not 6.90
Comment 2 Bug Zapper 2008-04-04 09:40:03 EDT
Based on the date this bug was created, it appears to have been reported
during the development of Fedora 8. In order to refocus our efforts as
a project we are changing the version of this bug to '8'.

If this bug still exists in rawhide, please change the version back to
(If you're unable to change the bug's version, add a comment to the bug
and someone will change it for you.)

Thanks for your help and we apologize for the interruption.

The process we're following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
Comment 3 Bug Zapper 2008-11-26 02:42:29 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  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 WONTFIX if it remains open with a Fedora 
'version' of '8'.

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 prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
Comment 4 Ben Merembeck 2008-11-27 15:58:14 EST
This bug was fixed by the release of Fedora 8.

B Merembeck
Comment 5 Bug Zapper 2009-01-08 23:51:21 EST
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 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.

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.