Bug 751718 - F16 RC5 does not boot after installation
Summary: F16 RC5 does not boot after installation
Status: CLOSED DUPLICATE of bug 735733
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 16
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2011-11-07 10:13 UTC by Bernard Ladenthin
Modified: 2011-11-15 18:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-11-07 11:20:58 UTC
Type: ---

Attachments (Terms of Use)

Description Bernard Ladenthin 2011-11-07 10:13:47 UTC
Description of problem:


i have a MDEION MD95300 (http://www.medion.de/flash/md95300/html/service.html).

installation of f16 RC5 i686 works fine (with and without LUKS).

After the installation and restart, the BIOS tells:
Hard disk boot sector invalid
Press 'H' to retry Hard Disk, any other key for floppy

I have done a low-level formatting before.

What can i do, or post you for help, to fix this problem?

I think it is a problem with the GPT.

Thank you an greetings from germany.

Steps to Reproduce:
1. Install F16 RC5
2. Restart after installation

Expected results:
System should boot.

Additional info:
You can download some information (from f16 live boot):
dmesg: http://pastebin.com/nCC9s6ye
lspci: http://pastebin.com/nZpMscet
lsusb: http://pastebin.com/MvKTiu1j
fdisk: http://pastebin.com/qL5MJHSj
lshw:  http://pastebin.com/CUZasWzU

screenshot of gparted: http://picpaste.com/pics/Screenshot-Pt74PDrq.1320660568.png

Comment 1 Bernard Ladenthin 2011-11-07 11:20:58 UTC
nogpt boot option and MSDOS fix the problem. Need further information for a white/black list?

*** This bug has been marked as a duplicate of bug 735733 ***

Comment 2 Adam Williamson 2011-11-07 18:17:56 UTC
did you use the latest available BIOS?

Fedora Bugzappers volunteer triage team

Comment 3 Bernard Ladenthin 2011-11-11 20:13:44 UTC
"did you use the latest available BIOS?" yes

Comment 4 Adam Williamson 2011-11-15 18:11:45 UTC
thanks. i think we're not really trying to construct a comprehensive system-by-system blacklist atm, we generally are of the opinion that blacklists have too much of a cost in terms of maintenance and sometimes-being-wrong. we blacklisted all Lenovo systems just because so many of them seem to be broken and a _lot_ of people run Lenovos.

Fedora Bugzappers volunteer triage team

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