Can I fix corrupted vmdk image? VERR_VD_VMDK_INVALID_HEADER
I suffered host crash when running guest OS with VirtualBox. Now the VM won't start and complain that:
Could not open them medium '[file.vmdk]` VMDK: inconsistency between
grain table and backup grain table in '[file.vmdk]'
(VERR_VD_VMDK_INVALID_HEADER).
VD: error VERR_VD_VMDK_INVALID_HEADER
opening image file '[file.vmdk]' (VERR_VD_VMDK_INVALID_HEADER)
All I actually need is to get some files from this hard disk image. And also, any way to prevent this in future? One of my hosts that I need to work with is pretty unstable and tends to crash from time to time. I wouldn't like to go through this again.
virtualbox virtual-machine
asked Jul 14 '15 at 7:40
SiliconMindSiliconMind
3064922
add a comment |
I suffered host crash when running guest OS with VirtualBox. Now the VM won't start and complain that:
Could not open them medium '[file.vmdk]` VMDK: inconsistency between
grain table and backup grain table in '[file.vmdk]'
(VERR_VD_VMDK_INVALID_HEADER).
VD: error VERR_VD_VMDK_INVALID_HEADER
opening image file '[file.vmdk]' (VERR_VD_VMDK_INVALID_HEADER)
All I actually need is to get some files from this hard disk image. And also, any way to prevent this in future? One of my hosts that I need to work with is pretty unstable and tends to crash from time to time. I wouldn't like to go through this again.
virtualbox virtual-machine
asked Jul 14 '15 at 7:40
SiliconMindSiliconMind
3064922
add a comment |
I suffered host crash when running guest OS with VirtualBox. Now the VM won't start and complain that:
Could not open them medium '[file.vmdk]` VMDK: inconsistency between
grain table and backup grain table in '[file.vmdk]'
(VERR_VD_VMDK_INVALID_HEADER).
VD: error VERR_VD_VMDK_INVALID_HEADER
opening image file '[file.vmdk]' (VERR_VD_VMDK_INVALID_HEADER)
All I actually need is to get some files from this hard disk image. And also, any way to prevent this in future? One of my hosts that I need to work with is pretty unstable and tends to crash from time to time. I wouldn't like to go through this again.
virtualbox virtual-machine
asked Jul 14 '15 at 7:40
SiliconMindSiliconMind
3064922
I suffered host crash when running guest OS with VirtualBox. Now the VM won't start and complain that:
Could not open them medium '[file.vmdk]` VMDK: inconsistency between
grain table and backup grain table in '[file.vmdk]'
(VERR_VD_VMDK_INVALID_HEADER).
VD: error VERR_VD_VMDK_INVALID_HEADER
opening image file '[file.vmdk]' (VERR_VD_VMDK_INVALID_HEADER)
All I actually need is to get some files from this hard disk image. And also, any way to prevent this in future? One of my hosts that I need to work with is pretty unstable and tends to crash from time to time. I wouldn't like to go through this again.
virtualbox virtual-machine
virtualbox virtual-machine
asked Jul 14 '15 at 7:40
SiliconMindSiliconMind
3064922
asked Jul 14 '15 at 7:40
SiliconMindSiliconMind
3064922
asked Jul 14 '15 at 7:40
SiliconMindSiliconMind
3064922
asked Jul 14 '15 at 7:40
SiliconMindSiliconMind
3064922
asked Jul 14 '15 at 7:40
SiliconMindSiliconMind
3064922
3064922
add a comment |
add a comment |
5 Answers
5
active
oldest
votes
Download the VDD kit from VMWare from here and run the following command:
vmware-vdiskmanager -R <Path to vmdk file>
This repaired my corrupt header which was caused by a power outage while the VM was running in Virtualbox.
answered Oct 16 '15 at 12:56
PierrickPierrick
12115
I have the same error after a hard reset but after running the repair command I get "No errors were found on the virtual disk" Do you have any other ideas how to fix this? Thanks
– user95227
Sep 21 '16 at 14:20
add a comment |
I had the same issue today. Solved it using vdiskmanager (Download link available in attachment section) and follow the instructions here.
Regards,
HBK
answered Nov 4 '15 at 9:40
HBKHBK
19113
When I run1023856-vmware-vdiskmanager-linux.7.0.1 -Ron the corrupt VMDK file, it doesn't return anything, but when I run it on the non-corrupt ones, it returns, saying they are not corrupt. This utility didn't fix my corrupt VMDK.
– Geremia
Oct 5 '17 at 14:53
Doesn't run on 64-bit Linux OS. The link gives a 32-bit LSB executable.
– doughgle
Oct 18 '17 at 13:46
add a comment |
For repair corrupted.vhd file use
%Program Files%OracleVirtualBoxVBoxManage.exe internalcommands repairhd "corrupted.vhd"
answered Oct 16 '16 at 11:43
mimoprohodilmimoprohodil
211
Did not work for me, while thevdiskmanagerdid the trick
– Raffi
Jun 13 '17 at 18:13
I had to use as is aheadVBoxManage.exe internalcommands repairhd corrupted_vdi_with_path.vdi -format VDIto be able to use the above command. However, this just lead to further info for the case to me - "..Error code VERR_VD_IMAGE_REPAIR_IMPOSSIBLE.." (Command references here - virtualbox.org/manual/ch08.html#vboxmanage-list)
– parasrish
Apr 9 '18 at 4:22
add a comment |
I managed to fix the corrupt header using Virtual Disk Development Kit from vmware. This post about mounting disk image led me to the vddk.
vmware-manager.exe allows you to fix the image file. It worked for me, as I was able to launch the VM, however files I needed were corrupt anyway.
answered Jul 14 '15 at 11:03
SiliconMindSiliconMind
3064922
add a comment |
A much easier way to fix this error that required no external tools.
From the main window of the Oracle VM VirtualBox Manager, select the VM that won't start. Click on Snapshots in upper right. Select the second-last entry (since presumably the last one is corrupted, and the previous one is healthy). Right-click on it and choose Restore (I didn't see a point to creating a snapshot of the current VM state, since it's buggered). Done
answered Jan 15 at 15:59
Brent ThompsonBrent Thompson
1
add a comment |
protected by Community♦ Jan 15 at 17:10
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
Download the VDD kit from VMWare from here and run the following command:
vmware-vdiskmanager -R <Path to vmdk file>
This repaired my corrupt header which was caused by a power outage while the VM was running in Virtualbox.
answered Oct 16 '15 at 12:56
PierrickPierrick
12115
I have the same error after a hard reset but after running the repair command I get "No errors were found on the virtual disk" Do you have any other ideas how to fix this? Thanks
– user95227
Sep 21 '16 at 14:20
add a comment |
Download the VDD kit from VMWare from here and run the following command:
vmware-vdiskmanager -R <Path to vmdk file>
This repaired my corrupt header which was caused by a power outage while the VM was running in Virtualbox.
answered Oct 16 '15 at 12:56
PierrickPierrick
12115
I have the same error after a hard reset but after running the repair command I get "No errors were found on the virtual disk" Do you have any other ideas how to fix this? Thanks
– user95227
Sep 21 '16 at 14:20
add a comment |
Download the VDD kit from VMWare from here and run the following command:
vmware-vdiskmanager -R <Path to vmdk file>
This repaired my corrupt header which was caused by a power outage while the VM was running in Virtualbox.
answered Oct 16 '15 at 12:56
PierrickPierrick
12115
Download the VDD kit from VMWare from here and run the following command:
vmware-vdiskmanager -R <Path to vmdk file>
This repaired my corrupt header which was caused by a power outage while the VM was running in Virtualbox.
answered Oct 16 '15 at 12:56
PierrickPierrick
12115
answered Oct 16 '15 at 12:56
PierrickPierrick
12115
answered Oct 16 '15 at 12:56
PierrickPierrick
12115
answered Oct 16 '15 at 12:56
PierrickPierrick
12115
12115
I have the same error after a hard reset but after running the repair command I get "No errors were found on the virtual disk" Do you have any other ideas how to fix this? Thanks
– user95227
Sep 21 '16 at 14:20
add a comment |
I have the same error after a hard reset but after running the repair command I get "No errors were found on the virtual disk" Do you have any other ideas how to fix this? Thanks
– user95227
Sep 21 '16 at 14:20
I have the same error after a hard reset but after running the repair command I get "No errors were found on the virtual disk" Do you have any other ideas how to fix this? Thanks
– user95227
Sep 21 '16 at 14:20
I have the same error after a hard reset but after running the repair command I get "No errors were found on the virtual disk" Do you have any other ideas how to fix this? Thanks
– user95227
Sep 21 '16 at 14:20
add a comment |
I had the same issue today. Solved it using vdiskmanager (Download link available in attachment section) and follow the instructions here.
Regards,
HBK
answered Nov 4 '15 at 9:40
HBKHBK
19113
When I run1023856-vmware-vdiskmanager-linux.7.0.1 -Ron the corrupt VMDK file, it doesn't return anything, but when I run it on the non-corrupt ones, it returns, saying they are not corrupt. This utility didn't fix my corrupt VMDK.
– Geremia
Oct 5 '17 at 14:53
Doesn't run on 64-bit Linux OS. The link gives a 32-bit LSB executable.
– doughgle
Oct 18 '17 at 13:46
add a comment |
I had the same issue today. Solved it using vdiskmanager (Download link available in attachment section) and follow the instructions here.
Regards,
HBK
answered Nov 4 '15 at 9:40
HBKHBK
19113
When I run1023856-vmware-vdiskmanager-linux.7.0.1 -Ron the corrupt VMDK file, it doesn't return anything, but when I run it on the non-corrupt ones, it returns, saying they are not corrupt. This utility didn't fix my corrupt VMDK.
– Geremia
Oct 5 '17 at 14:53
Doesn't run on 64-bit Linux OS. The link gives a 32-bit LSB executable.
– doughgle
Oct 18 '17 at 13:46
add a comment |
I had the same issue today. Solved it using vdiskmanager (Download link available in attachment section) and follow the instructions here.
Regards,
HBK
answered Nov 4 '15 at 9:40
HBKHBK
19113
I had the same issue today. Solved it using vdiskmanager (Download link available in attachment section) and follow the instructions here.
Regards,
HBK
answered Nov 4 '15 at 9:40
HBKHBK
19113
answered Nov 4 '15 at 9:40
HBKHBK
19113
answered Nov 4 '15 at 9:40
HBKHBK
19113
answered Nov 4 '15 at 9:40
HBKHBK
19113
19113
When I run1023856-vmware-vdiskmanager-linux.7.0.1 -Ron the corrupt VMDK file, it doesn't return anything, but when I run it on the non-corrupt ones, it returns, saying they are not corrupt. This utility didn't fix my corrupt VMDK.
– Geremia
Oct 5 '17 at 14:53
Doesn't run on 64-bit Linux OS. The link gives a 32-bit LSB executable.
– doughgle
Oct 18 '17 at 13:46
add a comment |
When I run1023856-vmware-vdiskmanager-linux.7.0.1 -Ron the corrupt VMDK file, it doesn't return anything, but when I run it on the non-corrupt ones, it returns, saying they are not corrupt. This utility didn't fix my corrupt VMDK.
– Geremia
Oct 5 '17 at 14:53
Doesn't run on 64-bit Linux OS. The link gives a 32-bit LSB executable.
– doughgle
Oct 18 '17 at 13:46
When I run
1023856-vmware-vdiskmanager-linux.7.0.1 -R on the corrupt VMDK file, it doesn't return anything, but when I run it on the non-corrupt ones, it returns, saying they are not corrupt. This utility didn't fix my corrupt VMDK.– Geremia
Oct 5 '17 at 14:53
When I run
1023856-vmware-vdiskmanager-linux.7.0.1 -R on the corrupt VMDK file, it doesn't return anything, but when I run it on the non-corrupt ones, it returns, saying they are not corrupt. This utility didn't fix my corrupt VMDK.– Geremia
Oct 5 '17 at 14:53
Doesn't run on 64-bit Linux OS. The link gives a 32-bit LSB executable.
– doughgle
Oct 18 '17 at 13:46
Doesn't run on 64-bit Linux OS. The link gives a 32-bit LSB executable.
– doughgle
Oct 18 '17 at 13:46
add a comment |
For repair corrupted.vhd file use
%Program Files%OracleVirtualBoxVBoxManage.exe internalcommands repairhd "corrupted.vhd"
answered Oct 16 '16 at 11:43
mimoprohodilmimoprohodil
211
Did not work for me, while thevdiskmanagerdid the trick
– Raffi
Jun 13 '17 at 18:13
I had to use as is aheadVBoxManage.exe internalcommands repairhd corrupted_vdi_with_path.vdi -format VDIto be able to use the above command. However, this just lead to further info for the case to me - "..Error code VERR_VD_IMAGE_REPAIR_IMPOSSIBLE.." (Command references here - virtualbox.org/manual/ch08.html#vboxmanage-list)
– parasrish
Apr 9 '18 at 4:22
add a comment |
For repair corrupted.vhd file use
%Program Files%OracleVirtualBoxVBoxManage.exe internalcommands repairhd "corrupted.vhd"
answered Oct 16 '16 at 11:43
mimoprohodilmimoprohodil
211
Did not work for me, while thevdiskmanagerdid the trick
– Raffi
Jun 13 '17 at 18:13
I had to use as is aheadVBoxManage.exe internalcommands repairhd corrupted_vdi_with_path.vdi -format VDIto be able to use the above command. However, this just lead to further info for the case to me - "..Error code VERR_VD_IMAGE_REPAIR_IMPOSSIBLE.." (Command references here - virtualbox.org/manual/ch08.html#vboxmanage-list)
– parasrish
Apr 9 '18 at 4:22
add a comment |
For repair corrupted.vhd file use
%Program Files%OracleVirtualBoxVBoxManage.exe internalcommands repairhd "corrupted.vhd"
answered Oct 16 '16 at 11:43
mimoprohodilmimoprohodil
211
For repair corrupted.vhd file use
%Program Files%OracleVirtualBoxVBoxManage.exe internalcommands repairhd "corrupted.vhd"
answered Oct 16 '16 at 11:43
mimoprohodilmimoprohodil
211
answered Oct 16 '16 at 11:43
mimoprohodilmimoprohodil
211
answered Oct 16 '16 at 11:43
mimoprohodilmimoprohodil
211
answered Oct 16 '16 at 11:43
mimoprohodilmimoprohodil
211
211
Did not work for me, while thevdiskmanagerdid the trick
– Raffi
Jun 13 '17 at 18:13
I had to use as is aheadVBoxManage.exe internalcommands repairhd corrupted_vdi_with_path.vdi -format VDIto be able to use the above command. However, this just lead to further info for the case to me - "..Error code VERR_VD_IMAGE_REPAIR_IMPOSSIBLE.." (Command references here - virtualbox.org/manual/ch08.html#vboxmanage-list)
– parasrish
Apr 9 '18 at 4:22
add a comment |
Did not work for me, while thevdiskmanagerdid the trick
– Raffi
Jun 13 '17 at 18:13
I had to use as is aheadVBoxManage.exe internalcommands repairhd corrupted_vdi_with_path.vdi -format VDIto be able to use the above command. However, this just lead to further info for the case to me - "..Error code VERR_VD_IMAGE_REPAIR_IMPOSSIBLE.." (Command references here - virtualbox.org/manual/ch08.html#vboxmanage-list)
– parasrish
Apr 9 '18 at 4:22
Did not work for me, while the
vdiskmanager did the trick– Raffi
Jun 13 '17 at 18:13
Did not work for me, while the
vdiskmanager did the trick– Raffi
Jun 13 '17 at 18:13
I had to use as is ahead
VBoxManage.exe internalcommands repairhd corrupted_vdi_with_path.vdi -format VDI to be able to use the above command. However, this just lead to further info for the case to me - "..Error code VERR_VD_IMAGE_REPAIR_IMPOSSIBLE.." (Command references here - virtualbox.org/manual/ch08.html#vboxmanage-list)– parasrish
Apr 9 '18 at 4:22
I had to use as is ahead
VBoxManage.exe internalcommands repairhd corrupted_vdi_with_path.vdi -format VDI to be able to use the above command. However, this just lead to further info for the case to me - "..Error code VERR_VD_IMAGE_REPAIR_IMPOSSIBLE.." (Command references here - virtualbox.org/manual/ch08.html#vboxmanage-list)– parasrish
Apr 9 '18 at 4:22
add a comment |
I managed to fix the corrupt header using Virtual Disk Development Kit from vmware. This post about mounting disk image led me to the vddk.
vmware-manager.exe allows you to fix the image file. It worked for me, as I was able to launch the VM, however files I needed were corrupt anyway.
answered Jul 14 '15 at 11:03
SiliconMindSiliconMind
3064922
add a comment |
I managed to fix the corrupt header using Virtual Disk Development Kit from vmware. This post about mounting disk image led me to the vddk.
vmware-manager.exe allows you to fix the image file. It worked for me, as I was able to launch the VM, however files I needed were corrupt anyway.
answered Jul 14 '15 at 11:03
SiliconMindSiliconMind
3064922
add a comment |
I managed to fix the corrupt header using Virtual Disk Development Kit from vmware. This post about mounting disk image led me to the vddk.
vmware-manager.exe allows you to fix the image file. It worked for me, as I was able to launch the VM, however files I needed were corrupt anyway.
answered Jul 14 '15 at 11:03
SiliconMindSiliconMind
3064922
I managed to fix the corrupt header using Virtual Disk Development Kit from vmware. This post about mounting disk image led me to the vddk.
vmware-manager.exe allows you to fix the image file. It worked for me, as I was able to launch the VM, however files I needed were corrupt anyway.
answered Jul 14 '15 at 11:03
SiliconMindSiliconMind
3064922
answered Jul 14 '15 at 11:03
SiliconMindSiliconMind
3064922
answered Jul 14 '15 at 11:03
SiliconMindSiliconMind
3064922
answered Jul 14 '15 at 11:03
SiliconMindSiliconMind
3064922
3064922
add a comment |
add a comment |
A much easier way to fix this error that required no external tools.
From the main window of the Oracle VM VirtualBox Manager, select the VM that won't start. Click on Snapshots in upper right. Select the second-last entry (since presumably the last one is corrupted, and the previous one is healthy). Right-click on it and choose Restore (I didn't see a point to creating a snapshot of the current VM state, since it's buggered). Done
answered Jan 15 at 15:59
Brent ThompsonBrent Thompson
1
add a comment |
A much easier way to fix this error that required no external tools.
From the main window of the Oracle VM VirtualBox Manager, select the VM that won't start. Click on Snapshots in upper right. Select the second-last entry (since presumably the last one is corrupted, and the previous one is healthy). Right-click on it and choose Restore (I didn't see a point to creating a snapshot of the current VM state, since it's buggered). Done
answered Jan 15 at 15:59
Brent ThompsonBrent Thompson
1
add a comment |
A much easier way to fix this error that required no external tools.
From the main window of the Oracle VM VirtualBox Manager, select the VM that won't start. Click on Snapshots in upper right. Select the second-last entry (since presumably the last one is corrupted, and the previous one is healthy). Right-click on it and choose Restore (I didn't see a point to creating a snapshot of the current VM state, since it's buggered). Done
answered Jan 15 at 15:59
Brent ThompsonBrent Thompson
1
A much easier way to fix this error that required no external tools.
From the main window of the Oracle VM VirtualBox Manager, select the VM that won't start. Click on Snapshots in upper right. Select the second-last entry (since presumably the last one is corrupted, and the previous one is healthy). Right-click on it and choose Restore (I didn't see a point to creating a snapshot of the current VM state, since it's buggered). Done
answered Jan 15 at 15:59
Brent ThompsonBrent Thompson
1
answered Jan 15 at 15:59
Brent ThompsonBrent Thompson
1
answered Jan 15 at 15:59
Brent ThompsonBrent Thompson
1
answered Jan 15 at 15:59
Brent ThompsonBrent Thompson
1
1
add a comment |
add a comment |
protected by Community♦ Jan 15 at 17:10
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
