LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Kernel panic (https://www.linuxquestions.org/questions/linux-newbie-8/kernel-panic-897807/)

jonaskellens 08-17-2011 05:44 AM
Kernel panic
 
Hello,

anyone knows what these messages could tell me about the problem on my server :
Code:
...
attempt to access beyond end of device
dm-0: rw=0, want=9179442040, limit=60555264
/sbin/init: error while loading shared libraries: /lib64/libsepol.so.1 : cannot read file data: Invalid argument
Kernel panic - not syncing: Attempt to kill init!
Server would no longer boot up.. and always showed this message.

Peverel 08-17-2011 12:18 PM
Presumably a corrupted disk address. The limit is a bit less than 3.5G, which may be the number of blocks on some disk, "want" is about 140G.

jonaskellens 08-18-2011 04:28 AM
Quote:
Originally Posted by Peverel (Post 4445753)
Presumably a corrupted disk address. The limit is a bit less than 3.5G, which may be the number of blocks on some disk, "want" is about 140G.
I know it's a general question, but what could be causing this ? Is it CentOS ? Is it software on the server ? Is it much much traffic to the server (as in an attack) ?

Peverel 08-20-2011 03:35 AM
Well, it is during the initial boot, so not traffic on the server, probably a corrupted file. Init is trying to read a file from an invalid position. Not obvious where the error is: it may be in the shared library specified, in init itself, or in the file system. Can you boot with a rescue disk and run fsck on the file system?

jonaskellens 08-21-2011 03:32 AM
Quote:
Originally Posted by Peverel (Post 4448384)
Well, it is during the initial boot, so not traffic on the server, probably a corrupted file. Init is trying to read a file from an invalid position. Not obvious where the error is: it may be in the shared library specified, in init itself, or in the file system. Can you boot with a rescue disk and run fsck on the file system?
This is a production server. There was no time to run fsck. We placed a snapshot taken earlier. So also all information in the logfiles is gone as we went back to a state were the problem did not yet occur.

The problem has not yet re-occured, but it would be very nice to know what caused the kernel panic and the corrupt file system. Sadly we do not have much information...


All times are GMT -5. The time now is 05:30 AM.