virtualbox.org

Note: My english is poor.

Hello, i have a server running windows server 2008 R2 and your Vdisk have corrupted bellow the error log when i try add the Vdisk.

• Failed to open the hard disk file F:\home\máquinas virtuais\VSERVER01\SERVER01 01112013-disk1.vmdk.
  
  Could not get the storage format of the medium 'f:\home\máquinas virtuais\VSERVER01\SERVER01 01112013-disk1.vmdk' (VERR_NOT_SUPPORTED)
  
  Result Code:
  VBOX_E_IPRT_ERROR (0x80BB0005)
  Component:
  Medium
  Interface:
  IMedium {05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac}
  Callee:
  IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554}
  Callee RC:
  VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

Thank for any help provided.

Disk-1 looks like you have mounted the wrong file. There should be a file that does not have a number to it.

Perryg wrote:Disk-1 looks like you have mounted the wrong file. There should be a file that does not have a number to it.

This Vdisk belongs to the machine, but to try fix the problem i release and removed Vdisk fom "Virtual Media Manager" and so i'm try add again the Vdisk.

No solution yet, anyone have any idea of how to help me recover this disk?

Thx.

Well, the message means that the file is not really a (complete) VMDK, but from here we can't tell you what it really is.

You could try cloning the VMDK using CloneVDI. I expect this will fail, but perhaps the error message will give you further clues as to what this file actually is.

What size is "SERVER01 01112013-disk1.vmdk"? Sometimes VMDKs come in several fragments, all of which must be together in the same folder to be a valid virtual disk. Sometimes users copy just one of the files in the set, not realizing that the entire set must be moved together. For example, if the named VMDK is very small (a few Kbytes) then it must just be the "descriptor" (header file) for the disk.

First thanks for try help mpack, but now the software show this message: "Source file corrupt - block map contains erros"

is there any way to recover it?

If it gives you that message then no, I'm afraid that the only way to fix that problem is with a new (uncorrupted) copy of the file.

So I think my VHD is gone.

Well, so then closes the discussion. Thank you all.