Yesterday my iMac crashed and I ended up having to a reinstall of MacOS. (all user data/files are retained - not reinstallation of anything needed) I believe vagrant/virtualbox was running at the time.
It was running the Trellis stack from https://roots.io
Now when I vagrant up
I get the following error:
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'bento/ubuntu-18.04' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Vagrant has detected a configuration issue which exposes a
==> default: vulnerability with the installed version of VirtualBox. The
==> default: current guest is configured to use an E1000 NIC type for a
==> default: network adapter which is vulnerable in this version of VirtualBox.
==> default: Ensure the guest is trusted to use this configuration or update
==> default: the NIC type using one of the methods below:
==> default:
==> default: https://www.vagrantup.com/docs/virtualbox/configuration.html#default-nic-type
==> default: https://www.vagrantup.com/docs/virtualbox/networking.html#virtualbox-nic-type
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "a6e2e43b-61b1-45a4-907f-27646982e7a1", "--type", "headless"]
Stderr: VBoxManage: error: Could not open the medium '/Users/dev/VirtualBox VMs/site.test/ubuntu-18.04-amd64-disk001.vmdk'.
VBoxManage: error: VMDK: descriptor does not start as expected in '/Users/gbwdev/VirtualBox VMs/site.test/ubuntu-18.04-amd64-disk001.vmdk' (VERR_VD_VMDK_INVALID_HEADER).
VBoxManage: error: VD: error VERR_VD_VMDK_INVALID_HEADER opening image file '/Users/dev/VirtualBox VMs/site.test/ubuntu-18.04-amd64-disk001.vmdk' (VERR_VD_VMDK_INVALID_HEADER)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MediumWrap, interface IMedium
Could anyone help me get this to work again? It has vital data on it, more specifically a mysql database within the VM instance.
What have I tried to fix this?
I've tried using the vmware-vdiskmanager
but I don't quite understand it.
vmware-vdiskmanager -r sourceDisk.vmdk destinationDisk.vmdk
-r
= repair, but I don't understand where I get a destination disk from if all I want to do is repair the only disk I have, the broken one I'm trying to vagrant up
with?
User contributions licensed under CC BY-SA 3.0