virtualbox.org

Hello
today Virtual Box window has crashed and since that i'm not able to start my virtual machine
.vmdk file seems to be ok it's not empty but when i look into seetting it is showing me:
Virtual Size --
Actual Size --
please help there is all my work for last 3 month i can't loose it

Please read the following carefully and respond to each item.

What is the guest OS?

Show me a file listing of the VM folder and "Snapshots" subfolder.

Create a zip file containing the <vmname>.vbox file and the "VBox.log" file (from the Logs subfolder). Do not include any files I didn't ask for.

Check disk space on the host drive, report that too.

How old is your last full backup of the VM folder?

mpack wrote:What is the guest OS? :

Debian Wheezy

Show me a file listing of the VM folder and "Snapshots" subfolder.

I'm not sure where it is

Create a zip file containing the <vmname>.vbox file and the "VBox.log" file (from the Logs subfolder). Do not include any files I didn't ask for.

http://www.mediafire.com/download/he4qj ... +Media.rar

Check disk space on the host drive, report that too.

i have 80GB empty space on my drive, and almost 1TB on virtual host

How old is your last full backup of the VM folder?

i don't have backups

Skyway wrote:

mpack wrote:Show me a file listing of the VM folder and "Snapshots" subfolder.

I'm not sure where it is

The VM folder is the folder you found the .vbox file in. The same folder should have contained your VMDK, but I see from the .vbox file that it doesn't and that is probably the source of your trouble.

Your VM is looking for a hard disk image file: "D:/skyway/skymedia/Skyway Final 2014 sep-disk1.vmdk". It would be better if it didn't need to use an absolute path to access its own hard disk.

Solution: move the VMDK file into the VM folder (see first sentence). Replace your existing .vbox file with the one attached to this message. Hopefully the VM will then work.

NOTE: It is important that in your attempts at repair that you have NOT created multiple VMs which try to access that disk. If you have then you will need to remove those redundant VMs, otherwise VirtualBox will complain about conflicting UUIDs.

mpack wrote: Solution: move the VMDK file into the VM folder (see first sentence). Replace your existing .vbox file with the one attached to this message. Hopefully the VM will then work.

Thank you very much for the solotion i start to belive that it will help , but issue is that i don't have enought space on my Disk C:/ to transfer vmdk file and there is nothing that i can delete to have more space
is it somehove possible to transfer .vbox file to disk D:/ ?

Yes, follow the tutorial: Howto: Move a VM.

Then replace the .vbox and move the VMDK as described earlier.

mpack wrote:Yes, follow the tutorial: Howto: Move a VM.

Then replace the .vbox and move the VMDK as described earlier.

i did it they are in the same folder on disk D:\skyway\Skyway Media:


i replaced .vbox file as you requested but i'm getting same error please see the files attached

p.s. it will be even huge help if somehow there was possibility to extract folders from vmdk file i tried to google solution but i didn't find anything working or usefull

Please download a copy of CloneVDI and use it to open the VMDK. I'm interested in knowing what errors if any it reports.

You can access the contents of the VMDK in two ways: (1) Create a VM which accesses it (perhaps as a second drive), (2) Run a third party virtual disk driver on the host. However, neither of these will work if the VMDK is corrupted, the truth of which is what we're trying to establish using CloneVDI.

mpack wrote:Please download a copy of CloneVDI and use it to open the VMDK. I'm interested in knowing what errors if any it reports.

You can access the contents of the VMDK in two ways: (1) Create a VM which accesses it (perhaps as a second drive), (2) Run a third party virtual disk driver on the host. However, neither of these will work if the VMDK is corrupted, the truth of which is what we're trying to establish using CloneVDI.

Than you very very very very very very very much CloneVDI fixed my issue

Um. CloneVDI was only intended to provide extra diagnostics, not fix anything. You haven't said what you did, but I'm pleased that it worked. I do suggest that in future you make regular backups of the entire VM folder.

mpack wrote:Um. CloneVDI was only intended to provide extra diagnostics, not fix anything. You haven't said what you did, but I'm pleased that it worked. I do suggest that in future you make regular backups of the entire VM folder.

I just cloned my VMDK to VDI file and genreted new UUID for it, after i created new machine from my vitual box using that new VDI drive
everything went back to normal

I see, thanks for letting us know.