Kernel Panic - not syncing: Attempted to kill init!
Linux - NewbieThis 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!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I notice two things. One, the system appears to be trying to resume from suspend to ram or disk. Two, an ext3 filesystem is failing to mount. Maybe Grub is using the wrong partition as root after the reinstall. I suggest it's the swap partition, as this could explain the resume-from-suspend attempts. Remember, grub counts partitions from zero. This has screwed me over fustratingly before. Do you know the partition layout on your hard drive? That is, which partitions are used for root, swap, home? You should double check the layount with what grub has in /boot/grub/menu.lst. It should be something like
title Mandriva Linux
Now grub counts from zero, so (hda,2) is actually the third hard drive partition.
If you can't boot linux at all, a live-cd can be very helpful, so try booting from the mandriva live cd to get some diagnostic info. Or get a special-purpose live cd such as Knoppix or PuppyLinux (I really like Puppy), which are great system-rescue tools.
I've tried booting directly from the partition using Super Grub CD and I get a constant beep from the pc speaker, I've also tried booting failsafe minus the resume parameters and the kernel still panics. I have only 3 partitions a 8GB / partition, 3GB swap and a 60GB /home partition.
That was quick!
Does the Mandriva CD still boot? It could be a corrupt install. In fact, not having grub working in the first place is really unusual. Reinstalling Mandriva could be the go.
If you want to poke around a bit more first, get a live cd and look at the partitions with GParted, and look at /etc/fstab, a file which lists all the disk partitions, their type, and which device they are on (devices are special files in the /dev directory. You hard drive will be /dev/hda or /dev/sda. Partitions will be /dev/hda1, /dev/hda2, etc).
Ok. So grub is working, live cd works, and the hard drive mandriva install will not boot, even if done directly with a grub boot cd. Maybe when you reinstalled grub you overwrote something, but I don't know enough about mandriva to be sure about how they set up grub and the system boot.
Either start from scratch and reinstall, or post the content/boot/grub/menu.lst and /etc/fstab files. You should be able to mount and look at your hard drive with the mandriva livecd. Also have you tried looking on google for other mandriva uses with the same or similar problem?