Kernel Panic issue...please assist

[furquan]

Hello Every one !!

I had a kernel panic error yesterday on one of my servers, The DC has booted the server and it was back up fine, but i need to know what is the cause of the error and how can i make sure that this does not happen again in the future, but since it is my first time with kernels i am a bit apprehensive as to how do i proceed further.

Can any one assist me in this ?

This is what my /var/log/messages file contains :-

root@alexander [~]# cat /var/log/messages | grep kernel
Apr 5 22:43:15 alexander kernel: EXT3-fs error (device cciss/c0d0p8): ext3_lookup: unlinked inode 2586383 in dir #2586408
Apr 5 22:43:15 alexander kernel: Aborting journal on device cciss/c0d0p8.
Apr 5 22:43:15 alexander kernel: EXT3-fs error (device cciss/c0d0p8): ext3_lookup: unlinked inode 2586352 in dir #2586408
Apr 5 22:43:15 alexander kernel: EXT3-fs error (device cciss/c0d0p8): ext3_lookup: unlinked inode 2586343 in dir #2586408
Apr 5 22:43:15 alexander kernel: EXT3-fs error (device cciss/c0d0p8): ext3_lookup: unlinked inode 2586355 in dir #2586408
Apr 5 22:43:15 alexander kernel: EXT3-fs error (device cciss/c0d0p8): ext3_lookup: unlinked inode 2586357 in dir #2586408
Apr 5 22:43:15 alexander kernel: EXT3-fs error (device cciss/c0d0p8): ext3_lookup: unlinked inode 2586361 in dir #2586408
Apr 5 22:43:15 alexander kernel: EXT3-fs error (device cciss/c0d0p8): ext3_lookup: unlinked inode 2586381 in dir #2586408
Apr 5 22:43:15 alexander kernel: EXT3-fs error (device cciss/c0d0p8): ext3_lookup: unlinked inode 2586364 in dir #2586408
Apr 5 22:43:15 alexander kernel: EXT3-fs error (device cciss/c0d0p8): ext3_lookup: unlinked inode 2586358 in dir #2586408
Apr 5 22:43:15 alexander kernel: EXT3-fs error (device cciss/c0d0p8): ext3_lookup: unlinked inode 2586367 in dir #2586408
Apr 5 22:43:15 alexander kernel: ext3_abort called.
Apr 5 22:43:15 alexander kernel: EXT3-fs error (device cciss/c0d0p8): ext3_journal_start_sb: Detected aborted journal
Apr 5 22:43:15 alexander kernel: Remounting filesystem read-only
Apr 5 23:18:19 alexander kernel: klogd 1.4.1, log source = /proc/kmsg started. Apr 5 23:18:19 alexander kernel: Linux version 2.6.18-238.1.1.el5 (mockbuild@x86-008.build.bos.redhat.com) (gcc version 4.1.
2 20080704 (Red Hat 4.1.2-50)) #1 SMP Tue Jan 4 13:32:19 EST 2011

The time the server went down and then when it came back up.

How do i find out what partition was having any issue and what was the issue.

Please assist.

[Infopro]

Apr 5 22:43:15 alexander kernel: Remounting filesystem read-only

Do you have backups of your account(s) from this server? If not you should get them done right away to be safe.

[furquan]

Thank you so much for the response, Can you tell me why do you say so, ? Is it very very serious ? Let me know if you need any further inputs ?

[Infopro]

Having backups is always important, especially when your server is having issues such as this. Get your important files backed up. The below threads, some old, may not be useful at all but should give my suggestion some context.

http://forums.cpanel.net/f5/unlinked...in-145333.html
http://forums.cpanel.net/f5/read-onl...em-170622.html
http://forums.cpanel.net/f5/read-onl...tem-67885.html
http://forums.cpanel.net/f5/centos-5...ggy-73160.html

[furquan]

Thank you for the useful links Inforpro...i shall have it looked into ..thank you once again