hello where are the files you need to keep? on the directory on your machine ? then you can copy them to ensure they wont be deleted or overwritten
if the files where local somewhere in the vm, try to open virtualbox gui, and start the VM once done, check over the gui console to login and check if the files are still there, if yes, copy them vagrant is to create disposable projects, depending on how this is configured, the files may be on the host or the vm the best is treat the VM as disposable and try to get some persistence on your projects either by copy of the files. or control version. good luck alvaro On Wed, Jan 1, 2020 at 6:07 PM kranai <[email protected]> wrote: > Hi > > Recently I accidentally deleted some file in one of the virtual box > directory because I saw a message that it could not rename a certain file > because it did not clean during the last shutdown. But when I removed it > and started "vagrant up" it went through and but when I tried to access my > CMS wordpress site on my localhost machine at 192.168.33.10 it gave me a > panel that shows it was going re-install my wordpress even though my > wordpress files are intact. > > I was afraid to proceed because I fear that all my work done on my > website/themes in my public folder on my laptop might get overwritten and I > will lose a lot of work done. > > Can anyone please let me know how I can get back on track again: Below is > the message I see when I do "vagrant up". I am running windows 10 (64bit). > > $ vagrant up > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'scotch/box'... > ==> default: Matching MAC address for NAT networking... > ==> default: Checking if box 'scotch/box' version '3.5' is up to date... > ==> default: Setting the name of the VM: WPDistillery-Demo > The name of your virtual machine couldn't be set because VirtualBox > is reporting another VM with that name already exists. Most of the > time, this is because of an error with VirtualBox not cleaning up > properly. To fix this, verify that no VMs with that name do exist > (by opening the VirtualBox GUI). If they don't, then look at the > folder in the error message from VirtualBox below and remove it > if there isn't any information you need in there. > (P.s. I checked in my VB GUI there was no VMs with the same name) > VirtualBox error: > > VBoxManage.exe: error: Could not rename the directory > 'C:\Users\user\VirtualBox > VMs\build-stuff_default_1496193404567_88071_1577851854867_22901' to > 'C:\Users\user\VirtualBox VMs\WPDistillery-Demo' to save the settings file > (VERR_ALREADY_EXISTS) > VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component > SessionMachine, interface IMachine, callee IUnknown > VBoxManage.exe: error: Context: "SaveSettings()" at line 3206 of file > VBoxManageModifyVM.cpp > > I submitted the above issue on *Vitrual Box forum* and below is the > response : > *"Vagrant does unexpected things with Virtualbox, so we don't support it > here. You'll need to try Vagrant's forums."* > > I ping ponging now between vagrant and virtual box forums... > > can anybody help me get on track again without losing my work? > > Best Rgds > Help much appreciated > > -- > This mailing list is governed under the HashiCorp Community Guidelines - > https://www.hashicorp.com/community-guidelines.html. Behavior in > violation of those guidelines may result in your removal from this mailing > list. > > GitHub Issues: https://github.com/mitchellh/vagrant/issues > IRC: #vagrant on Freenode > --- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/vagrant-up/7e629441-82c2-41c2-ad1b-1a065a7fa146%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/7e629441-82c2-41c2-ad1b-1a065a7fa146%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Alvaro -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezf%3DKaxg5Hcb%3DxnH4UN%3DkB2ZD2ykaAXi2jLVCs7Z5p_Sw%40mail.gmail.com.
