StartHost failed, but will try again: creating host: create: creating: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe storageattach minikube --storagectl SATA --port 1 --device 0 --type hdd --medium C:\Users\kapils\.minikube\machines\minikube\disk.vmdk failed:

[sahuk1979]

What Happened?

PS C:\WINDOWS\system32> minikube start

• minikube v1.30.1 on Microsoft Windows 10 Enterprise 10.0.19044.2965 Build 19044.2965

• Automatically selected the virtualbox driver

• Starting control plane node minikube in cluster minikube

• Creating virtualbox VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...

• Deleting "minikube" in virtualbox ...
  ! StartHost failed, but will try again: creating host: create: creating: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe storageattach minikube --storagectl SATA --port 1 --device 0 --type hdd --medium C:\Users\kapils.minikube\machines\minikube\disk.vmdk failed:
  VBoxManage.exe: error: UUID {bc69d4c9-9de0-4e9a-b1a8-4e1c8bf7d1ee} of the medium 'C:\Users\kapils.minikube\machines\minikube\disk.vmdk' does not match the value {e21355a1-c237-40e5-afe2-94be16bf4459} stored in the media registry ('C:\Users\kapils.VirtualBox\VirtualBox.xml')
  VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MediumWrap, interface IMedium, callee IUnknown
  VBoxManage.exe: error: Context: "AttachDevice(Bstr(pszCtl).raw(), port, device, DeviceType_HardDisk, pMedium2Mount)" at line 785 of file VBoxManageStorageController.cpp

• Failed to start virtualbox VM. Running "minikube delete" may fix it: error loading existing host. Please try running [minikube delete], then run [minikube start] again: filestore "minikube": open C:\Users\kapils.minikube\machines\minikube\config.json: The system cannot find the file specified.

X Exiting due to GUEST_NOT_FOUND: Failed to start host: error loading existing host. Please try running [minikube delete], then run [minikube start] again: filestore "minikube": open C:\Users\kapils.minikube\machines\minikube\config.json: The system cannot find the file specified.

• Suggestion: minikube is missing files relating to your guest environment. This can be fixed by running 'minikube delete'
• Related issue: StartHost failed, but will try again: Error loading existing host. Please try running [minikube delete], then run [minikube start] again.: filestore "minikube": #9130

Attach the log file

X Exiting due to GUEST_NOT_FOUND: load: filestore "minikube": open C:\Users\kapils.minikube\machines\minikube\config.json: The system cannot find the file specified.

• Suggestion: minikube is missing files relating to your guest environment. This can be fixed by running 'minikube delete'
• Related issue: StartHost failed, but will try again: Error loading existing host. Please try running [minikube delete], then run [minikube start] again.: filestore "minikube": #9130

Operating System

Windows

Driver

VirtualBox

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.