Idea #1: Is there a way to REPAIR an RHEL 6.2 installation?

During the start-up procedure, after a recent forced reboot, my Linux machine (RHEL 6.2) hangs right after successfully starting virt-who. I can use login screens (Alt + F2/F3...) in text mode.

I am clueless -- how can I find out what is the next step in the startup sequence? That step is most likely what is causing it to hang.

These are the last lines saved to /var/log/boot.log:

Starting RPC idmapd: [60G[[0;32m  OK  [0;39m]
Starting cups: [60G[[0;32m  OK  [0;39m]
Starting acpi daemon: [60G[[0;32m  OK  [0;39m]
Starting HAL daemon: [60G[[0;32m  OK  [0;39m]
Starting PC/SC smart card daemon (pcscd): [60G[[0;32m  OK  [0;39m]
Retrigger failed udev events[60G[[0;32m  OK  [0;39m]
Loading autofs4: [60G[[0;32m  OK  [0;39m]
Starting automount: [60G[[0;32m  OK  [0;39m]
Enabling Bluetooth devices:
Starting sshd: [60G[[0;32m  OK  [0;39m]
Starting ntpd: [60G[[0;32m  OK  [0;39m]
Starting mysqld:  [60G[[0;32m  OK  [0;39m]
Starting postfix: [60G[[0;32m  OK  [0;39m]
Starting abrt daemon: [60G[[0;32m  OK  [0;39m]
Starting ksm: [60G[[0;32m  OK  [0;39m]
Starting ksmtuned: [60G[[0;32m  OK  [0;39m]
Starting Qpid AMQP daemon: [60G[[0;32m  OK  [0;39m]
Starting crond: [60G[[0;32m  OK  [0;39m]
Starting atd: [60G[[0;32m  OK  [0;39m]
Starting libvirtd daemon: [60G[[0;32m  OK  [0;39m]
Starting rhsmcertd 240 1440[60G[[0;32m  OK  [0;39m]
Starting virt-who: [60G[[0;32m  OK  [0;39m]