LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Trouble shoot Linux-Kernel Panic (https://www.linuxquestions.org/questions/linux-newbie-8/trouble-shoot-linux-kernel-panic-821214/)

hari85 07-21-2010 04:28 AM

Trouble shoot Linux-Kernel Panic
 
Hello all,
when i booted a Linux(Centos 4.3) system today morning, i got the below messages.
...............................................................
Uncompressing Linux . OK,boot kernel
Redhat nash version 4.2.1.6 starting
mkrootdev:label / not found
mount:error 2 mounting ext3
mount:error 2 mounting none
switchroot:mount failed :22
umount /initrd/dev failed:2
Kernel panic not syncing:
Attempted to kill init!!
............................
To solve this i made a reboot. it works fine that time.
but again when i start the system after the lunch,sees the same problem.
i made another reboot. it works fine.
........................................................................
may i know what is the cause of this problem and how to solve it permanently..
i am only using centos 4.3 distro in my pc.Grub is installed in it.
GNU GRUB version 0.95.
..............................................................

Filip_Kv 07-21-2010 04:46 AM

It seems like a filesystem error to begin with. Let's hope that it is not related to a disk hardware error. I'd suggest to boot with a live cd, ubuntu for instance and from there run a fsck check to
your root drive. With fsck you can correct file system errors, that might prevent proper access to
the disk/filesystem.

However, I am afraid that since the error is not consistent, meaning that it is not happening in
every reboot, it might be related to a hard disk error. To check for hardware errors you can check
UBCD (Ultimate Boot CD), a bootable CD with which you can boot-check your system for various
errors.

However, you should first backup your data, since in such situations you may not know what might be lost during the
"healing" process.

hari85 07-22-2010 12:15 AM

Quote:

Originally Posted by Filip_Kv (Post 4040465)
It seems like a filesystem error to begin with. Let's hope that it is not related to a disk hardware error. I'd suggest to boot with a live cd, ubuntu for instance and from there run a fsck check to
your root drive. With fsck you can correct file system errors, that might prevent proper access to
the disk/filesystem.

However, I am afraid that since the error is not consistent, meaning that it is not happening in
every reboot, it might be related to a hard disk error. To check for hardware errors you can check
UBCD (Ultimate Boot CD), a bootable CD with which you can boot-check your system for various
errors.

However, you should first backup your data, since in such situations you may not know what might be lost during the
"healing" process.

...................................................................
Thank u dear friend... may i know how i can backup my data with rescue CD..i heard about knoppix .For checking and repairing file system integrity with fsck may i need knoppix or rescue cd is enough. also how to check my hard disk error using command prompt.
........................................................

Filip_Kv 07-22-2010 02:02 AM

Hmmm, what I would try to do in that situation is not to force too much the hard disk with a backup utility. I would boot from a live cd and then copy all my data by hand from the places where I know it should be. A good live cd that you can try is ubuntu live cd


All times are GMT -5. The time now is 10:49 PM.