LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices

Reply
 
Search this Thread
Old 02-20-2007, 01:02 AM   #1
jot
LQ Newbie
 
Registered: Aug 2004
Location: Singapore
Distribution: Ubuntu and Fedora
Posts: 25

Rep: Reputation: 0
Question boot error for kernel-2.6.19-1.2288.fc5


Hi all

Is there any known problem with the latest kernel? Few days ago I upgraded my kernel (like a 100 times before) from kernel-2.6.18-1.2257.fc5 to kernel-2.6.19-1.2288.fc5 via yum. Attempting to boot the latter ends up in a kernel panic. The former still does work when booted via my grub menu (my rescue for the moment!).

Ok, for the 2.6.19-1.2288 I get these messages/errors:

Code:
Decompressing linux...done.
Booting the kernel.

Red Hat nash version 5.0.32 starting
Unable to access resume device (/dev/VolGroup00/LogVol01)
mount: could not find filesystem '/dev/root'
setuproot: moving /dev failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
switchroot: mount failed: No such file or directory

kernel panic - not syncing: Attempted to kill init!
As I had mentioned above, the older kernel still works. So the problem must have to do with the latest one (2.6.19). I've also checked if everything is in place in the /boot directory:
Code:
-rw-r--r-- 1 root root   62678 Dec 16 05:28 config-2.6.18-1.2257.fc5
-rw-r--r-- 1 root root   66716 Feb 11 04:21 config-2.6.19-1.2288.fc5
drwxr-xr-x 2 root root    1024 Feb 20 12:53 grub
-rw-r--r-- 1 root root 1946023 Jan  6 03:09 initrd-2.6.18-1.2257.fc5.img
-rw-r--r-- 1 root root 1192375 Feb 18 18:23 initrd-2.6.19-1.2288.fc5.img
drwx------ 2 root root   12288 Sep  6 18:30 lost+found
-rw-r--r-- 1 root root   94600 Feb  8  2006 memtest86+-1.65
-rw-r--r-- 1 root root 1113960 Dec 16 05:28 System.map-2.6.18-1.2257.fc5
-rw-r--r-- 1 root root 1159572 Feb 11 04:21 System.map-2.6.19-1.2288.fc5
-rw-r--r-- 1 root root 1955345 Dec 16 05:28 vmlinuz-2.6.18-1.2257.fc5
-rw-r--r-- 1 root root 2024675 Feb 11 04:21 vmlinuz-2.6.19-1.2288.fc5
Looks fine (to me at least). No surprises in the grub.conf either:

Code:
title Fedora Core (2.6.19-1.2288.fc5)
        root (hd0,0)
        kernel /vmlinuz-2.6.19-1.2288.fc5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        initrd /initrd-2.6.19-1.2288.fc5.img
title Fedora Core (2.6.18-1.2257.fc5)
        root (hd0,0)
        kernel /vmlinuz-2.6.18-1.2257.fc5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        initrd /initrd-2.6.18-1.2257.fc5.img
My configuration:
AMD Athlon 64 X2 Dual Core 4600 on a A8N32 SLI Deluxe board
Fedora Core 5 (x86_64)


Any hints, anyone?
 
Old 02-20-2007, 04:22 AM   #2
reddazz
Guru
 
Registered: Nov 2003
Location: N. E. England
Distribution: Fedora, CentOS, Debian
Posts: 16,298

Rep: Reputation: 73
Moved: This thread is more suitable in the Fedora forum and has been moved accordingly to help your thread/question get the exposure it deserves.
 
Old 02-28-2007, 01:29 AM   #3
DCOH
Member
 
Registered: Oct 2006
Location: Ohio
Distribution: Fedora 13/14/15KDE/PclinuxOS
Posts: 95

Rep: Reputation: 16
I had the same problem I just used yumex to remove the new kernel than reinstalled it, worked fine when I rebooted
 
Old 02-28-2007, 11:55 AM   #4
jot
LQ Newbie
 
Registered: Aug 2004
Location: Singapore
Distribution: Ubuntu and Fedora
Posts: 25

Original Poster
Rep: Reputation: 0
Thanks for your reply, DCOH!

