Unable to export on 4.2

[drq]

I have a minimal CentOS VM that I have successfully exported before (VB 4.1.22) that is now failing on 4.2. The message given is:

Failed to export appliance /Users/sasdrq/Documents/centos-puppet.ova.

Could not create the clone medium '/Users/sasdrq/Documents/centos-puppet-disk1.vmdk' (VERR_VD_READ_OUT_OF_RANGE).

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: Appliance
Interface: IAppliance {3059cf9e-25c7-4f0b-9fa5-3c42e441670b}

Any guidance will be appreciated.

[mpack]

Frankly, this doesn't sound like a VirtualBox problem. It seems to me that the source VMDK may be incomplete VMDK (i.e. I'd guess that it's a segmented VMDK, and you don't have all the segments). However I'm having to guess because you provide no information about the source. Fix that (e.g. with a directory listing of the VM and snapshot folders) and we can talk some more. If the source is a VMDK then perhaps show (or post if more than a few lines) the descriptor (if the source VMDK is surprisingly small, a few K at most, then it's actually a small text file called the descriptor). If the source file is large then it has an embedded descriptor which is hence harder for you to post - it may be viewable with a hex editor however.

[drq]

The machine name is Cents:

drwxr-xr-x 8 sasdrq staff 272 Sep 17 10:33 .
-rw------- 1 sasdrq staff 28507 Sep 10 15:01 ./Cents-1.12-macosx.vbox
-rw------- 1 sasdrq staff 37982 Sep 17 10:33 ./Cents.vbox
-rw------- 1 sasdrq staff 47347 Sep 17 10:33 ./Cents.vbox-prev
-rw------- 1 sasdrq staff 86016 Sep 7 10:36 ./Cents.vdi
drwx------ 6 sasdrq staff 204 Sep 17 10:27 ./Logs
-rw------- 1 sasdrq staff 73815 Sep 17 10:37 ./Logs/VBox.log
-rw------- 1 sasdrq staff 97391 Sep 17 08:47 ./Logs/VBox.log.1
-rw------- 1 sasdrq staff 108402 Sep 17 08:42 ./Logs/VBox.log.2
-rw------- 1 sasdrq staff 96367 Sep 14 10:42 ./Logs/VBox.log.3
drwx------ 6 sasdrq staff 204 Sep 17 10:33 ./Snapshots
-rw------- 1 sasdrq staff 77680640 Sep 10 14:55 ./Snapshots/{550d4c4a-0193-4d10-9cb9-df6c3b4ba949}.vdi
-rw------- 1 sasdrq staff 126963712 Sep 17 08:42 ./Snapshots/{82dfbee9-2b59-44f2-9f3f-4335543cf6d2}.vdi
-rw------- 1 sasdrq staff 2119258112 Sep 10 14:44 ./Snapshots/{a13b69a3-7326-4914-a6e0-8362ec4ed193}.vdi
-rw------- 1 sasdrq staff 36786176 Sep 17 11:00 ./Snapshots/{b7117ce2-5915-4486-8f9d-60b0ebac95e4}.vdi

I created another VM on VB 4.2 and I can successfully export it. It seems to fail on VMs that had been created on prior versions of VB.

[mpack]

It seems to fail on VMs that had been created on prior versions of VB.

Unlikely. I can't think of any reason it would have a preference for which version of the software created the data - there have been no real format changes in recent versions.

ISTM more likely that there is some problem (i.e. corruption [*]) in the snapshot chain in that VM. Naturally this will not be a problem in a new VM which has no snapshots. It will also not be a problem until the VM tries to read the data from the old snapshot - which it may not need to do in normal operation, but is likely to do when cloning or exporting the VM. A test of that theory by cloning the VM ought to be useful (clone current state only, i.e. do not preserve snapshots). If the theory fails then at least you'll now have a merged clone which I'll bet you can export. If the theory is true then we can consider the possibilities once you report back.

[*] The corruption I would anticipate is that one or more files have been truncated.

[drq]

It is likely. It has failed during "Export Appliance" on any VM I had before upgrading to 4.2. Whether or not the format changed, it's what I'm seeing.

I'll try the clone and see what it does.

[drq]

Clone of said machine fails with the same VERR_VD_READ_OUT_OF_RANGE error.