Bug 994333 - Problems to boot kernel-3.10.5-200.fc19.x86_64: premature end of file /boot/vmlinuz-3.10.5-200.fc19.x86_64
Summary: Problems to boot kernel-3.10.5-200.fc19.x86_64: premature end of file /boot/v...
Keywords:
Status: CLOSED DUPLICATE of bug 991808
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-07 05:18 UTC by Joachim Backes
Modified: 2013-08-07 12:56 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-07 12:56:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Joachim Backes 2013-08-07 05:18:39 UTC
Description of problem:
After installing kernel-3.10.5-200.fc19.x86_64 from koji and trying to boot, grub2 has problems:

error: premature end of file /boot/vmlinuz-3.10.5-200.fc19.x86_64
error: you need to load the kernel first

No problems when booting my current kernel-3.10.4-300.fc19.x86_64


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


How reproducible:
3.10.5-200.fc19.x86_64

Steps to Reproduce:
1.Install 3.10.5-200.fc19.x86_64
2.reboot
3.

Actual results:

error: premature end of file /boot/vmlinuz-3.10.5-200.fc19.x86_64
error: you need to load the kernel first


Expected results:
the kernel boots

Additional info:

Seeing a weird behaviout during install: If installing the kernel (with yum), cc1 still runs after the shell cmd prompt reappears (I think this has to do with rebuilding kmod-VirtualBox). But why the yum prompt appears despite the module rebuild has not finished?

Comment 1 Joachim Backes 2013-08-07 05:45:04 UTC
Seems to be the same problem as reported in #991808.

Comment 2 rvcsaba 2013-08-07 07:28:23 UTC
Kernel image length is 0.

Comment 3 Josh Boyer 2013-08-07 12:56:42 UTC

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


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