vcenter vSAN 5.5 U2 - Web interface Datastore shows red "Inactive"

[COS]

From the web client the one of my datastores is showing red "Inactive".

I can't seem to see what's causing this. From the web client, I can create a folder, delete the folder, create/copy a file into it and delete. I can even move a VM in there.

From the thick client I don't see any errors and I can do everything I did from the web client.

Yet the dang web client keeps saying the datastore is "Inactive".

I made sure no VM's had any files attached to that datastore. No iso images connected from it.

I even made sure no VM's had snapshots.

It just the lab so not many VM's on there.

Any ideas?

Thanks

[ramakrishnak]

what type of datastore is this (NFS|VMFS|VSAN) ?

Intermittent network issues/connection losses can trigger such things (look at the vsphere and host side logs to see if this is the case). 

Also look at the Alerts/Event in the vCenter  (datastore - > Monitor -> {issues|Events} section )

try refreshing the datastore and see if this comes back to active state

Thanks,

[COS]

Aw man, there I go agin not giving enough info.......lol

All my datastores are local SAS drives/LUN's.

I recall having this issue before and rebooted the vCenter server, but no luck this time.

What I did do is evacuate the host, put it in maint mode then rebooted the host.

That did the trick. Now all datastores are happy.

Now the question is why did I have to even do this if the datastore completely functional.

Thanks

[ramakrishnak]

> Aw man, there I go agin not giving enough info.......lol

  more info is always good to get enough clues

>Now the question is why did I have to even do this if the datastore completely functional.

seems like some intermittent issue resulted in datastore query timeouts and an inconsistent host-cache entries (vpx/hostd logs would give you information on why this happened)

if you had just restarted the hostd process (/etc/init.d/hostd restart), you should have got back to consistent state if this was the case

but again this is all deducing from limited info without any logs so it could well be some other issue (-;

Thanks,