[SOLVED] RHEL4 Strange kernel panic on boot. Kernel Update no solution
Hi,
I have the following strange thing with a RHEL4 installation. Since last week, the system did a reboot and now something is really fucked up. During boot we get the following messages (don't care about 'strange' typo's, my colleague typed it 'blind' from the screen) Code:
scanning logical volumes HDD is sda. The strange thing is that we never see a 'could not mount blabla' or similar messages. First we thought it was a failing kernel update by plesk, but even after manually updating the kernel with RHN RPM's, still the same message. Booting with rescue mode and then chroot the system works. After that we even can start things like plesk and so on. We double checked things with another RHEL4 install, and at least two things were odd: 1: the working machine has /dev/dm-0 and /dev/dm-1, the broken one doesn't 2: some files on /dev didn't have group root, but 252 We tried to recreate the /dev/dm-X nodes with [vgmknodes -v], output: Code:
file descriptor 20 left open We have a copy of the boot partition so if one need more info please let me know. grub.conf: Code:
default=0 Code:
echo Making device-mapper control node And for those who are reading this today: Already have a happy newyear! :D Thanks! Onno. |
Hi,
In addition to my question I discovered the following: I installed a VM with RHEL4 to check some things out, and I discovered that the next message right after "switchting to new root" is "SELinux disabled on runtime". At least that is on a working machine. So I would say (please disagree with me if I'm wrong) that SELinux is causing the kernel to panic right?! Hope someone can reply on this with useful info. Thanks! Onno. |
I am also getting the same problems with PUD linux, and antix linux on my virtualbox vm's. when i tried installing pud on my laptop, i got the kernel panic error, so i reverted back to ubuntu and did a virtual machine to see what was wrong with pud, if it didnt like my hardware or whatnot. im at a loss here too. so if anyone has any hints or answers, shoot, i'll take them.
|
Hi,
This problem is solved. I found out by myself that the problem was caused by a faulty /sbin/init Normally the init exec is around 40KB or more, but on all these systems it was just around 15KB (!) We really don't know what happend, we think "someone" screwed it up. After doing a reinstall of SysVinit RPM, everything started to work again. To complete this post I'll include the commands used to force the reinstall of the SysVinit Package. # rpm -qa |grep -i sysvinit SysVinit-2.85-34.4 # rpm -e --nodeps SysVinit-2.85-34.4 # yum install sysvinit That did the trick. At least thanks for replies. Onno. |
All times are GMT -5. The time now is 04:14 PM. |