E
E
exernet2015-08-12 11:30:10
linux
exernet, 2015-08-12 11:30:10

Kernel Panic on OS boot (Red Hat). Is SELinux to blame?

Greetings! Tell me, please, with a problem.
Server with OS - Red Hat.
Kernel 2.6.32-279.el6.x86_64
The server is running on VmWare.
It worked fine, but suddenly, in the morning, it stopped letting the user in. Decided to restart the server. After a reboot, the server crashed into Kernel Panic.
grub.conf config

root (hd0,0)
    kernel /vmlinuz-2.6.32-279.el6.x86_64 ro root=UUID=357f520e-d03a-4990-996b-06b24ac965bb rd_NO_LUKS KEYBOARDTYPE=pc KEYTABLE=us LANG-en_US.UTF-8 rd_NOMD SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_NO_LVM biosdevname=0rd_NO_DM rhgb quiet
    initrd /initramfs-2.6.32-279.el6.x86_64.img

The boot logs show that the problem is with SELinux.
f6226cb8dda24ef9b762fe576ab0ea79.PNG
Although the load_policy file is in place.
[[email protected] sbin]# ls -la | grep load_
    -rwxr-xr-x. 1 root root 11216 Mar 6 06:04 load_policy

If you disable SELinux when loading the kernel, then it falls into a new error:
26ddcd7c9e514769bdf17aacca9f7856.PNG
Yes, and in fact, I read that it makes no sense to disable SELinux.
Found a similar issue with xen lists.xen.org/archives/html/xen-users/2013-01/msg0... but I didn't quite understand how he solved it. If someone translates on the fingers, I will be grateful.

Answer the question

In order to leave comments, you need to log in

[[+comments_count]] answer(s)
A
Alexey Ostin, 2015-08-12
@nitso

If everything worked before and suddenly stopped - there can be a lot of options. The most likely scenario is an image problem. Try booting into safe-mode or from a bootdisk, scan fs, go into chroot.
The problem with the image (disk, fs) is hinted at by a panic immediately after mounting root and trying to go there.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question