As there was no reply to my post for quite some time, I assumed it had to be an error specific to my box. So I had actually done the same as you earlier: removing kernel 2.6.19 and reinstalling it again (via yum). And it worked for me too!!!

Though it bothered me that there was no obvious reason for the previous error. So I checked /boot again, and - bingo! One file differs in size (increase from 1192375 to 1983731 bytes). I wonder how that could slip through:

Code:
-rw-r--r-- 1 root root   62678 Dec 16 05:28 config-2.6.18-1.2257.fc5
-rw-r--r-- 1 root root   66716 Feb 11 04:21 config-2.6.19-1.2288.fc5
drwxr-xr-x 2 root root    1024 Mar  1 00:21 grub
-rw-r--r-- 1 root root 1946023 Jan  6 03:09 initrd-2.6.18-1.2257.fc5.img
-rw-r--r-- 1 root root 1983731 Mar  1 00:21 initrd-2.6.19-1.2288.fc5.img
drwx------ 2 root root   12288 Sep  6 18:30 lost+found
-rw-r--r-- 1 root root   94600 Feb  8  2006 memtest86+-1.65
-rw-r--r-- 1 root root 1113960 Dec 16 05:28 System.map-2.6.18-1.2257.fc5
-rw-r--r-- 1 root root 1159572 Feb 11 04:21 System.map-2.6.19-1.2288.fc5
-rw-r--r-- 1 root root 1955345 Dec 16 05:28 vmlinuz-2.6.18-1.2257.fc5
-rw-r--r-- 1 root root 2024675 Feb 11 04:21 vmlinuz-2.6.19-1.2288.fc5
Isn't yum running some integrity check after downloading files?

*wonder*
 
Old 02-28-2007, 06:53 PM   #5
DCOH
Member
 
Registered: Oct 2006
Location: Ohio
Distribution: Fedora 13/14/15KDE/PclinuxOS
Posts: 95

Rep: Reputation: 16
I'm not sure about an integrity check by yum but it does verify the download. When I reinstalled the kernel with yumex the kernel showed update so there my have been a problem with the kernel.
 
Old 03-17-2007, 02:13 PM   #6
anajand
LQ Newbie
 
Registered: Mar 2007
Posts: 1

Rep: Reputation: 0
boot error for kernel-2.6.20.xxxx

Hi Fellows,

I have Fedora and had the same problem when updating from 2.6.18.xxxx to 2.6.20.xxxx: I could not boot with the new kernel and got the same messages as below:

"Decompressing linux...done.
Booting the kernel.

Red Hat nash version 5.0.32 starting
Unable to access resume device (/dev/VolGroup00/LogVol01)
mount: could not find filesystem '/dev/root'
setuproot: moving /dev failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
switchroot: mount failed: No such file or directory

kernel panic - not syncing: Attempted to kill init!"


But I could boot with the older one. So with "Add/Remove Software" I removed the 2.6.20 kernel and then added it back to my system and this time everything was fine and I could boot with the new kernel! Now I am worried about the other updated files/modules, could other files have been corrupted during the update process? How to know that? Of course not using them or their associated programs will not show anything but what if this happens weeks from now, how to associate potential issues to the upgrade problem?

Question to Linux experts: is a kernel built (compiled/linked/etc.) on the local computer during the update process, or is it just a file that gets downloaded? The former would mean that the build was not correct; the latter would mean that the file was not downloaded properly. In any case are they other files that could have been build erroneously or downloaded without keeping their integrity?

Thanks
 
  


Reply

Tags
kernel, kernel panic, yum update


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
ndiswrapper refuses to compile against kernel 2.6.19-1.2288 lavie Linux - Wireless Networking 7 02-25-2007 10:52 AM
Kernel Panic Error Message on boot for FC5 gotrojan Fedora 6 02-07-2007 01:40 PM
kernel-2.6.18-1.2200.fc5 = NO BOOT RottenMutt Fedora 7 11-05-2006 09:18 AM
cannot boot with new kernel.Raid.FC5 Guignol Linux - Software 0 07-25-2006 08:28 AM
wireless-tools (iw*) error on FC5 using kernel 2.6.17.6 burninGpi Linux - Wireless Networking 2 07-21-2006 02:57 PM


All times are GMT -5. The time now is 11:45 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration