Hi,
I have my linux box setup for years without any problem until two days ago. It was a power failure and the system hang during boot process.
The system is redhat 7.2. The following is my observation:
1. I can go to single mode.
2. The system hang after setting hostname XXXX.XX: [OK].
3. To interrupt the booting process, I used ctl_C and it showed the message:
INIT: Entering runlevel: 3
Updating /etc/fstab exevp: No such file or director [FAILED]
Checking for new hardware/etc/rc3.d/S05kudzu: /usr/sbin/kudzu: No such file or directory [FAILED]
touch: creating '/var/lock/subsys/kudzu': no such file or directory
Flushing all curentrules.....
Clearing ......
Applying ipchains firewall rules:
touch creating ......
Setting network parameters: [OK]
Bringing up interface lo:
4. System hang again and there is no way I can interrup the system.
Can anyone please tell me what could be the problem? and how to fix it?
I have tried to run fsck -yf /dev/hda1....hda8 in single mode and all should be OK now. However, the problem is still there.
TIA
Roger
I have my linux box setup for years without any problem until two days ago. It was a power failure and the system hang during boot process.
The system is redhat 7.2. The following is my observation:
1. I can go to single mode.
2. The system hang after setting hostname XXXX.XX: [OK].
3. To interrupt the booting process, I used ctl_C and it showed the message:
INIT: Entering runlevel: 3
Updating /etc/fstab exevp: No such file or director [FAILED]
Checking for new hardware/etc/rc3.d/S05kudzu: /usr/sbin/kudzu: No such file or directory [FAILED]
touch: creating '/var/lock/subsys/kudzu': no such file or directory
Flushing all curentrules.....
Clearing ......
Applying ipchains firewall rules:
touch creating ......
Setting network parameters: [OK]
Bringing up interface lo:
4. System hang again and there is no way I can interrup the system.
Can anyone please tell me what could be the problem? and how to fix it?
I have tried to run fsck -yf /dev/hda1....hda8 in single mode and all should be OK now. However, the problem is still there.
TIA
Roger