We have a situation where we cannot browse the contents of a specific datastore, but multiple VM's are running from that datastore in good health.
I have troubleshot this as far as i can, i would really appreciate some expertise here, it feels like a super easy fix, but i can't find it.
vsphere server at 172.16.1.120, version 5.0.0
esxi physical server at 172.16.1.245, version 5.0
"broken" datastore is on an iSCSI target at 172.16.1.226
if i log into vsphere client directed at the vcenter manager 172.16.1.120, logging in with active directory (a domain admin) - i can see all of our physical esxi hosts, all of our VM's and everything is fine - except this one datastore.
on one esxi host, one VM isn't powered on. Went to power it on, errored out as insufficient permission.
Weird, i though, so i went to browse the datastore it lives on (as seen from its esxi host) - the datastore appears blank (blank as in all i see is "\" and no folders or files)
in a panic, i check the health of the other vm's on this datastore - they're running just fine (but i can't browse the datastore or see their vmdk files)
so i try to make a new folder on the "blank" datastore, and receive:
"Call “FileManager.MakeDirectory” for object “FileManager” on vCenter Server “servername.company.com” failed.
Google searched that, found 5-10 articles mentioning various things, but so far all i can find for sure is that if i use vsphere client to log DIRECTLY into the esx host itself as root (172.16.1.245), i can browse the same datastore just fine, see files, make/delete things, no problem
So the issue has to center around vsphere server - the problem is only present when logging in there
I've read that sometimes this happens and if you log into vcenter as root, you have proper permissions... but nobody knows the root password at this time (it isn't root, vmware, blank, or any of our prior passwords we like to use)
So, how can i make this datastore usable from vcenter again?