Vagrant corrupted index file C:\Users\USERNAME\.vagrant.d/data/machine-index/index

virtual-machine vagrant windows-8.1
Thomas Venturini picture Thomas Venturini · Jul 23, 2014 · Viewed 16.5k times · Source

My Windows 8.1 just crashed. Now I have some files on my dist that are corrupted. This includes my vagrant machine index (Not shure if the naming is right but I know that it is this file -> C:\Users\USERNAME.vagrant.d/data/machine-index/index).

So There is a lot of binary or hexdecimal stuff in there (Again not shure because I don't deal with this stuff usualy so correct me if I'm wrong!) And Vagrant spits out the following message if I try to start everything after boot.

vagrant up returns this

The machine index which stores all required information about
running Vagrant environments has become corrupt. This is usually
caused by external tampering of the Vagrant data folder.

Vagrant cannot manage any Vagrant environments if the index is
corrupt. Please attempt to manually correct it. If you are unable
to manually correct it, then remove the data file at the path below.
This will leave all existing Vagrant environments "orphaned" and
they'll have to be destroyed manually.

Path: C:/Users/Username/.vagrant.d/data/machine-index/index

Answer

Jukka Puranen picture Jukka Puranen · Aug 10, 2014

Same thing happened to me. So I just deleted the index file and the .lock file from the machine-index folder to get Vagrant working again.

Related questions

SSH to Vagrant box in Windows?

I'm using Vagrant to start a VirtualBox VM in windows. In other platforms, I can just $ vagrant ssh to connect to the VM. How do i connect to this Vagrant box in windows? The way suggested in Vagrant documentation to …

Read More
Where does Vagrant download its .box files to?

What happens to the .box file after the following command is executed? vagrant box add lucid32 http://files.vagrantup.com/lucid32.box I can't find the lucid32.box file on the file system after download has completed.

Read More
VBoxManage: error: Failed to create the host-only adapter

I am running vagrant 1.4 and virtual box 4.3 on fedora 17 machine. When I do "vagrant up", I get this error: Bringing machine 'default' up with 'virtualbox' provider... [default] Clearing any previously set forwarded ports... [default] Clearing any previously set network interfaces... …

Read More