Fedora Linux Support Community & Resources Center

Go Back   FedoraForum.org > Fedora 17/18 > Using Fedora
FedoraForum Search

Forgot Password? Join Us!

Using Fedora General support for current versions. Ask questions about Fedora and it's software that do not belong in any other forum.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 26th May 2007, 08:59 PM
kirktrue Offline
Registered User
 
Join Date: May 2007
Posts: 1
Kernel panic on vanilla 2.6.21.3 kernel

I get a kernel panic on boot when I upgraded from a vanilla 2.6.20.4 to a vanilla 2.6.21.3 kernel on a Fedora Core 6 box. Here's the relevant part of the log:
Creating root device.
Mounting root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
[ 580.767825] Kernel panic - not syncing: Attempted to kill init!
What I believe is happening is that the builtin nash command mkrootdev is silently failing to produce a /dev/root. I assume this because I added a call to the init script that lists the entries in the /dev file system at boot time:
find /dev
This is output right after the mkrootdev call but before the setuproot call. I see about two dozen or so /dev entries from the find command on the console. However, on 2.6.21.3, /dev/root is not listed, but it is listed for 2.6.20.4. As such, 2.6.20.4 boots fine whereas 2.6.21.3 then panics.

Here is what my 2.6.20.4 boot log looks like:
Creating root device.
Mounting root filesystem.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Setting up other filesystems.
Setting up new root fs
no fstab.sys, mounting internal defaults
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
Regarding my root= option, it's /dev/sda3 as opposed to LABEL=/. My root filesystem is ext3 which is a module as opposed to built-in. However, my 2.6.20.4 kernel was the same way and caused no issues.

So, it would seem that mkinitrd is not creating a /dev entry for the root device. Based on some Google-ing, I tried to manually create the entry in my init script:
mknod /dev/sda3 b 8 3
mknod /dev/root b 8 3
But then it said:
Creating root device.
Mounting root filesystem.
mount: error mounting /dev/root on /sysroot as ext3: No such device or address
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
[ 292.981508] Kernel panic - not syncing: Attempted to kill init!
I have heard some references to udev and have seen some calls to /sbin/udevstartup or something in some user's init scripts, but my mkinitrd does not generate this call.

Any ideas? I've been working on this for nearly a week now and Google-ing for it ad naseum. I've heard that Fedora is not too friendly to vanilla kernels, but I don't really want to switch my whole distro because of this issue.

Thanks!
Reply With Quote
  #2  
Old 26th May 2007, 09:25 PM
sideways's Avatar
sideways Offline
Retired User
 
Join Date: Oct 2004
Location: London, UK
Posts: 4,999
Try labelling sda3 and referring to it by its label in grub.conf and fstab

eg see 'important warnings' in this blog
http://ostoolbox.blogspot.com/2007/0...-released.html
Reply With Quote
  #3  
Old 27th May 2007, 12:09 AM
lmo Offline
Registered User
 
Join Date: Mar 2007
Posts: 1,047
When you "upgraded from a vanilla 2.6.20.4 to a vanilla 2.6.21.3" could you have left out a step? If it didn't do the mkinitrd for the new kernel, I think it could cause that error.
Reply With Quote
Reply

Tags
kernel, panic, vanilla

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

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 On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
fedora kernel spec file and vanilla kernel LocutusOfBorg Using Fedora 4 27th August 2007 07:23 AM
New Kernel/Vanilla Kernel good bad and ugly quik69 Fedora Focus 5 7th February 2007 05:09 AM


Current GMT-time: 11:54 (Monday, 20-05-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat