ホーム

I got a mount error when I vagrant up

Can not mount

box add, vagrantfile modified, vagrant up, I got a mount error. It seems that the virtual machine is running because it just failed to mount.

When I read the error log, it seems that there is no vbox file in the main point? vboxf is the configuration file of the virtual box. That, vboxf nothing why, vboxf can not mount! It is said

[sourcecode language="plain"]
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:

mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant

The error output from the command was:

mount: unknown filesystem type 'vboxsf'
[/sourcecode]

What is mount?

Well, at this point it was the level of what is mounting, so I checked it. Mount, for example, Linux has a root directory (/) as a vertex, tree structure of directory structure is not it?

/ Users / The name of my computer / Desktop. When thinking about increasing the number of external hard disks as a new memory personnel somewhere in the tree-shaped directory, what we do is called mounting. Did you understand? What?

So, what mount can be placed in vartualbox

Vartualbox mounting means to make it easy to communicate between the host OS and the guest OS. The following article was helpful.

this

this

What is vagrant-vbguest?

I read about below! And I understood. And at the same time, the mystery of deepening "I do not really know how to make vboxf mountable by matching the version of Guest Addition" has deepened.

Make it possible to mount by possibly filling up the difference between the os installed in the vartualbox 's box and the version of the hoso OS! That's the meaning!

Well, I can not do it in the end!

If you put the vagrant - vbguest plug - in, it will be updated according to the version of VirtualBox if the version of VirtualBox in your environment and the version of Guest Addition installed in Box are different.

Failure continued life

I came up with a new error and it could not be solved.

We will summarize the continuation in another article and put a link

Additional notes 2016-12-17

At a later date, once again vagrant up, it is a mystery why I was able to do it normally for some reason.

If it is true the following error log should have appeared, but why is not it?

[sourcecode language="plain"]

Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:

mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant

The error output from the command was:

/sbin/mount.vboxsf: mounting failed with the error: No such device

[/sourcecode]

After doing why once again I ran without any problems as below

[sourcecode language="plain"]

vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: [vagrant-hostsupdater] Checking for host entries
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: flag to force provisioning. Provisioners marked to run always will still run.

</pre>
</div>
</div>
<div class="code-frame" data-lang="text">
<div class="highlight">
<pre>[/sourcecode]
There is no problem with ssh connection, mystery is deepening.

[sourcecode language="plain"]
vagrant ssh
Last login: Fri Dec 16 03:51:18 2016 from 10.0.2.2
----------------------------------------------------------------
  CentOS 7.2.1511                             built 2016-01-04
----------------------------------------------------------------
[/sourcecode]
追記 2016-12-18

I did not solve it

I thought that I could solve it with vagrant up once, but it was useless.

It seems that the same error appears as vagrant restart

So, after all, I will put a solution on a different article

Pocket
LinkedIn にシェア



新規webサービスの開発の依頼ならoffテク⭐️

低コストで、Reactなどモダン言語での新規webサービス開発を承ります

-ホーム

Copyright© off , 2020 All Rights Reserved Powered by AFFINGER5.