![]() ![]() ![]() From here you should be able to add the datastore again without hassle. Read more After you create a Virtual Volumes datastore, it remains inaccessible. Read more You can use the vvol stats command in your ESXi host to track performance statistics. If it hasn’t disappeared refresh the view. You can use the esxcli storage vvol commands to troubleshoot your Virtual Volumes environment. Log out and check your vSphere Client’s storage tab – it should be gone there, too. You can also restart the management agents from the ESXi host console. To restart management agents on the ESXi 6.7 login into SSH as root and run the command below: services.sh restart. If you list the available datastores again it should be gone: Restart management agents in the ESXi host, or restart the ESXi host itself. This will return us to the prompt like so: ![]() Now to unmount the inaccessible datastore we run: That will list all of the datastores currently available to ESXi via NFS. The fix is quite easy – enable SSH access on your server (if you’re not sure how, see our guide here) and log into the root account. “Error: The resources ‘ip.of.data.store:/data/location’ is in use.Įrror stack: Call “HostDatastoreSystem.RemoveDatastore” for object “ha-datastoresystem” on ESXi “ip.of.your.esxi” failed. If you have found one of your datastores is greyed out/inactive one solution is to unmount it and add it again sometimes ESXi won’t let you do this, giving the following error message: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |