Vagrant: Can't vagrant up always with these error?

Created on 5 Sep 2018 · 8Comments · Source: hashicorp/vagrant

Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting \?\C:\Users\Administrator.vagrant.d\boxes\laravel-VAGRANTSLASH-homestead\6.1.0\virtualbox\box.ovf...
OK.
0%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage.exe: error: Appliance import failed
VBoxManage.exe: error: Could not create the imported medium 'C:\Users\Administrator\VirtualBox VMs\ubuntu-18.04-amd64_1528981308408_40115\ubuntu-18.04-amd64-disk001.vmdk'.
VBoxManage.exe: error: VMDK: Compressed image is corrupted '\?\C:\Users\Administrator.vagrant.d\boxes\laravel-VAGRANTSLASH-homestead\6.1.0\virtualbox\ubuntu-18.04-amd64-disk001.vmdk' (VERR_ZIP_CORRUPTED)
VBoxManage.exe: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component ApplianceWrap, interface IAppliance
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleImportAppliance(struct HandlerArg *)" at line 886 of file VBoxManageAppliance.cpp

waiting-reply

Source

honkkki

Most helpful comment

@cbj4074 Thanks bro anyway i solved it by destroying the box and reinstalling it ...

paksniper on 11 Nov 2019

🎉1 😄1

All 8 comments

What is the SHA1 hash of the disk image file, C:\Users\Administrator\.vagrant.d\boxes\laravel-VAGRANTSLASH-homestead\6.1.0\virtualbox\ubuntu-18.04-amd64-disk001.vmdk?

If it's not 5851150903A809CC3C09EB80F35C0150D2085E08, then it appears that your download was corrupted in some capacity. Have you tired re-downloading it?

cbj4074 on 5 Sep 2018

👍1

Hi @honkkki - yes, I recommend deleting the box with vagrant box remove, then try to re-add it and see if that fixes it.

briancain on 5 Sep 2018

👍1

Thx bro! I will try to solve the problem.

honkkki on 5 Sep 2018

Hey there,

I am going to close this due to lack of response. If this is still occurring, please open a new issue and follow the provided issue template that appears when you click the "New Issue" button. This will help us in getting a reproduction and fix. Thanks!

briancain on 8 Oct 2018

hi i stuck in this problem as well

paksniper on 8 Nov 2019

@paksniper Then I would do as @briancain suggested above: open a new issue, fill-out the template, and submit.

cbj4074 on 11 Nov 2019

@cbj4074 Thanks bro anyway i solved it by destroying the box and reinstalling it ...

paksniper on 11 Nov 2019

🎉1 😄1

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.