Centos6 is hanged on startup.Showing only white bar
 

My centos machine was working properly on VM server ESX 5.0
Now i transfered it to VM server ESX 3.5. Then also it was working properly. But after some month when i gone to restart the machine it is showing only WHITE BAR WITH TEXT CENTOS 6.4.
After this nothing is happen.
But i m able to ping the machine through IP address since i set the static IP.

How can i resolve this problem

When the white line is showing, click the white bar (or somewhere inside to get the focus) and press the up or right arrow. That normally shows what's going on during the boot process...that should show you where it's getting stuck.

Also try going to other TTY's (Ctrl+Alt+F<1-6>) to see if you can gain any other additional information.

Lastly try booting into single user mode and seeing what the log files tell you.

Hope that helps...

It is hanged after below line
Starting atd: [OK]


And then nothing is showing.

Are you able to boot into single user mode?

What command need to type to enter into SINGLE mode USER
 

To enter into single user mode
first i tried to edit the kernal line. But don't know what command to type exactly into edit screen to enter into single user mode.
I m attaching my machine screen shots.
Now plz guide me.

Yes now i m able to login in Single User Mode. Here i got only terminal but not GUI.

Now i searched in etc/rc3.d and it showed that after atd there is one process name is 'libvirt-guests'

IS it related to any hanging problem or there is something different that is not allowing me to enter into the GUI?

Again i noted one thing durring startup is 'Enabling Bluetooth Device [OK]'
But my host server is not supporting any bluetooth.
So how can i disable this bluetooth device to startup at boot time?

If you're using the GUI then you're booting into level 5 so that would be /etc/rc5.d. You can check /etc/inittab to see the level to which you login.

In order to stop the bluetooth device at startup you can check the persistence such as
# chkconfig --list | grep -i bluetooth

And to stop the service from starting simply type
# chkconfig <name_of_service> off
where <name_of_service> would be the service recognized by the system like atd, libvirt-guests, etc.

Lastly you may want to check your /var/log/messages file and /var/log/boot.log file to see if that is giving you any additional information about your boot up process.

Message logs showing something like
"Aug 4 05:20:04 CENTOS23 winbindd[1448]: [2013/08/04 05:20:04.247390, 0] libads/kerberos_util.c:101(ads_kinit_password)
Aug 4 05:20:04 CENTOS23 winbindd[1448]: kerberos_kinit_password CENTOS23$@OBJECTEDGE.COM failed: Client not found in Kerberos database
Aug 4 05:25:18 CENTOS23 winbindd[1448]: [2013/08/04 05:25:18.561385, 0] libads/kerberos_util.c:101(ads_kinit_password)
Aug 4 05:25:18 CENTOS23 winbindd[1448]: kerberos_kinit_password CENTOS23$@OBJECTEDGE.COM failed: Client not found in Kerberos database
Aug 4 05:30:08 CENTOS23 winbindd[1448]: [2013/08/04 05:30:08.635264, 0] libads/kerberos_util.c:101(ads_kinit_password)
Aug 4 05:30:08 CENTOS23 winbindd[1448]: kerberos_kinit_password CENTOS23$@OBJECTEDGE.COM failed: Client not found in Kerbemessages
"

Those messages from the logs seem to highlight that you're system is trying to authenticate using Kerberos.
Try turning off the LDAP/Kerberos service and starting it manually after the system has started.

Remember troubleshooting is an art, not a science so it may take a while to figure out the exact issue for the first time.
But it looks like you're getting closer