Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 154968 - FC4 grub hangs on stage2
Summary: FC4 grub hangs on stage2
Alias: None
Product: Fedora
Classification: Fedora
Component: grub
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Mike McLean
Depends On:
Blocks: FC4Blocker
TreeView+ depends on / blocked
Reported: 2005-04-15 05:50 UTC by Warren Togami
Modified: 2007-11-30 22:11 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-05-18 19:44:46 UTC

Attachments (Terms of Use)

Description Warren Togami 2005-04-15 05:50:44 UTC
While the vast majority of "grub hands at stage2" problems from FC3 were fixed
in FC4, it seems that a few machines still experience this problem.  This bug is
split from Bug 139140 which is a confusing mess of different hardware and
FC3/FC4 mixed reports.

Please describe your hardware here ONLY if FC4's grub fails exactly in one of
these two ways:
1) hangs on stage2
2) spontaneous reboot when it reaches stage2
DO NOT REPORT HERE IF YOU ARE USING FC3.  Instead follow the procedure that I
wrote here.  Chances are it will fix your FC3.

Comment 1 Gene Czarcinski 2005-04-15 14:31:48 UTC
Please also see
which appears (to me) as an anaconda bug (on FC4T2).  When this occurs, grub is
not installed in the partition (i386).

This also occurred in a similar but different situation doing an x86_64 (fresh)
install on the same system except that it appears more like the problem
described here in that the install was all screwed up.  To recover, I had to run
rescueCD to set the MBR in my "system boot controller partition
(grub/root/setup).  I then rebooted the x86_64 rescueCD and had to run
grub-install becuase nothing had been installed.

The system is an opteron on an ASUS SK8V motherboard with two disks PATA on hda
and a SATA which comes up as sda.  Booting is off the hda drive with hda1 being
a small system (boot controller) pointed to by MBR, hda9 being the i386
partition and hda10 being the x86_64 partition.

fdisk -l /dev/hda:

Disk /dev/hda: 122.9 GB, 122942324736 bytes
255 heads, 63 sectors/track, 14946 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1         123      987966   83  Linux
/dev/hda2             124         489     2939895   82  Linux swap / Solaris
/dev/hda4             490       14946   116125852+   5  Extended
/dev/hda5             490        2314    14659281   83  Linux
/dev/hda6            2315        4139    14659281   83  Linux
/dev/hda7            4140        5964    14659281   83  Linux
/dev/hda8            5965        7789    14659281   83  Linux
/dev/hda9            7790        9614    14659281   83  Linux
/dev/hda10           9615       11439    14659281   83  Linux
/dev/hda11          11440       13264    14659281   83  Linux
/dev/hda12          13265       14946    13510633+  83  Linux

I have another partition (hda11) which I can do another test install if there is
something you want me to test.  Once the install is complete and I fix
everything up, it works fine.

Comment 2 Jeremy Katz 2005-05-18 19:44:46 UTC
Gene's problem should be fixed with Peter's change from last week... not seeing
other reports here, I'm going to close this due to lack of information.

Comment 3 Robert Nichols 2006-02-03 01:34:04 UTC
I ran into this problem with FC4 installed on a Compaq Evo D510 CMT I just
acquired.  GRUB would display:

    GRUB Loading stage 1.5

    GRUB loading, please wait...

and then hang.  GRUB version is 0.95-13.i386.  I discovered that if I
substitute the /boot/grub/*stage* files from FC3 (grub-0.95-3.i386) and
rerun "setup (hd0)" from the GRUB shell, then booting works properly.

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