virtualbox.org

After installing an extension pack my running VM starting responding late to my commands etc. so I closed and tried to reopen but received the error "failed to open a session for the virtual machine". In the storage part of the VM it says " Could not open the medium "..... .vdi". VDI: error reading pre-header in "....vdi" (VERR_IO_CRC). VD: error VERR_VD_VDI_INVALID_HEADER opening image file ".......vi" (VER_VD_VDI_INVALID_HEADER").

I have seen some solutions about copying the first 512 bytes of a new vdi to the corrupted one and editing them. I am not sure how to do that with a hexeditor too. My file size is 13,160,824,832 bytes.
Helps appreciated.

Mpack's CloneVDI has an automatic header fixer, if the disk file can be fixed.

If CloneVDI cannot fix the file, you'll have to restore from a backup.

shameless8 wrote:After installing an extension pack my running VM starting responding late to my commands etc.

Not quite sure myself how installing the Extension Pack could cause trouble with the VM. But, hey, it's a computer, anything is possible. Could also be something else.

If you get the disk file fixed, Start the VM from full power off, not save-state. Run until you see the problem happen, then shut down the VM from within the VM OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Please right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.