Impossible to restart VM after crash

[Student_fr]

It's all in the title, for no reason Mac OS crashed while one of my vm was running. After turning my computer back on again, I can't turn this vm on again, the following error is displayed.

Code: Select all

Could not open the medium '/Users/my_login/VirtualBox VMs/Kali-Linux-2018.3-vbox-amd64/Kali-Linux-2018.3-vbox-amd64-disk1.vmdk'.
VMDK: inconsistency between grain table and backup grain table in '/Users/my_login/VirtualBox VMs/Kali-Linux-2018.3-vbox-amd64/Kali-Linux-2018.3-vbox-amd64-disk1.vmdk' (VERR_VD_VMDK_INVALID_HEADER).
VD: error VERR_VD_VMDK_INVALID_HEADER opening image file '/Users/my_login/VirtualBox VMs/Kali-Linux-2018.3-vbox-amd64/Kali-Linux-2018.3-vbox-amd64-disk1.vmdk' (VERR_VD_VMDK_INVALID_HEADER).

I tried several things like disabling NAT, then renamed some prev files but without a solution. Thank you in advance for your help

[andyp73]

I tried several things like disabling NAT, then renamed some prev files but without a solution.

The crash has caused a corruption of the .vmdk disk image file. No amount of tinkering with network or other unrelated settings is going to fix that.

The vmdk isn't a native VirtualBox disk image format (.vdi). You will need to download the command line tools from VMWare and run the vmware-vdiskmanager utility to repair the .vmdk file and then VirtualBox should be able to load it again.

I have never used the tool so don't know if there is a macOS version of it or whether you will have to copy the broken .vmdk file to a Windows / Linux machine and use the tool there and then copy the repaired file back again.

-Andy.

[Student_fr]

All right, thanks for your answer, I'll look this way then However if some of them have software to recommend for mac I'm a taker, apart from setting up a vm windows I don't have any on hand