VERR_VD_VMDK_INVALID_HEADER in virtualbox after hard reset
8,004
This is a problem with a corrupt vmdk disk. It is discussed briefly on the Whonix troubleshooting page.
To fix it, the idea is to convert the vmdk disk into a vdi disk, unmount the old vmdk disk from the VM and attach in its stead the newly minted vdi disk.
Tools to do that are discussed here and here.
Related videos on Youtube
Author by
Salustiano Muniz
PHP Programmer with frontend and Mysql skills
Updated on September 18, 2022Comments
-
Salustiano Muniz over 1 year
I had to hard reset my notebook after my system (Ubuntu gnome 15.04) freezes. Now I'm not able to resume the vagrant and if I try to load it on virtualbox I receive this message:
Could not open the medium '/home/stsmuniz/VirtualBox VMs/vagrant_default_1441759013197_1623/box-disk1.vmdk'. VMDK: inconsistency between grain table and backup grain table in '/home/stsmuniz/VirtualBox VMs/vagrant_default_1441759013197_1623/box-disk1.vmdk' (VERR_VD_VMDK_INVALID_HEADER). VD: error VERR_VD_VMDK_INVALID_HEADER opening image file '/home/stsmuniz/VirtualBox VMs/vagrant_default_1441759013197_1623/box-disk1.vmdk' (VERR_VD_VMDK_INVALID_HEADER). Código de Resultado: NS_ERROR_FAILURE (0x80004005) Componente: MediumWrap Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
Can anybody help me on solving this?
-
Salustiano Muniz over 8 yearsI did the steps shown here and after converting the box to VDI it worked. Thank you, buddy.
-
DavidPostill over 7 yearsPlease quote the essential parts of the answer from the reference link(s), as the answer can become invalid if the linked page(s) change.