Failed to clone: Could not create the clone medium VERR_VD_READ_OUT_OF_RANGE

[shawnmatlock]

Hello All,

I have a Win2016 host, running VBox Version 6.1.4 r136177 (Qt5.6.2).

I have 2 guests, I am only able to clone 1. Unfortunately, the second is the one I need.

The error for the second is:

Failed to clone the virtual machine AIO.

Could not create the clone medium 'D:\VM\PBA\PBA.vdi' (VERR_VD_READ_OUT_OF_RANGE).

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: MediumWrap
Interface: IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}


Thank you,
Shawn

[scottgus1]

Googling

"VERR_VD_READ_OUT_OF_RANGE" site:forums.virtualbox.org

shows this error to be rare on the forum. It may be because of a failed virtual disk.

Please zip and post the failing second guest's .vbox file, using the forum's Upload Attachment tab.

Also run this command in your command prompt and post the text output on the forum:

CD "C:\Program Files\Oracle\Virtualbox"
vboxmanage showmediuminfo "D:\VM\PBA\PBA.vdi"

[mpack]

What type of drive is D:? and what filesystem?

VERR_VD_READ_OUT_OF_RANGE is a new one on me as well, but the simplest interpretation would be that the VDI block map refers to a block offset that is beyond the end of the VDI file, meaning either that the block map has been corrupted, or more usually that the VDI has been truncated by copying it onto a disk or filesystem that couldn't handle it. Or perhaps it's a failed download.

[shawnmatlock]

Thanks Mpack & Scottgus1 for responding.

Mpack, you are probably right about corruption. The D:\ drive is a recently recovered NTFS RAID drive - RAID 5 that had 1 drive fail and another that had to be rebuilt. Except these 2, all VMs were lost. And out of these two, the first is the one that worked without issue, the second required the OS and software be reinstalled. The installations worked, and the VM runs, so I thought it should be fine.


Attached is the vbox file.

showmediuminfo:
(Since the clone (PBA.vdi) failed, I assume you wanted the showmediuminfo from the source.)

UUID: bf31e3ba-07b3-4d60-95fc-7c9d93a86487
Parent UUID: base
State: created
Type: normal (base)
Location: D:\VM\FacetsAIO\FacetsAIO.vdi
Storage format: VDI
Format variant: dynamic default
Capacity: 102400 MBytes
Size on disk: 67885 MBytes
Encryption: disabled
Property: AllocationBlockSize=1048576
In use by VMs: FacetsAIO (UUID: 3cf83917-6f93-4f31-bce1-55fdd32d8ce5)

[scottgus1]

Thanks for the uploads! Before we dig into the data you provided, we need to be sure of the original problem, which I think I may not be sure yet.

From this:

I have 2 guests, I am only able to clone 1. Unfortunately, the second is the one I need.

The error for the second is:

Failed to clone the virtual machine AIO.

Could not create the clone medium 'D:\VM\PBA\PBA.vdi' (VERR_VD_READ_OUT_OF_RANGE).

I gathered the following:
you had two working guests, VM1 & "AIO".
you cloned VM1 successfully,
you were unable to clone "AIO", with the error above.

Is this the correct understanding of your problem?

[mpack]

The installations worked, and the VM runs, so I thought it should be fine.

The VM will run just fine, provided it doesn't attempt to read from the affected portion of the drive. Of course if you clone a drive then every used portion of the drive will be copied.

There's no easy fix for it either. Both VBoxManage and CloneVDI check for damaged VDIs, and one of the basic checks is that the block map offsets are consistent with the current file. If it was my own VDI then I'd write some code to scan the block map looking for the maximum offset (ignore 0xFFFFFFFn which marks special purpose blocks), and I would make sure that the drive image was at least that many blocks long. Of course the added blocks would have to be filled with zeros, so it still means data loss.

Or, copy out the files you need and thow away the VM. In future keep VDIs small enough that backups are practical.

[shawnmatlock]

Scottgus1:

I gathered the following:
you had two working guests, VM1 & "AIO".
you cloned VM1 successfully,
you were unable to clone "AIO", with the error above.

Is this the correct understanding of your problem?

Scottgus1, that is correct.

Considering Mpack's response, and OS & Software were just reinstalled, the simplest solution is to just rebuild from scratch. No loss in data, just time.

Thanks, again for the quick responses.

[scottgus1]

OK, sounds good. Come on back if you have other questions.

A few IT thoughts going forward:

Modern-size multiple-terabyte drives are too big for RAID-5 to have a good chance to recover the array. The possibility of a second disk error while rebuilding is within the error limits of the other drives now, due to the amount of data a drive can hold. If you had a RAID 5 on terabyte-size disks, go for RAID 6.

Also, I like to remember that the 'R' in RAID stands for "Redundant" not "Reliable". Nor do any of the letters stand for "Backup". RAID will keep your computer running if a drive (or two or three depending on level) fails. RAID arrays don't always recover well from a disk failure. Good backups are a necessity even on RAIDed computers.

Finally, test your backups. A backup that can't restore isn't a backup, it's a carbon-footprint-increaser and budgeted-supply-reducer due to the electricity and disk head cycles used.