Windows OS Hub
  • Windows Server
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Active Directory Domain Services (AD DS)
    • Group Policies
  • Windows Clients
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows XP
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
    • KVM
  • PowerShell
  • Exchange
  • Cloud
    • Azure
    • Microsoft 365
    • Office 365
  • Linux
    • CentOS
    • RHEL
    • Ubuntu
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Active Directory Domain Services (AD DS)
    • Group Policies
  • Windows Clients
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows XP
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
    • KVM
  • PowerShell
  • Exchange
  • Cloud
    • Azure
    • Microsoft 365
    • Office 365
  • Linux
    • CentOS
    • RHEL
    • Ubuntu

 Windows OS Hub / Virtualization / VMWare / How to Remove an Inactive NFS Datastore on VMWare ESXi Host

April 15, 2015 VMWare

How to Remove an Inactive NFS Datastore on VMWare ESXi Host

Several times I have come across the situation when the NFS datastore on the VMWare ESXi host becomes unavailable / inactive and greyed out in the host’s storage list. However, the NFS storage stays available on the network level. Usually, it can be solved by removing the NFS storage and then adding it back.

However, it happens that when trying to remove such inactive NFS storage from the ESXi host configuration, it returns an error:

The resource datastore_nfs02 is in use.

Call “HostDatastoreSystem.RemoveDatastore” form object “datastoreSystem-28″ on vCenter Server “xxxx” failed.
CannotRemove datastore ‘datastore_name’ because Storage I/O control is enabled on it. Correct it and re-try the operation

Inactive NFS Datastore on VMWare ESXi

Based upon the error, the NFS storage cannot be removed due to the Storage I/O control (SIOC) is enabled. If you disable it, another error appears:

Datastore is not accessible

disable Storage I/O control - VMWare ESXi

Solution

To properly remove the  NFS storage from the VMWare ESXi host, you must directly connect the ESXi host server via SSH (you can enable SSH from vSphere Client).

Display the list of the NFS storages in the system:

esxcli storage nfs list

esxcli: list nfs storage

A similar command in ESXi 4.x looks like this:

esxcfg-nas -l

To unmount the NFS storage:

esxcli storage nfs remove –v datastore_nfs02

In ESXi 4.x command is as follows:

esxcfg-nas -d datastore_nfs02

Note. If the name of the NFS storage contains spaces, it has to be enclosed in quotes.

remove NFS datastore

If the NFS datastore isn’t removed from the vSphere Client, click the Refresh button in the ESXi storage section (Configuration -> Storage).

Refresh datastores view on VMWare ESXi

Note. This has to be done on every ESXi host, where you need to remove the inactive storage.

1 comment
0
Facebook Twitter Google + Pinterest
previous post
How to Hide a Windows Service from Users
next post
How Windows Determines That the File Has Been Downloaded from the Internet

Related Reading

How to Install Free VMware Hypervisor (ESXi)?

January 24, 2023

Using VMware Converter for P2V Migration (Physical to...

October 19, 2022

Using iPerf to Test Network Speed and Bandwidth

September 29, 2022

Adding Drivers into VMWare ESXi Installation Image

September 26, 2022

VMWare: Virtual Machine Disks Consolidation is Needed

September 16, 2022

1 comment

sav1 August 7, 2015 - 6:38 am

In my case the NFS storage was bisy with one of VM. Via thick vSphere Client I so it in Inventory “Datastores and Datastore Clusters” at “Virtual Machines” tab. Although there was no devices placed there at that moment and in fact of that the VM’s properties didnt content storage in storage list. But earlier there was mounted a CDROM to iso file at (i used this storage for delploy ), and there was a snapshot (i dont use snapshots in my work, but it was autogenerated with clone operation and in unknown reason didnt removed automaticaly). Then I deleted snapshot and occured VM covered from earlier tab, and then I abled to unmount storage.
Clearly, in except of using so hard manipulations (and in commonly, not preferable), in first step we should release storage from any obvious relations.

Reply

Leave a Comment Cancel Reply

Categories

  • Active Directory
  • Group Policies
  • Exchange Server
  • Microsoft 365
  • Azure
  • Windows 11
  • Windows 10
  • Windows Server 2022
  • Windows Server 2019
  • Windows Server 2016
  • PowerShell
  • VMWare
  • Hyper-V
  • Linux
  • MS Office

Recent Posts

  • Configure User’s Folder Redirection with Group Policy

    February 3, 2023
  • Using Previous Command History in PowerShell Console

    January 31, 2023
  • How to Install the PowerShell Active Directory Module and Manage AD?

    January 31, 2023
  • Finding Duplicate E-mail (SMTP) Addresses in Exchange

    January 27, 2023
  • How to Delete Old User Profiles in Windows?

    January 25, 2023
  • How to Install Free VMware Hypervisor (ESXi)?

    January 24, 2023
  • How to Enable TLS 1.2 on Windows?

    January 18, 2023
  • Allow or Prevent Non-Admin Users from Reboot/Shutdown Windows

    January 17, 2023
  • Fix: Can’t Extend Volume in Windows

    January 12, 2023
  • Wi-Fi (Internet) Disconnects After Sleep or Hibernation on Windows 10/11

    January 11, 2023

Follow us

woshub.com
  • Facebook
  • Twitter
  • RSS
Popular Posts
Footer Logo

@2014 - 2023 - Windows OS Hub. All about operating systems for sysadmins


Back To Top