virtualbox.org

EDIT: is it possible to move this to Windows hosts ? Sorry, my guest is linux but host is Windows

Upgraded VBox to 6.1.4, and somehow, and I really hope not, my virtual drive image (with 90+gb of data ..) got corrupted (really hope not) . It is not recognized as valid.

I tried removing it from VBox media manager, and re-import again. Result is I get pop-up dialog telling me image is corrupted... But it shouldn't be really, it worked just fine with VBox 6.0.x..

Could not open the medium 'D:\VMs\shared-drives\dev-drive.vhd'.
VD: error VERR_VD_IMAGE_CORRUPTED opening image file 'D:\VMs\shared-drives\dev-drive.vhd' (VERR_VD_IMAGE_CORRUPTED).

Result Code:
E_FAIL (0x80004005)
Component:
MediumWrap
Interface:
IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}
Callee:
IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d}
Callee RC:
VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)


Any idea ..?

VHD images are notoriously prone to corruption, but the upgrade to VirtualBox 6.1.4 did not cause it. As far as I know, 6.1.4 doesn't even have new code for detecting corruption in VHD (it's not like it's a hot new format requiring development work) - and obviously there's no way that replacing an executable caused a VHD to be modified.

I guess a recent backup of this important data is out of the question?

The only thing I can suggest is to try cloning the VHD using CloneVDI. No guarantees of course, but CloneVDI tends to be less fussy about some conformance issues than VirtualBox is. Also its code for reading VHD is completely independant and can't possibly be affected by VirtualBox version changes.

and p.s. since you chose an alien format I'm afraid you'll find that there's little repair knowledge for it around here. You'd have to research how people repair VHD in places where it's a preferred format. For VirtualBox you should be using VDI.

Thank you , mpack, I actually found some N year old thread you were helping someone else with CloneVDI.

For me, I resolved it simpler / did not have to go down to fixing the image, nothing was broken / corrupted with it.
Thus, I do much believe it is some VBox glitch, may be with some interface it's using to open the files, dunno .. .(i haven't checked any of it's code tbh).

So what I did: in Win10 disk manager, attach the vhd image. It was attached, thus, I presume there was _nothing_ wrong with it (unlike VBox thinking ..).
No mounting of anything inside it, as it's a Linux fs inside.

I just removed it from Win disk manager, and then re-attached it fine to VBox media manager. I booted my Linux, and so far I saw no problems with anything inside - all fs intact.
Some glitch with something ...

> ...and p.s. since you chose an alien format I'm afraid you'll find that there's little repair knowledge.

After that, because I did have space, I Vboxmanage clonemedium --format vdi it, and archived the old one

Thanks for response.