LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Kernel Panic after upgrading to Fedora 7 (https://www.linuxquestions.org/questions/linux-newbie-8/kernel-panic-after-upgrading-to-fedora-7-a-626461/)

WhoMe99 03-07-2008 01:12 PM

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.

alan_ri 03-07-2008 02:30 PM

Quote:

Originally Posted by WhoMe99 (Post 3081373)
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?

WhoMe99 03-07-2008 02:43 PM

Quote:

Originally Posted by alan_ri (Post 3081442)
Did you tried what you were suggested?

Yes, I tried. of course there is no guarantee that I did it correctly.

alan_ri 03-07-2008 02:52 PM

Quote:

Originally Posted by WhoMe99 (Post 3081455)
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?

WhoMe99 03-07-2008 03:05 PM

Quote:

Originally Posted by alan_ri (Post 3081469)
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?

alan_ri 03-07-2008 03:17 PM

With that kind of attitude I don't think that you will get much help here.

WhoMe99 03-07-2008 03:28 PM

Quote:

Originally Posted by alan_ri (Post 3081495)
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.

WhoMe99 03-09-2008 05:17 PM

Can anyone else offer any ideas?

osor 03-09-2008 05:51 PM

Quote:

Originally Posted by WhoMe99 (Post 3083374)
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.

WhoMe99 03-10-2008 09:05 AM

Quote:

Originally Posted by osor (Post 3083399)
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"

osor 03-10-2008 09:59 AM

Quote:

Originally Posted by WhoMe99 (Post 3083893)
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 (Post 3083893)
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).

WhoMe99 03-10-2008 11:56 AM

Quote:

Originally Posted by osor (Post 3083937)
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 (Post 3083937)
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!

osor 03-10-2008 06:36 PM

Quote:

Originally Posted by WhoMe99 (Post 3084056)
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).


All times are GMT -5. The time now is 03:20 AM.