FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Mandrake 9.2 =<3 and Red Hat 8.0 (server)
Posts: 242
Rep:
Kernel Panic
I dual boot with Windows XP pro, and things were running fine, but something happened when I tried to reboot into linux. I had been using it for like a week and I do not know what happened, but I get a kernel panic saying that it can't find the init. I was told it's because I have Partition magic on my system, but I havent used it since my install. How can I fix this panic without reinstalling, and I have a knoppix cd so i think I should be able to mount the partition in there to make any changes (/boot/grub.conf)
You don't need Knoppix for that. The first Fedora Core CD contains a very helpful "rescue" mode option which you can use to boot into your system and repair it. What it is necessary to repair it depends on the level of damage and your familiarity with Linux in general. You didn't quote the error message. Reinstalling GRUB could be enough. Checking the root partition for damaged packages could find damage. A missing /initrd directory could be the culprit, and many other reasons. Most of them are easy to fix.
Distribution: Mandrake 9.2 =<3 and Red Hat 8.0 (server)
Posts: 242
Original Poster
Rep:
kernel panic: could not load the init
something along those lines. I have tried the rescue cd's before, and they really have not gotten me too far. i'd appreciate some help and a better understanding of why they happen and how to prevent them.
Originally posted by wldkos
[B]kernel panic: could not load the init
something along those lines.
That doesn't help, because it's not the original error message. The term "init" has several meanings.
Quote:
I have tried the rescue cd's before, and they really have not gotten me too far.
That is not enough information and hence doesn't help either.
You need to understand that the rescue mode provides an independent working system which you can boot into to get a working set of utilities. Certainly enough tools to examine and mount your partitions or re-install GRUB. One of the optional features of the rescue mode is to search for your installed system and "chroot" into it. Whether the rescue mode is of good use depends on how you use it.
Quote:
i'd appreciate some help and a better understanding of why they happen and how to prevent them.
Most probably the kernel couldn't find the root partition, hence the error couldn't find init etc.. check your grub.conf and fix the root directory.
Here is mine:
..
splashimage=(hd1,7)/grub/splash.xpm.gz
title Fedora Core (2.4.22-1.2115.nptl)
root (hd1,7)
kernel /vmlinuz-2.4.22-1.2115.nptl ro root=LABEL=/ hdd=ide-scsi rhgb
initrd /initrd-2.4.22-1.2115.nptl.img
..
The root partition should be whatever the number (in sequence, not literally the device number itself) .. and for my example above, I've linux in my 2nd HD in the 7th partition.
This is the error, the rest is a result of this error as it doesn't find your root partition. To fix it, boot into rescue mode (or knoppix, whatever you're familiar with). Examine your partition table to find out which one is the root partition. E.g with
parted /dev/hda print
assuming that /dev/hda is your primary IDE hard disk drive. Substitute /dev/hdaX in
e2label /dev/hdaX /
with your partition device to re-create the missing partition label on your root partition. They try a reboot.
Distribution: Mandrake 9.2 =<3 and Red Hat 8.0 (server)
Posts: 242
Original Poster
Rep:
Quote:
Originally posted by misc This is the error, the rest is a result of this error as it doesn't find your root partition. To fix it, boot into rescue mode (or knoppix, whatever you're familiar with). Examine your partition table to find out which one is the root partition. E.g with
parted /dev/hda print
assuming that /dev/hda is your primary IDE hard disk drive. Substitute /dev/hdaX in
e2label /dev/hdaX /
with your partition device to re-create the missing partition label on your root partition. They try a reboot.
e2label is the program I would use to do that? I have never heard of that one.
Distribution: Mandrake 9.2 =<3 and Red Hat 8.0 (server)
Posts: 242
Original Poster
Rep:
Quote:
Who is "they"? [/B]
I was referring to kernel panics, hence the topic of this thread, meaning I should not have to explain what "they" are since it is the whole idea of this thread.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.