PDA

View Full Version : Upgrade, Kernel panic: No init found..


zg0000
2004-09-11, 01:04 AM CDT
After upgrading the stock core 2 kernel I get the following error (when trying to load the new kernel):

Decompressing Linux...done
Booting the kernel.
audit(1094835472.234:0): Initialized
Red Hat nash version 3.5.22 starting
mkrootdev: label /not found
mount: error 2 mounting ext3
pivotroot: pivot_root(/sysroot, /systroot/initrd) failed: 2
umount /initrd/proc failed: 2
Kernel panic: No init found. Try passing init-option to kernel

My grub configuration is (auto configured during the rpm install, 2.6.5-1 is the working kernel):

timeout=10
splashimage=(hd0,4)/boot/grub/splash.xpm.gz
title Fedora Core (2.6.8-1.521)
root (hd0,4)
kernel /boot/vmlinuz-2.6.8-1.521 ro root=LABEL=/ rhgb quiet
initrd /boot/initrd-2.6.8-1.521.img
title Fedora Core (2.6.5-1.358)
root (hd0,4)
kernel /boot/vmlinuz-2.6.5-1.358 ro root=LABEL=/ rhgb quiet
initrd /boot/initrd-2.6.5-1.358.img

Anyone else have trouble with the updated kernel? Any ideas?

imdeemvp
2004-09-11, 01:06 AM CDT
is not a very good kernel.....i dont like it and i dont use! i am still using 2.6.7 version...

ghaefb
2004-09-11, 01:49 AM CDT
is not a very good kernel.....i dont like it and i dont use! i am still using 2.6.7 version...
That's not a good advice/solution..

Try this:
title Fedora Core (2.6.8-1.521)
root (hd0,4)
kernel /boot/vmlinuz-2.6.8-1.521 ro root=305 rhgb quiet
initrd /boot/initrd-2.6.8-1.521.img

imdeemvp
2004-09-11, 02:38 AM CDT
sorry about answer i am just being honest:

mount /dev/hda1 /mnt/windowsxp
mount: fs type ntfs not supported by kernel

and i know for a fact i downloaled correct package name because this is the last kernel for fc2 but i dont have same issue if i use previous kernel.......and also hardware does not seen to work ok...according to some readings i done. :eek:

zg0000
2004-09-11, 11:18 PM CDT
That's not a good advice/solution..

Try this:
title Fedora Core (2.6.8-1.521)
root (hd0,4)
kernel /boot/vmlinuz-2.6.8-1.521 ro root=305 rhgb quiet
initrd /boot/initrd-2.6.8-1.521.img

I tried that, it seems to fix the label error, but the /sysroot, /systroot/initrd error persists.

I appreciate the suggestion. I might try the other suggesters idea and install the 2.6.7.

wzzrd
2004-09-17, 01:08 PM CDT
What seems to happen is that your kernel can't find it's root fs. This is the stuff that happens when you configure grub to use a label name instead of a device name. I like fedora, but I never understood why they do this. Now you first have to find out whether the problem is with the filesystem label or with the reading of the filesystem all together...

I hope I don't offend you when I ask you: do you know where your root fs is located? Because THAT is what you need to fill in after root= in grub.conf. Your /boot directory (I don't think it's a partition in your case) seems to be located at /dev/hda4. My guess is, that your rootfs is at the same location (having a /boot partition at /dev/hda4 and then a root partition somewhere else sounds a bit silly). Try to set root=/dev/hda4 in your grub.conf.

Hope this helps!

(Another reason why this would happen is that the kernel doesn't know you filesystem type (your root fs is reiser, but your kernel doesn't recognize this.)