I have a situation that is driving me up the wall and I've tried reversing most recent changes to the system to no avail.
OS: CentOS 5.3 Final
Let me explain what transpired recently:
It all started when my system locked up during a `yum -y update` session. This is an old box I use as a home server running on an ABIT KT7A-RAID motherboard. This system has been serving me well since 2001 but the inevitable had to happen - the caps have blown up - all 9 2200uF surrounding the CPU! Fortunate for me, I've always bought server boards in pairs to facilitate rapid disaster recovery and the server is now up and running. That's right, with a new KT7A-RAID motherboard - I simply swapped all peripherals to the new motherboard and took the opportunity to clean out old heat sink material - CPU now running much cooler! I run this system headless and use the serial port via hyper terminal to select kernel and/or to view boot-up messages.
When I first booted the system after recovery, the first hint of an issue occurred when nothing displayed on my hyper terminal session (BIOS indicates that my COM port is enabled). Nevertheless, the system did boot and functioned as expected. I then shut the system down and attached K, V, and M to see what was going on. After the BIOS messages, all I see is "Grub Loading stage 2" and then a hurricane of scrolling text as is usual, but then the scrolling stops after SELinux starts. Nothing else is displayed until I get to login prompt. SELinux is set to disabled in /etc/selinux/config.
I then did a `yum update` to see how far it got into the update process before the crash and a message was spewed about the need to run yum-complete-transaction. I installed yum-utils and went ahead and completed the pending transactions and performed a reboot hoping the issue would be resolved. Nada!
I then extracted a list of all packages installed just before and after the crash from /var/log/yum.log and performed a "yum reinstall" on all of them, and after a reboot, still no joy!
Can anyone shed any light on how I can go about resolving this?
Here's my grub.conf:
Code:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup01/LogVol00
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
serial --unit=1 --speed=57600 --word=8 --parity=no --stop=1
terminal --timeout=0 serial console
title CentOS (2.6.18-128.1.10.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-128.1.10.el5 ro root=/dev/VolGroup01/LogVol00 console=tty0 console=ttyS1,57600 panic=15
initrd /initrd-2.6.18-128.1.10.el5.img
title CentOS (2.6.18-128.1.10.el5xen)
root (hd0,0)
kernel /xen.gz-2.6.18-128.1.10.el5
module /vmlinuz-2.6.18-128.1.10.el5xen ro root=/dev/VolGroup01/LogVol00 rhgb console=tty0 console=ttyS1,57600 panic=15
module /initrd-2.6.18-128.1.10.el5xen.img
title CentOS (2.6.18-128.1.10.el5PAE)
root (hd0,0)
kernel /vmlinuz-2.6.18-128.1.10.el5PAE ro root=/dev/VolGroup01/LogVol00 rhgb console=tty0 console=ttyS1,57600 panic=15
initrd /initrd-2.6.18-128.1.10.el5PAE.img
title CentOS (2.6.18-128.1.6.el5PAE)
root (hd0,0)
kernel /vmlinuz-2.6.18-128.1.6.el5PAE ro root=/dev/VolGroup01/LogVol00 rhgb console=tty0 console=ttyS1,57600 panic=15
initrd /initrd-2.6.18-128.1.6.el5PAE.img
title CentOS (2.6.18-128.1.6.el5xen)
root (hd0,0)
kernel /xen.gz-2.6.18-128.1.6.el5
module /vmlinuz-2.6.18-128.1.6.el5xen ro root=/dev/VolGroup01/LogVol00 rhgb console=tty0 console=ttyS1,57600 panic=15
module /initrd-2.6.18-128.1.6.el5xen.img
title CentOS (2.6.18-128.1.6.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-128.1.6.el5 ro root=/dev/VolGroup01/LogVol00 rhgb console=tty0 console=ttyS1,57600 panic=15
initrd /initrd-2.6.18-128.1.6.el5.img
And here's my /etc/inittab:
Code:
#
# inittab This file describes how the INIT process should set up
# the system in a certain run-level.
#
# Author: Miquel van Smoorenburg, <miquels@drinkel.nl.mugnet.org>
# Modified for RHS Linux by Marc Ewing and Donnie Barnes
#
# Default runlevel. The runlevels used by RHS are:
# 0 - halt (Do NOT set initdefault to this)
# 1 - Single user mode
# 2 - Multiuser, without NFS (The same as 3, if you do not have networking)
# 3 - Full multiuser mode
# 4 - unused
# 5 - X11
# 6 - reboot (Do NOT set initdefault to this)
#
id:3:initdefault:
# System initialization.
si::sysinit:/etc/rc.d/rc.sysinit
l0:0:wait:/etc/rc.d/rc 0
l1:1:wait:/etc/rc.d/rc 1
l2:2:wait:/etc/rc.d/rc 2
l3:3:wait:/etc/rc.d/rc 3
l4:4:wait:/etc/rc.d/rc 4
l5:5:wait:/etc/rc.d/rc 5
l6:6:wait:/etc/rc.d/rc 6
# Trap CTRL-ALT-DELETE
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
# When our UPS tells us power has failed, assume we have a few minutes
# of power left. Schedule a shutdown for 2 minutes from now.
# This does, of course, assume you have powerd installed and your
# UPS connected and working correctly.
pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down"
# If power was restored before the shutdown kicked in, cancel it.
pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled"
# Run gettys in standard runlevels
1:2345:respawn:/sbin/mingetty tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6
# Run gettys in standard runlevels for serial connections
# Comm 1 (ttyS0) is being used by the UPS
#S0:12345:respawn:/sbin/agetty -L 57600 ttyS0 linux
S1:12345:respawn:/sbin/agetty -L 57600 ttyS1 linux
# Run xdm in runlevel 5
x:5:respawn:/etc/X11/prefdm -nodaemon
# OPTI-SAFE Xtreme UPS daemons
dp::wait:/usr/bin/dnpower/powersrv
du::wait:/usr/bin/dnpower/upsagentd
di::wait:/usr/bin/dnpower/upsis -s -q -w /usr/bin/dnpower
Let me know if you need more configuration files.
Regards,
tkb.