Centos 6.4 stuck during boot sequence

Hi,

I had to,reboot my office computer running Centos 6.4 and Vurtual Box.

For an unknown reason, I am stuck during the reboot process and the screen show this message:

Readahead-collector finished

And that's it. The system is stuck there and no way to gain access to my desktop and to launch my Virtual boxes.

Rather critical here on my side as I donT realy have time to rebuild a new machine etc...
coolplayAsked:
Who is Participating?
 
Daniel HelgenbergerConnect With a Mentor Commented:
Hello coolplay,

the logs are somehow incomplete; I think there might have some time passed since boot? Also, anything you had done before that particular reboot the system became unusable?
Also something is wrong with VirtualBox; kernel modules are missing it seems:
Starting VirtualBox kernel modules
  (modprobe vboxdrv failed. Please use 'dmesg' to find out why)

To further investigate this, please attach the following things:
Directly after reboot and login run these commands as root:
dmesg > boot_log.txt
ls -l /boot >> boot_log.txt
modprobe vboxdrv
dmesg |tail -n 20 >> boot_log.txt

Open in new window

Then, attach this boot.log here.
And attach also: /boot/grub/grub.conf

Also, you might want to run search&replace over these files to protect any confidential info.
0
 
GaryCommented:
Can you do CTRL+ALT+F2 and get to the shell?
If so check you startup/run levels.
0
 
coolplayAuthor Commented:
Yes I can access to ctrl alt F2 .. But sorry (newbie) I don't know how to check my startup/runlevels :-(

For info, I never had any problem like this before that machine was working just fine for years ( so so you know)
0
Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

 
coolplayAuthor Commented:
I just checked my /etc/inittab and I do have this :

id:5:initdefault

This is the only linein my inittab file!
0
 
Daniel HelgenbergerCommented:
The good news: If you can log in using the console this is nothing super serious and commonly fixable.
The bad news: this might as well take a while.

Please post the contents of /var/log/boot.log,
as well as the output from these commands after you logged in the console:
tail -n 50 /var/log/messages
dmesg|tail -n 50

Open in new window


I would guess there is a problem initizing  X or your default window manager - but lets have a lock at the logs first! It would help a lot if you would use code tags for the logs or attached the them as files here.
0
 
coolplayAuthor Commented:
Hi Helge000,

here attached are the results of the asked request
bootlog.txt
outputcommand1.txt
outputcommand2.txt
0
 
coolplayAuthor Commented:
Indeed the problem was related to virtualbox ! I did update VirtualBox to,the last release and everything went back to normal
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.