Bug 167844 - GRUB hangs when booting
Summary: GRUB hangs when booting
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: grub
Version: 4
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Mike McLean
URL: grub displays prompt will not boot
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-09-08 20:21 UTC by Dave Browne
Modified: 2008-02-28 23:57 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-28 23:57:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Dave Browne 2005-09-08 20:21:10 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)

Description of problem:
When I boot the word GRUB appears with prompt will not boot further.

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


How reproducible:
Always

Steps to Reproduce:
1.Reboot
2.
3.
  

Actual Results:  GRUB _ with prompt flashing

Expected Results:  Should complete booting

Additional info:

Comment 1 Erik P. Olsen 2005-10-07 12:01:14 UTC
Same happened to my FC3 after updating to kernel 2.6.12-1.1378.
Reactivating previous grub.conf makes no difference.
/etc/mtab looks strange:

/dev/hdb5 / ext3 rw 0 0
none /proc proc rw 0 0

Regards,
Erik P. Olsen

Comment 2 Erik P. Olsen 2005-10-08 17:45:41 UTC
Solved my problem. The GRUB loader was destroyed and "grub-install" inserted a
new GRUB loader. Apparently the up2date process clobbered the loader when
updating the kernel.

Regards,
Erik P. Olsen

Comment 3 Christian Iseli 2007-01-22 10:49:09 UTC
This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?

Thanks.

Comment 4 petrosyan 2008-02-28 23:57:39 UTC
Fedora Core 4 is no longer maintained.

Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.


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