- Advertisement -
HomeVirtualizationVMwareUnable to delete an "inaccessible" datastore

Unable to delete an "inaccessible" datastore

Problem:

Unable to delete an inaccessible datastore

I was switching my storage array, so I migrated the VMs from that old datastore/storage to a new datastore/storage.

The old datastore was shared by 3 ESXi 6.7 hosts, with no cluster. After migrating the VMs and unmount/delete the datastore, it was still presented in two of the ESXi hosts and was marked as Inaccessible. I am pretty sure that I did something wrong, but don’t know what.

Unable to delete an inaccessible datastore

Attempting a few times to delete the datastore keep popping up the error below:

Inaccessible datastore

I tried and check:

  • There was no VM or template allocated in the old datastore.
  • There was no files, snapshots or templates. In fact, the datastores show 0 B of capacity.
Inaccessible datastore
  • Storage I/O Control (SIOC) wasn’t enabled on the datastore.
  • Access via SSH to delete the datastore from there, but these two datastores were not listed.
  • This wasn’t an Orphaned Datastore, the Delete Datastore option wasn’t grayed out, it just didn’t work.
  • I tried more options. See resources.

Solution:

Yet another "simple" solution. Restart management agents in the ESXi host, or restart the ESXi host itself.

- Advertisement -

To restart management agents on the ESXi 6.7 login into SSH as root and run the command below:

services.sh restart

You can also restart the management agents from the ESXi host console.

My major problem was that one of these two ESXi hosts was hosting the vCenter Server and all other servers of the infrastructure. This is not suitable nor friendly for productions environments but was the only solution for me.

Besides users being more careful when removing datastores, I hope VMware had another solution to solve this kind of issue.

Resources:

- Advertisement -

https://kb.vmware.com/s/article/2004605

https://communities.vmware.com/thread/571912

https://communities.vmware.com/message/2662944#2662944

https://community.spiceworks.com/topic/1972169-remove-inactive-datastore-from-esxi

Juan Mulford
Juan Mulford
I have been active in IT for over fourteen years now. I am a solutions architect, working with storage, virtualization, and VDI solutions. For the past ten years, I have been living and working in Taiwan.

4 COMMENTS

  1. Nice! I was going to just reboot my VCSA, that wouldn't have done anything for me though.. luckily I googled, otherwise I woulda had a few minutes of confusion..
    What's awkward here is that: Previously I was told to always unmount then delete datastores, then remove the mapping from my SAN, then delete the volume on the SAN- which always worked in 5.5 and in 6.5..

    But when following this in 6.7, the datastores reappear after about 20 seconds as inaccessible as if I only deleted them from the SAN.

    You don't need to run services.sh restart, I was able to clear out mine by running:
    /etc/init.d/hostd restart
    followed by
    /etc/init.d/vpxa restart
    -I'm pretty sure this leaves a couple of the management services alone, your hosts will still drop from vCenter momentarily, but it will not impact running VMs.

  2. For me it was simpler. Select the datastore and go to “VMs”, do VM’s have an ISO mounted on this datastore? If so remove it from the VM settings (Change CD/DVD drive to “client device”). Still have the problem? VM still listed? Check if there are any snapshots and delete them (Old vm settings will still have the old datastore mounted). That should remove all the VMs. However now check the “Templates” tab, any templates listed? If so you will need to do the same on the template. For me, I couldn’t convert the template to a VM as the template was in a contradicted state as it would only power on if it could get to the datastore. I had to clone the template to a new VM, and delete the old template.

  3. If anyone else comes across this, my solution was to put the hosts in Maintenance Mode, then once the running VMs are migrated off, navigate to the host > Configure tab > System > Services, then restart the VMware vCenter Agent service. Took longer to migrate the VMs off than it did to cycle the service. Once the host was back up, the datastore was no longer listed on the Datastore tab.

Leave a Reply

- Advertisement -

Popular Articles

mulcas.com-Raspberry-Pi

Raspberry Pi OS in a Virtual Machine with VMware

4
Although the Raspberry Pi OS is designed and optimized for the Raspberry Pi module, it is possible to test and use it without its hardware, with VMware. This solution can be useful if you are a developer (or just a curious guy) and don't have a Raspberry Pi module with you
mulcas.com-VMware-OVF-Tool

How to export a Virtual Machine using the VMware OVF Tool

8
The VMware OVF Tool is implemented by VMware for easily importing and exporting virtual machines in Open Virtualization Format (OVF) standard format. Here, I want to show you how to download and install it, and then how to use it from a Windows machine.
This is not a valid source path / URL

This is not a valid source path / URL - SourceTree and Gitlab

0
I have been working on a project with a friend who set up a repository in Gitlab but even though I was able to view all projects on it, I couldn’t really join the repository. I was using SourceTree and Gitlab.
WinSCP VCSA

Unable to Access the VCSA 6.7 via WinSCP

8
One of the many and easiest ways to get the logs from the ESXi hosts and vCenter Server Appliance (VCSA), is accessing directly to the files directory using tools such as WinSCP, which helps to transfer the files between a local and a remote computer ( Ex. VCSA). I never have had issues with the ESXi hosts and WinSCP, however, trying to access the VCSA is a different story.
This request is not authorized to perform this operation.

This request is not authorized to perform this operation - Azure-Veeam

1
Attempting to add a new external repository (Azure blob storage container) to the Veeam Backup and Replication console throws the following error: This request is not authorized to perform this operation.
- Advertisement -

Recent Comments