Re-post of Steve Graham's Question: Error installing OSEHRA VistA

I am running a 16 GB, 64-bit version of Windows 10, and have gotten the same error twice while trying to install OSHERA VistA per https://www.osehra.org/content/how-setup-osehra-vista-development-virtual-machine-vm-0

The log in part shows:

Unmounting Virtualbox Guest Additions ISO from: /mnt
==> OSEHRA VistA - Ubuntu: Checking for guest additions in VM...
    OSEHRA VistA - Ubuntu: The guest additions on this VM do not match the installed version of
    OSEHRA VistA - Ubuntu: VirtualBox! In most cases this is fine, but in rare cases it can
    OSEHRA VistA - Ubuntu: prevent things such as shared folders from working properly. If you see
    OSEHRA VistA - Ubuntu: shared folder errors, please make sure the guest additions within the
    OSEHRA VistA - Ubuntu: virtual machine match the version of VirtualBox you have installed on
    OSEHRA VistA - Ubuntu: your host and reload your VM.
    OSEHRA VistA - Ubuntu:
    OSEHRA VistA - Ubuntu: Guest Additions Version: 5.1.24
    OSEHRA VistA - Ubuntu: VirtualBox Version: 5.2
==> OSEHRA VistA - Ubuntu: Mounting shared folders...
    OSEHRA VistA - Ubuntu: /vagrant => C:/Users/Steve/Development/VistA/Scripts/Install
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:

: No such device

 

In between attempts, I uninstalled/re-installed Vagrant.  Any help would be appreciated.

I have used and appreciated this version of VistA.  Would love to do so again.

Thanks, Steve Graham

 

like0

Comments

Hi Steve,

Joseph Snyder's picture

Hi Steve,

Thanks for keeping us appraised of your trials and tribulations with the Vagrant scripts.  I am sorry to say that I haven't been able to replicate your problem.  I just installed VirtualBox 5.2.12 and Vagrant 2.1.1 onto my 64bit Windows 10 machine and the mounting of the directory was successful in two of two attempts to generate the VM.

Can you try to re-download the box as a part of a new build?  You can remove the old image with the command:

vagrant box remove "OSEHRA Ubuntu 16.04 Image"

and destroy the old Vagrant machine as well using vagrant destroy.  Once that is removed, please run another vagrant up to see if the error is found with this freshly downloaded version.  I'll be trying to see if there are other Window 10 problems in the mean time

Thanks!

like0

Re-post of Steve Graham's Question: Error installing OSEHRA...

Sam Habiel's picture
This is a very common error. Just google for the answer. e.g. https://github.com/hashicorp/vagrant/issues/8303.



--Sam Habiel, Pharm.D.

Technical Fellow

Open Source Electronic Health Records Alliance (OSEHRA)

Cell: 206-353-1681



On Mon, Jun 11, 2018 at 4:57 PM, Joseph Snyder <snyderj@osehra.org> wrote:

Hi Steve,

Thanks for keeping us appraised of your trials and tribulations with the Vagrant scripts.  I am sorry to say that I haven't been able to replicate your problem.  I just installed VirtualBox 5.2.12 and Vagrant 2.1.1 onto my 64bit Windows 10 machine and the mounting of the directory was successful in two of two attempts to generate the VM.

Can you try to re-download the box as a part of a new build?  You can remove the old image with the command:

vagrant box remove "OSEHRA Ubuntu 16.04 Image"

and destroy the old Vagrant machine as well using vagrant destroy.  Once that is removed, please run another vagrant up to see if the error is found with this freshly downloaded version.  I'll be trying to see if there are other Window 10 problems in the mean time

Thanks!


like0