LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
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!

Notices


Reply
  Search this Thread
Old 03-07-2008, 01:12 PM   #1
WhoMe99
LQ Newbie
 
Registered: Mar 2008
Posts: 7

Rep: Reputation: 0
Kernel Panic after upgrading to Fedora 7


I recently upgraded my Fedora Core 5 box to FC 6 and then to 7 via yum. The upgrade from 5 to 6 was relatively painless. The upgrade to 7 wasn't so nice.

When I try to boot I receive the following message:
Uncompressing Linux... ok, booting the kernel
Kernel panic - not syncing: no init found. Try passing init= option to kernel.


I use grub to boot and am able to manually switch back to the FC6 kernel. Below is a copy of my grub.conf/menu.lst and fdisk results.

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/hda3
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.23.15-80.fc7)
root (hd0,0)
kernel /vmlinuz-2.6.23.15-80.fc7 ro root=LABEL=/1 rhgb quiet
initrd /initrd-2.6.23.15-80.fc7.img
title Fedora Core (2.6.22.14-72.fc6)
root (hd0,0)
kernel /vmlinuz-2.6.22.14-72.fc6 ro root=LABEL=/1 rhgb quiet
initrd /initrd-2.6.22.14-72.fc6.img


/sbin/fdisk -l

Disk /dev/hda: 251.0 GB, 251000193024 bytes
255 heads, 63 sectors/track, 30515 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 274 2096482+ 82 Linux swap / Solaris
/dev/hda3 275 30515 242910832+ 83 Linux



By the way, I searched this forum and found a few posts similar to mine but I didn't think they were exactly like my situation. If you think there is another post out there that answers my question, please feel free to point me to it.
 
Old 03-07-2008, 02:30 PM   #2
alan_ri
Senior Member
 
Registered: Dec 2007
Location: Croatia
Distribution: Debian GNU/Linux
Posts: 1,733
Blog Entries: 5

Rep: Reputation: 127Reputation: 127
Quote:
Originally Posted by WhoMe99 View Post
When I try to boot I receive the following message:
<b> Uncompressing Linux... ok, booting the kernel
Kernel panic - not syncing: no init found. Try passing init= option to kernel.
Did you tried what you were suggested?
 
Old 03-07-2008, 02:43 PM   #3
WhoMe99
LQ Newbie
 
Registered: Mar 2008
Posts: 7

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by alan_ri View Post
Did you tried what you were suggested?
Yes, I tried. of course there is no guarantee that I did it correctly.
 
Old 03-07-2008, 02:52 PM   #4
alan_ri
Senior Member
 
Registered: Dec 2007
Location: Croatia
Distribution: Debian GNU/Linux
Posts: 1,733
Blog Entries: 5

Rep: Reputation: 127Reputation: 127
Quote:
Originally Posted by WhoMe99 View Post
Yes, I tried. of course there is no guarantee that I did it correctly.
Guarantee that you did it correctly,is only if it works.I think that you don't understand me.This is what you need to think about "Try passing init= option to kernel",or did you tried that?

Last edited by alan_ri; 03-07-2008 at 02:56 PM.
 
Old 03-07-2008, 03:05 PM   #5
WhoMe99
LQ Newbie
 
Registered: Mar 2008
Posts: 7

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by alan_ri View Post
Guarantee that you did it correctly,is only if it works.I think that you don't understand me.This is what you need to think about "Try passing init= option to kernel",or did you tried that?
Are you trying to be cryptic? I can only assume by the fact that you have not given me a specific item to try you are trying to lead to me to the correct answer? That may be a very long road. There is a reason I posted this in the newbie thread (and why it says 'LQ Newbie' under my username) But - to answer your question - Yes, I have thought about it and many other things. Would you like to give me a specific suggestion to try?
 
Old 03-07-2008, 03:17 PM   #6
alan_ri
Senior Member
 
Registered: Dec 2007
Location: Croatia
Distribution: Debian GNU/Linux
Posts: 1,733
Blog Entries: 5

Rep: Reputation: 127Reputation: 127
With that kind of attitude I don't think that you will get much help here.
 
Old 03-07-2008, 03:28 PM   #7
WhoMe99
LQ Newbie
 
Registered: Mar 2008
Posts: 7

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by alan_ri View Post
With that kind of attitude I don't think that you will get much help here.
I have already confessed that I am a newbie and am asking for help because I am feeling pressure to fix a broken box.

All I am asking for is some straight forward ideas of what I can try.

I know, it is a horrible attitude.

Thanks for you help. Perhaps someone else here can get past my attitude and can be of assistance.
 
Old 03-09-2008, 05:17 PM   #8
WhoMe99
LQ Newbie
 
Registered: Mar 2008
Posts: 7

Original Poster
Rep: Reputation: 0
Can anyone else offer any ideas?
 
Old 03-09-2008, 05:51 PM   #9
osor
HCL Maintainer
 
Registered: Jan 2006
Distribution: (H)LFS, Gentoo
Posts: 2,450

Rep: Reputation: 75
Quote:
Originally Posted by WhoMe99 View Post
Can anyone else offer any ideas?
The problem most likely isnít a problem with the name of init (although it could be), but it most likely a problem with the boot loader passing the root partition to the kernel. So the problem is in the highlighted portion of this line:
Code:
kernel /vmlinuz-2.6.23.15-80.fc7 ro root=LABEL=/1 rhgb quiet
Try changing it to
Code:
root=LABEL=/
Or to
Code:
root=/dev/sd??
Where ?? is replaced by the root partition label.
 
