Visit Jeremy's Blog.
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!


  Search this Thread
Old 07-09-2009, 01:17 PM   #1
Registered: May 2009
Posts: 34

Rep: Reputation: 0
kernel panic need help

Weird problem.
I got a new server poweredge 840. The old one shit the bed. I cloned the drive over from an hda(IDE) to a sata 250 gig. The drive boots in a poweredge 830 fine. I have a feeling the kernel panic is due to the changes in hardware between and 830 and 840. Perhaps a different sata controller or something so its not finding the boot. I have checked grub.conf menu.lst /etc/fstab and /etc/mtab. Is there anything else I need to switch from hda to sda that might not be causing it boot. Or is there a way to force kudzu to run before grub boots in order to install the new hardware? The kernel panic hits before kudzu normally runs. Or is there a way to take the hardware config from one machine over to another. I have this set up and running on a poweredge 840 already so if I can take its hardware profile to the new poweredge 840 it may work as well. Any help would be appreciated.

Red Hat Enterprise Linux ES release 3 (Taroon)
Kernel 2.4.21-15.0.3.EL on an i686

VFS:Mounted root (ext2 filesystem)
VFS: Cannot open root device "LABEL=/" 00:08
Please append a correct "root "boot option
Kernel panic:VFS:Unable to mount root fs on 00:08

Last edited by z01krh; 07-09-2009 at 01:21 PM.
Old 07-09-2009, 03:18 PM   #2
Registered: Jul 2009
Location: Illinois, US
Distribution: Fedora 11
Posts: 374

Rep: Reputation: 55
It's pretty much telling you what your error is. Is the label of the new filesystem correctly set to /? Check by running gparted or `tune2fs -l /dev/<partition>` (ext{2,3,4} only).
Old 07-09-2009, 03:47 PM   #3
Registered: May 2009
Posts: 34

Original Poster
Rep: Reputation: 0
I booted up using gparted live cd and checked the labels and they are set correct. The output of tune2fs -l also gives me the correct resuts.

/dev/sda2 20G 14G 5.3G 72% /
/dev/sda1 99M 20M 75M 21% /boot
none 504M 0 504M 0% /dev/shm
/dev/sda5 53G 13G 38G 25% /my_prj

Last edited by z01krh; 07-09-2009 at 03:50 PM.
Old 07-09-2009, 03:48 PM   #4
LQ Newbie
Registered: Nov 2006
Location: Ventura California USA
Distribution: openSUSE
Posts: 23

Rep: Reputation: 3
I believe you are correct in that the new hardware has a different hard drive controller than that in the old hardware. (The Dell site may confirm this.) The controller you are interested in is the one that controls the drive that has the root partition on it. The problem you are experiencing is almost undoubtedly that the driver for the new controller is not in the initrd file (initial ramdisk -- normally found in /boot/initrd...). The initrd gets mounted first thing after grub finishes. Its job is to find and mount the root partition, then hand off control to it. It does no test to see if this was successful -- it does its job blindly. If it has no driver for the controller, then it will be unable to do its job, leaving you with a kernel panic.

Fixing this can be done, but it is not trivial, and I cannot give you step-by-step instructions as I've only done this 2-3 times. It involves booting using another media, like your installation disc, and entering a rescue mode. Then you mount your hardware's partitions under a single folder (like /mnt) to recreate under it the filesystem that your hardware normally has (e.g. /mnt/bin, /mnt/usr, /mnt/usr/bin, etc.) Note that this may require manually loading a driver for your HD controller, but this is somewhat unlikely. If manual driver loading is required, you'll need to figure out which driver to use, such as by searching the web. Also, you may need to create device files under /mnt/etc. There is probably a simple way to do this, but I have yet to discover one.

Once your real filesystem is recreated, then you'd need to "pivot" your root. That is, what you've created under /mnt will be pivoted to become / (and what was / can be pivoted somewhere, like the post-pivot /mnt, but I don't think this is necessary). If you get to this point, you are 90% done. You could probably run kudzu at this point (you may want to make backup copies of /boot/initrd* and /boot/vmlinu[zx]*). You may also be able to get copies of your distribution's latest kernel RPMs and just use them to "upgrade" your kernel (you may need to force the installation -- rpm -Uvh --force ...). This ought to recreate your initrd for the new hardware. If this works, you're probably all set to shutdown and reboot.

Before trying this, search the web for kernel panic and rebuilding initrd. It'd be nice to have another PC available so you can refer to the web as you are going along. Good luck. If you try this, you will learn a lot of good stuff.

Last edited by bwayson; 07-09-2009 at 03:50 PM. Reason: clarification


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
upgrading Fedora Core 3 kernel 2.6.9-1.667 to manually+kernel panic error LinuxLovinNoob Linux - Newbie 7 12-17-2008 08:45 PM
Kernel 2.4 in Zipslack (Waring: unable to open an initial console | Kernel Panic...) kurtamos Linux - General 2 05-10-2006 12:58 PM
Kernel panic puts me in a panic theeeg Linux - Software 2 07-31-2004 04:46 PM
kernel panic (narius panic) narius Linux - Newbie 3 06-20-2002 03:56 PM
Kernel panic making me panic! Linux_N0oby Linux - Software 19 05-29-2002 12:31 AM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 08:12 AM.

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