How to fix vSphere and vCenter datastore reverting to old size

security design cybersecurity consulting services compliance

Workaround

For EACH host in the datacenter that had a connection to the faulty storage, I performed these steps:

      1. Navigate to Hosts & Clusters tab
      2. Select first host
      3. Configure tab
      4. Storage Devices tab
      5. Click button “Refresh host storage info…”
      6. Click button “Rescan all storage adapters…”
      7. Repeat for next host.

Voila, the next day when I checked, the correct datastore size was still displaying.  Months later, we have had no re-occurrences.

Hope this helps.  If you have comments, please help others by posting them!

(shameless self promotion)  By the way, I consult on VMware, Storage Area Networks (such as Netapp, Synology, FreeNAS, High Availability Designs, and networking for server performance.  I offer 30 minutes of free technical advice on these topics: if we can solve your problems in that time, great!  If the problem is too big, we can start working on a plan together.   Please schedule using the button below!  – Amira Armond, President, Kieri Solutions

Kieri Solutions provides consulting on this technology. We would be thrilled to chat and give you advice about your project.

v. amira armond picture venus ceo president founder about kieri solutions llc

kieri solutions IT consultant service provider cybersecurity logo

8 thoughts on “How to fix vSphere and vCenter datastore reverting to old size

  1. Boris Büttner says:

    Thank you very much we had the same issue even though all ESX hosts had the same patchlevel. All the time one datastore was reverting to the original size. Your workaround fixed it.

  2. Jeff says:

    Thanks! This worked for us, as well! We were running the same version of ESX across all hosts and kept having a handful of datastores revert to their original size…even after upgrading all ESX hosts. After performing the workaround as described, the issue is fixed! I’m glad it was simple.

  3. Tom Borcher says:

    Thank you! We had this problem with one of our datastores too. And like the other commenters, all hosts in the datacenter were running the same version of ESXi (in our case it was 6.5U1g – 7967591). Rescanning all hosts worked. FYI, you can just select the cluster (if the hosts are in a cluster) and kick off a scan of all the hosts rather than scanning them one at a time. Thanks again!

  4. Kevin says:

    I do a lot of datastore expansions and run into this issue ALL the time… Thank you Amira for the solution!

    How about a PowerCLI script to automate this? On my last expansion I ran this script after the LUN expansion and again after the datastore expansion. Worked for me!

    import-module “VMware.VimAutomation.Core”
    connect-viserver
    Get-Datacenter | Get-VMHost | Get-VMHostStorage -Refresh
    Get-Datacenter | Get-VMHost | Get-VMHostStorage -RescanAllHba
    Get-Datacenter | Get-VMHost | Get-VMHostStorage -RescanVmfs
    sleep 10
    Get-Datacenter | Get-VMHost | Get-VMHostStorage -Refresh
    Get-Datacenter | Get-VMHost | Get-VMHostStorage -RescanAllHba
    Get-Datacenter | Get-VMHost | Get-VMHostStorage -RescanVmfs

  5. Oliver Saße says:

    Thank you very much. We had the same issue. All the time the datastore was reverting to the original size, but your workaround fixed it.

Leave a Reply

Your email address will not be published.