Centos 6.3 won't boot after 4.2.0 upgrade

[oksofar]

I have a Centos 6.3 guest on a Windows 7 host. I've been using it for a while.

After I upgraded to VBox 4.2.0, the Centos guest won't boot.

It starts to come up, and produces the following messages. But never completes.



If I press the esc key, I can see the progess bar. After the above message shows, the bar continues to move to the right until it's all white and the word "centos 6.3" is also white.

Then the system hangs. If I insert a ctrl-alt-delete, the system restarts with the same result.

How can I get this thing to start so I can get my files??

thanx

[mpack]

Minimal information needed for assistance
viewtopic.php?f=24&t=48476

[oksofar]

OK - here's the requested info -

VBox 4.2.0
Guest Additions version 4.1.18. I tried to install the latest one, but it didn't take.
Host: Windows 7 64 bit.
Guest: Centos 6.3 64 bit.
Host RAM: 8GB
Guest RAM: 768MB

Log file attached

[sej7278]

you haven't changed the io-apic or vt-x settings have you? or removed a floppy or hard drive?

your log looks pretty similar to my working OEL 6.3 log, but yours finishes just before the AHCI and PIIX3 stuff starts, which is the end of the boot process i guess.! definitely something funky regarding your disks.

does it still work if you roll back to 4.1.18? do other guests work?

have you tried booting using a linux rescue cd and mounting the drives in a chroot, as i guess it could be a problem with the guest itself - like its needs a fsck or has a typo in fstab.

[mpack]

Is this a complete log? It doesn't look like it. Even if the guest hung and you had to close the VM window, I would see VBox shutdown steps appearing in the log. Please shut down (not suspend) the VM before submitting a log.

[oksofar]

Here's the complete log. The last one didn't have the shutdown.

[oksofar]

I'm going to treat this as a Linux issue, not a VBox issue. So this ticket can be closed.

Thank you all for your attention to this topic.

[sej7278]

I'm going to treat this as a Linux issue, not a VBox issue. So this ticket can be closed.

Thank you all for your attention to this topic.

yes it does look like you've messed up your permissions or something within the guest itself, there's no errors in the vbox log