It looks like
crond has started successfully: the problem might be with whatever comes after crond. Or it might be triggered by something
crond starts up.
sshd has already started and network parameters have already been set, so you should be able to login with SSH.
If that does not work, the kernel may be hung. To troubleshoot, interrupt the automatic boot at the GRUB menu, and add a boot option (e.g.
single) to boot the system into a minimal state ("single user mode"), omitting services like
After doing that, maybe first check
/var/log/messages, just in case there is a problem that causes log messages to be recorded but fails to display them.
Classically, the start-up scripts in
/etc/rc3.d would be executed in alphanumerical order and comparing your boot messages on your screenshot to the contents of
/etc/rc3.d on my RHEL VM looks like the order does match... so, run
ls /etc/rc3.d and see what scripts come after
S90crond on your installation if you need to know what would be the next steps in the start-up process.