Bug 146276 - Grub Disk Boot Failure on cold boot
Summary: Grub Disk Boot Failure on cold boot
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: grub
Version: 3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-01-26 17:38 UTC by Jerry Novetsky
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-03-30 22:27:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jerry Novetsky 2005-01-26 17:38:32 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
I am using Fedora Core 3 (FC3) with the latest updates/upgrades.
Upon a cold boot, I receive the following message:
Disk Boot Failure, Insert System Disk and Press Enter.
A warm boot is successful with grub stage 2 (grub 2)
grub-0.95-3

I have replaced the motherboard, an Asus A7N8X-E Deluxe with a new
one. I have tried the latest bios 1013 for the motherboard as well as
an older one 1012.  I have tried a new booting hard drive.  I have
essentially tried replacing all the hardware, everything but I still
cannot do a cold boot.  I believe that grub FC3 is at fault.


Please assist.
Thanks,
Jerry

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


How reproducible:
Always

Steps to Reproduce:
1.Install FC3 on Asus A7N8X-E Deluxe with latest bios.
2.Use up2date to update/upgrade system
3.Logg off, then do cold boot.
    

Actual Results:  Disk Boot Failure, Insert System Disk and Press Enter.

Expected Results:  Should have a successful Grub stage 2 boot

Additional info:

Comment 1 Peter Jones 2005-03-30 22:27:16 UTC
This sounds like a drive that's not spinning up quick enough, or something along
those lines.  In any case, that error message comes from the BIOS -- it's before
grub is loaded at all.


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