Quantcast
Channel: VMware Communities : Discussion List - ESXi
Viewing all articles
Browse latest Browse all 8132

Can't unmount datastore in ESXi

$
0
0

I recently installed ESXi 6.5 on a server.

 

I am using the ESXi HTML client.

 

I set up a datastore which now needs to be deleted.

 

No virtual machines have been installed on the host.

 

When I try to unmount the datastore, I get the error:

"Failed - the resource "Datastore Name: ..." is in use.

"Cannot unmount volume "Datastore Name: ..." because the file system in busy."

 

I deleted all the folders, except one, in the datastore. Exception: .sdd.sf ; I can't delete this folder.

 

In "Advanced settings" under the "System" tab under "Manage" under "Host",

I changed the path for the Key "ScratchConfig.CurrentScratchLocation" to a new folder that

I created in the datastore I am trying to delete - this is an error.  Now I can't delete THAT folder (see next paragraph).

 

I then tried to change the path again for the same Key "ScratchConfig.CurrentScratchLocation" to a folder I created in /tmp, and get the error "Failed - A specified parameter was not correct."  I then right click on the Key and select "Reset to default" and get the error "Failed - A specified parameter was not correct."

 

I have googled this problem, and every solution, each of which has several steps, includes a step that doesn't work.

One of the solutions includes over a hundred lines of PowerShell code (I haven't tried it). I've tried several others include EsxCli commands that fail on the critical step.

 

Given the simplicity of the task, it may be evident that this situation, which has now been ongoing for nearly two days, is devolving into a clown show.

It seems I'm eventually blocked no matter what path I take.

 

Is there a solution to this problem? I guess I could reinstall ESXi, but this isn't MS. Thanks for any help.


Viewing all articles
Browse latest Browse all 8132

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>