Old 03-10-2008, 09:05 AM   #10
WhoMe99
LQ Newbie
 
Registered: Mar 2008
Posts: 7

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by osor View Post
The problem most likely isnít a problem with the name of init (although it could be), but it most likely a problem with the boot loader passing the root partition to the kernel. So the problem is in the highlighted portion of this line:
I believe I tried your suggestions correctly but I didn't have any success.

Here is a list of everything I have tried:
  • kernel /vmlinuz-2.6.23.15-80.fc7 ro root=LABEL=/1
  • kernel /vmlinuz-2.6.23.15-80.fc7 ro root=LABEL=/
  • kernel /vmlinuz-2.6.23.15-80.fc7 ro root=/dev/sda1
  • kernel /vmlinuz-2.6.23.15-80.fc7 ro root=/dev/sda2
  • kernel /vmlinuz-2.6.23.15-80.fc7 ro root=/dev/sda3
  • kernel /vmlinuz-2.6.23.15-80.fc7 ro root=UUID=3c033249-df03-4919-95fc-797e5a82cd00

Any other ideas? Below is the output of blkid - is there any more information I can provide that would help?


/sbin/blkid
/dev/hda3: LABEL="/1" UUID="3c033249-df03-4919-95fc-797e5a82cd00" SEC_TYPE="ext2" TYPE="ext3"
/dev/hda1: LABEL="/boot1" UUID="7b273886-a0f2-44ec-b60f-b89eb6829841" SEC_TYPE="ext2" TYPE="ext3"
/dev/hda2: TYPE="swap" LABEL="SWAP-hda2"
 
Old 03-10-2008, 09:59 AM   #11
osor
HCL Maintainer
 
Registered: Jan 2006
Distribution: (H)LFS, Gentoo
Posts: 2,450

Rep: Reputation: 75
Quote:
Originally Posted by WhoMe99 View Post
Here is a list of everything I have tried:
  • kernel /vmlinuz-2.6.23.15-80.fc7 ro root=LABEL=/1
  • kernel /vmlinuz-2.6.23.15-80.fc7 ro root=LABEL=/
  • kernel /vmlinuz-2.6.23.15-80.fc7 ro root=/dev/sda1
  • kernel /vmlinuz-2.6.23.15-80.fc7 ro root=/dev/sda2
  • kernel /vmlinuz-2.6.23.15-80.fc7 ro root=/dev/sda3
  • kernel /vmlinuz-2.6.23.15-80.fc7 ro root=UUID=3c033249-df03-4919-95fc-797e5a82cd00
How about
Code:
kernel /vmlinuz-2.6.23.15-80.fc7 ro root=/dev/hda3
Quote:
Originally Posted by WhoMe99 View Post
Any other ideas?
Not really. At least not without seeing more of the kernel output (which is hard to capture). Perhaps you have a bad initrd (do you use any special LVM or RAID setup?). Here is a bug describing a deficiency in the FC7 initrd with respect to RAID or LVM. It seems that the fix is to boot into FC6, and issue the command:
Code:
/sbin/mkinitrd -f --force-lvm-probe --force-raid-probe /boot/initrd-2.6.23.15-80.fc7.img 2.6.23.15-80.fc7
There is also a fix that involves using the FC7 Rescue CD (which you will presumably have to download).
 
Old 03-10-2008, 11:56 AM   #12
WhoMe99
LQ Newbie
 
Registered: Mar 2008
Posts: 7

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by osor View Post
How about
Code:
kernel /vmlinuz-2.6.23.15-80.fc7 ro root=/dev/hda3
I think I had actually tried that but neglected to include that in my list of things I tried.

Quote:
Originally Posted by osor View Post
Code:
/sbin/mkinitrd -f --force-lvm-probe --force-raid-probe /boot/initrd-2.6.23.15-80.fc7.img 2.6.23.15-80.fc7
This worked! I actually had to run this twice - the first time I ran this, selinux complained a bit so I disabled enforcement, ran it again, rebooted and *poof* it worked. (Now, I'm left wondering if I was an idiot and neglected to do that when I upgraded.)

Thank you so very much for your assistance!
 
Old 03-10-2008, 06:36 PM   #13
osor
HCL Maintainer
 
Registered: Jan 2006
Distribution: (H)LFS, Gentoo
Posts: 2,450

Rep: Reputation: 75
Quote:
Originally Posted by WhoMe99 View Post
Now, I'm left wondering if I was an idiot and neglected to do that when I upgraded.
I donít think the fault lies with you but with the Fedora upgrade script (and thatís why itís in their bugzilla).
 
  


Reply


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
Kernel panic upgrading from 2.4.31 to 2.6.13 Sushy Slackware 8 12-03-2006 05:50 PM
kernel panic while upgrading satheesh kumar Linux - Kernel 2 12-01-2006 10:43 PM
Upgrading kernel on Debian from 2.4 to 2.6.8, Kernel Panic omlette Linux - General 3 03-07-2005 07:00 AM
kernel panic upgrading to 2.6.1 sadeer Red Hat 2 03-24-2004 05:12 AM
Help needed!! Kernel panic problem after upgrading RAM nparab Linux - Hardware 3 04-12-2003 01:03 PM


All times are GMT -5. The time now is 08: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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration