Clone VM failed

[tobreakfree]

Hello together,

a few days ago i cloned a VM (7.5 GB) - without any problems. Now I try to do it with the same VM (now 13 GB) and I get an error. There´s no difference between the command line tool and the GUI Version.

VirtualBox Version 4.2.6 r82870
Windows Host Version: Windows 7 Home Premium Service Pack 1
Windows Guest Version: Windows 7 Professional x64
Filesystem on C:\ and F:\ is NTFS.

Command Line
C:\Program Files\Oracle\VirtualBox>vboxmanage clonevm "Windows 7 Professional (x64)" --name "Windows 7 Professional (x64)_TEST"
0%...10%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage.exe: error: Clone VM failed
VBoxManage.exe: error: Could not create the clone medium 'F:\VirtualBox\Windows7 Professional (x64)_TEST\Windows 7 Professional x64)_TEST.vdi' (VERR_UNRESOLVED_ERROR)
VBoxManage.exe: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Medium, interface IMedium
VBoxManage.exe: error: Context: "int __cdecl handleCloneVM(struct HandlerArg *)" at line 472 of file VBoxManageMisc.cpp

Up to 11% (3.044.456 KB) everything is ok. But then I get the error message.

Any ideas? Thank you in advance and best regards, Alex

[mpack]

Well, it's obviously a disk write error of some sort. Either you are wrong about the F:\ filesystem being NTFS, or you've run out of disk space, hit a bad sector etc.

What exactly is drive F?

[tobreakfree]

Thank you very much for your answer!

Hard Disc f:\ is an external storage. I reproduced the error in 2 different ways. May it´s possible, that the original virtual machine is corrupt?

Procedure on Drive c:\
C:\Program Files\Oracle\VirtualBox>vboxmanage clonevm "Windows 7 Professional (x64)" --name "Windows 7 Professional (x64)_TEST"
0%...10%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage.exe: error: Clone VM failed
VBoxManage.exe: error: Could not create the clone medium 'C:\VirtualBox\Windows 7 Professional (x64)_TEST\Windows 7 Professional x64)_TEST.vdi' (VERR_UNRESOLVED_ERROR)
VBoxManage.exe: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Medium, interface IMedium
VBoxManage.exe: error: Context: "int __cdecl handleCloneVM(struct HandlerArg *)" at line 472 of file VBoxManageMisc.cpp

Procedure on Drive d:\
C:\Program Files\Oracle\VirtualBox>vboxmanage clonevm "Windows 7 Professional (x64)" --name "Windows 7 Professional (x64)_TEST"
0%...10%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage.exe: error: Clone VM failed
VBoxManage.exe: error: Could not create the clone medium 'D:\VirtualBox\Windows 7 Professional (x64)_TEST\Windows 7 Professional (x64)_TEST.vdi' (VERR_UNRESOLVED_ERROR)
VBoxManage.exe: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Medium, interface IMedium
VBoxManage.exe: error: Context: "int __cdecl handleCloneVM(struct HandlerArg *)" at line 472 of file VBoxManageMisc.cpp

c:\ 81 GB free, Filesystem NTFS
d:\ 286 GB free, Filesystem NTFS [partition on the same hard disc as c:\]
f:\ 765 GB free, Filesystem NTFS [external storage]

Thank you and best regards, Alex

[mpack]

Hard Disc f:\ is an external storage. I reproduced the error in 2 different ways. May it´s possible, that the original virtual machine is corrupt?

It does look that way, though in that case I'm surprised it just says "file error" and not "read error". One possible reason could be that it's actually a seek error, which would be caused if e.g. the source file had been truncated at some point in its past.

It would do no harm to run chkdsk on both the source and destination drives. NTFS is not well designed for removable storage, so you might well have problems on the external drive filesystem.

As to possible solutions :-

1. You could try cloning the VDI with CloneVDI. It will probably not work, but the resulting diagnostic error might be instructive. If the above theory is correct then I'm anticipating that the error will be "block map contains errors".
2. If the original VM still boots up then you can try running Disk2VHD from inside the VM, writing the VHD to a shared folder. Then I would convert the VHD to VDI using CloneVDI. Then build a new VM around the VDI, being sure to get the recipe as close as possible.

[tobreakfree]

Thank you!

CHKDSK found some damaged sectors. After the procedure it was possible to clone the VM without any problem.

Best regards and thanks again.