On Ubuntu 16.04.3 I can no longer run VirtualBox (and hence Vagrant). Running any vagrant command results in:

/usr/lib/ruby/vendor_ruby/vagrant/machine_index.rb:293:in `read': Input/output error @ rb_sysopen - /home/sillyinventor/.vagrant.d/data/machine-index/index (Errno::EIO)
    from /usr/lib/ruby/vendor_ruby/vagrant/machine_index.rb:293:in `read'
    from /usr/lib/ruby/vendor_ruby/vagrant/machine_index.rb:293:in `unlocked_reload'
    from /usr/lib/ruby/vendor_ruby/vagrant/machine_index.rb:53:in `block in initialize'
    from /usr/lib/ruby/vendor_ruby/vagrant/machine_index.rb:323:in `block in with_index_lock'
    from /usr/lib/ruby/vendor_ruby/vagrant/machine_index.rb:321:in `open'
    from /usr/lib/ruby/vendor_ruby/vagrant/machine_index.rb:321:in `with_index_lock'
    from /usr/lib/ruby/vendor_ruby/vagrant/machine_index.rb:52:in `initialize'
    from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:637:in `new'
    from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:637:in `machine_index'
    from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:180:in `block in action_runner'
    from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:33:in `run'
    from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:439:in `hook'
    from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:688:in `unload'
    from /usr/bin/vagrant:176:in `ensure in <main>'
    from /usr/bin/vagrant:176:in `<main>'

Running VirtualBox from command line results in a complete system lockup at waiting for power on (including sys rq). You can’t run VirtualBox from TTY for obvious reasons, and the lockup forces a hard shutdown (so no log).

I have checked the BIOS, and virtualization is enabled. There is plenty of harddrive space. I have uninstalled and reinstalled (in case there is a corrupt file). I have checked the syslog, but at the time where it crashed there are only bad characters. I have checked hard drive quality with smart control, and all seems well. The ~/.vagrant.ddata/machine-index/index file seems to be strangely unreadable.

I did install updates (apt-get update and dist-upgrade), may be related to that. Ideas are appreciated.

  • Not useful info to me, but perhaps it'll mean something to you that it just prints the box character (missing value) repeatedly. – SillyInventor Jan 17 '18 at 18:50
  • ... that seems very improbable to me. However, I will run some tests. – SillyInventor Jan 19 '18 at 22:16
  • Yeah, the system is fine. – SillyInventor Jan 22 '18 at 14:36
  • Can you view the contents of ~/.vagrant.d/data/machine-index/index? The reason I ask is this stuff is juts a JSON formatted text file that defines your machines. It’s possible that is damaged and might be repairable by just humanly looking at it in a text editor and seeing what you can see. And if anything looks odd, just fix it. – Giacomo1968 Jan 22 '18 at 14:59
  • Hmm, I get an I/O error on viewing it, which is strange since the virtualbox is what crashes the computer... perhaps it's attempting to write there when it crashes? – SillyInventor Jan 22 '18 at 20:24

I removed ~/.vagrant.d/ and now it works.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.