Clone hard disc fails part way through

[TattyB]

C:\Documents and Settings\Administrator\VirtualBox VMs>VBoxManage clonehd "C:\Do cuments and Settings\Administrator\VirtualBox VMs\ubuntu\ubuntu.vdi" "C:\VM_Back ups\ubuntu_backup_"2013-08-01".vdi" 0%...10%...20%...30%... Progress state: VBOX_E_FILE_ERROR VBoxManage.exe: error: Failed to clone hard disk VBoxManage.exe: error: Could not create the clone medium 'C:\VM_Backups\ubuntu_b ackup_2013-08-01.vdi' (VERR_IO_CRC) VBoxManage.exe: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component M edium, interface IMedium VBoxManage.exe: error: Context: "int cdecl handleCloneHardDisk(struct HandlerA rg *)" at line 682 of file VBoxManageDisk.cpp

[dhimes]

This might be back.

On Windows 8.1 (host) with VirtualBox 4.3.24 r98716 I was trying to clone a Linux Mint guest.

C:\Users\dhimes\VirtualBox VMs>VBoxManage clonevm "Mint 17.1" --mode machine

Progress state: VBOX_E_FILE_ERROR   
VBoxManage.exe: error: Clone VM failed                    
VBoxManage.exe: error: Could not create the clone medium 'C:\Users\dhimes\VirtualBox VMs\Mint 17.1 Clone\Mint 17.1 Clone.vdi' (VERR_IO_CRC)         
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 484 of file VBoxManageMisc.cpp                                         

More info: deleting snapshots also failed (in fact, the failing of the snapshot is what prompted me to clone a backup so I could chase that error).

Also, possibly important: the account dhimes is not an administrator account. I did, however, attempt to clone using the gui running as admin. (I am new to windows and vbox).

• Win8.1, but not sure which flavor (oddly the "about your computer" doesn't say). It's probably the basic- not professional or anything.
• Brand new Toshiba Satellite S55-B
• No errors on disk

Let me know if there is something else that might be helpful and I'll do my best to get it to you.

EDIT: Edited for format and to include the command that led to the included output.

[dhimes]

Here is perhaps another clue: I tried to simply copy the VM to a usb stick as a backup, and windows is reporting that there isn't enough space. However, there is 19.1 GB left on the stick and the "Mint 17.1.vdi" file reports in at 7.78 GB. These sizes are found by right-clicking and selecting "properties."

[dhimes]

After exploring a bit, I think it might be related to this ticket: "VBoxManage clonehd creates corrupted clone if snapshot present" https://www.virtualbox.org/ticket/11432

I merged my snapshots together, but there was one that wouldn't merge. The snapshot is corrupted, and that is preventing any merging or cloning. Could this have happened as the result of a crash? What's interesting is that the current state ran great- so the snapshot information wasn't needed for proper functioning. If I could have just been able to 'ignore' or clone the exact state of the machine from the particular moment (like copying the files in a repo but not bothering with the mercurial files themselves) then it would have been useful. But having the corruption 'upstream' wrecked the ability to clone the machine- even just the current state. At least, that is my hypothesis.