Bug 392594 - boot error after updating kernel
Summary: boot error after updating kernel
Status: RESOLVED DUPLICATE of bug 389177
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Beta 3
Hardware: i686 openSUSE 11.0
: P5 - None : Normal with 1 vote (vote)
Target Milestone: ---
Assignee: Andreas Gruenbacher
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-20 13:45 UTC by Nathan Ogden
Modified: 2008-05-27 04:25 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nathan Ogden 2008-05-20 13:45:06 UTC
I just installed openSUSE 11.0 Beta 3 from KDE4 Live CD. Installation went well. I enabled the 3 existing repositories (oss, non-oss, update). I then installed Thunderbird and Inkscape. Then I updated all existing packages (over 700 already had updates). Autocheck was successful so I updated the packages. When I was finished, I was notified that the kernel had been updated. Since I needed to reboot to activate the new kernel, I rebooted.
I received an error message after the boot prompt.

Error Message:
Error 15: File not found
Press any key to continue...

Above this message is the following information:
root (hd0,4)
 Filesystem type is ext2fs, partition type 0x83
kernel /boot/vmlinuz root=/dev/disk/by-id/scsi-SATA_FUJITSU_MHY2160_K428T7B27067-part5 resume=/dev/sda6 splash=silent showopts vga=0x314
 [Linux-bzImage, setup=0x3000, size=0x2048a0]
initrd /boot/initrd
Comment 1 Jiri Srain 2008-05-21 06:47:03 UTC
This sounds like initrd was not created, could you check the presence of /boot/initrd, and the target of it (it is usually a sympink)?
Comment 2 Nathan Ogden 2008-05-21 11:11:42 UTC
Since I am unable to boot, how do I find out? Should I use the live CD somehow?
Comment 3 Jiri Srain 2008-05-23 07:16:04 UTC
Yes, live CD is one way, you can mount the installed system and check it.
Comment 4 Nathan Ogden 2008-05-23 14:41:32 UTC
Okay, I have mounted the installed system with the live CD.

Comparison of /boot files before and after updating kernel

Before kernel update:

initrd
Type: Gzip archive
Points to: initrd-2.6.25.3-2-default

initrd-2.6.25.3-2-default
Type: Gzip archive

After kernel update:

initrd
Type: unknown
Points to: initrd-2.6.25.4-2-default

initrd-2.6.25.4-2-default DOES NOT EXIST

I guess that would be the problem then. Neither initrd-2.6.25.3-2-default nor initrd-2.6.25.4-2-default exist now.
Comment 5 Jason Power 2008-05-25 22:26:47 UTC
I have the exact same problem.
Comment 6 Jiri Srain 2008-05-26 06:06:38 UTC
Andreas, it looks like mkinitrd is not called, could you, please, check it?
Comment 7 Andreas Gruenbacher 2008-05-27 04:25:12 UTC

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