Virtual Box issue after fsck fix

[rymd80]

I'm running Ubuntu 9.04 and have been running VirtualBox happily for several months. My system wouldn't boot this morning and it took booting off the cd and running fsck from there to get my system to boot.

The fsck deleted the Virtual box container file. I had tar'd the .VirtualBox directory a few days ago, so I deleted the .VirtualBox directory and untar'd the backup.

Now, when I click on the VirtualBox icon, nothing happens, so I launched a cmd window and ran VirtualBox manually.

Nothing happens, it seems to just hang.

Here is the output of dmesg

[ 2795.780802] VBoxNetFlt: dbg - g_abExecMemory=ffffffffa0c70820
[ 2795.786848] VBoxNetAdp: dbg - g_abExecMemory=ffffffffa0c8dfc0
[ 3092.127575] vboxdrv: Trying to deactivate the NMI watchdog permanently...
[ 3092.127578] vboxdrv: Successfully done.
[ 3092.127579] vboxdrv: Found 2 processor cores.
[ 3092.127627] VBoxDrv: dbg - g_abExecMemory=ffffffffa0acff00
[ 3092.127641] vboxdrv: fAsync=0 offMin=0x186 offMax=0x1443
[ 3092.127676] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[ 3092.127677] vboxdrv: Successfully loaded version 3.0.4 (interface 0x000e0000).
[ 3092.334066] VBoxNetFlt: dbg - g_abExecMemory=ffffffffa0c70820
[ 3092.336191] VBoxNetAdp: dbg - g_abExecMemory=ffffffffa0c8dfc0

Does anyone have an idea? Thx

[Sasquatch]

You already mentioned that some files on your drive were missing or corrupt, did you try a reinstall of VB to fix those files? Maybe some other packages got corrupted which VB depends on.

[rymd80]

I forgot to mention that I reinstalled VB in case it had gotten corrupted.

[Sasquatch]

Are there other programs that don't work, or behave strange compared to before the check? It's quite possible your whole system got messed up.