Welcome to the Community - I would try removing the host from vCenter and reading to see if you can see the local storage.
1 person found this helpful
Thanks for the reply. Just to Note HA is currently enabled on vCenter... and Should I disconnect, or actually remove it.. and is there a difference?
1) Disable HA
2) disconnect/remove ESX 2 from vCenter
3) reconnect the ESX host to vCenter?
If someone could link me to some reading material on the subject, I would be more than happy to read it, and thanks in advance!
1 person found this helpful
Could server ESXi2 local storage be formatted with VMFS3 from an upgrade situation? Did you ever see the local storage in ESXi2 in the cluster storage in vcenter or never? Also, have you previously unmounted then remounted the local storage on ESXi2, especially after the server joined the cluster? Sometimes I see that in an unmount and then remount the name of the mounting point changes (or gets stuck) by default to something similar, so for example in stead of Datastore 1 you will now have Datastore 1 (1) which may not be obviously distinguishable. So the cluster may be looking for the old datastore name and you may be seeing a different data store name. Adding and removing as stated above may remedy this.
Once again I thank you for your reply. It's VMFS5, both ESX hosts local datastores are identical in both Physical (RAID type, and storage controller) and Digital setup (File Table type, mount style) AFAIK.
I'm not sure if it was ever visible or not, cause...
We have a new SAN (EMC VNXe) which apparently was unable to do a true quick failover when a SP went down and thus we didn't want to store any VM's hdds on this SAN till the failover was deemed working as described. So the old admin moved all the VM's hdd to their respected hosts local storage. There was no documentation on setup of the ESXi hosts, or the vCenter by this individual, there was change ticket done on the steps taken during the change... so after multiple mess ups he was removed and I was set to fix all the mistakes left behind. I have a lot to learn in a short time, the difference is I won't make false claims and I'll admin when I don't know something and will ask for help.
SOOO, I will first try to remove the host and readd it to vCenter after disabling HA, as this won't bring down any VM's in the process... All these VM's are in production So I'm taking real care not to bring any important corporate services down while trying to clean everything up. In the event that fails, I may attempt your advice, I don't want to just go remounting the local storage while all it's VM's hdds are hosted there. In that case, I would move all ESXi 2 VM's HDD's temporarily to the SAN, then attempt a unmount, remount.
I will report my findings, after these steps...
I just had to remedy something like this myself. If it's not already working, it may be helpful to see if you can schedule downtime to get vMotion working. Otherwise, it may just be worth your while to switch to a new boot drive and do a new install of ESXi from scratch. Get a vCenter up and running as a virtual appliance, or not (to reduce downtime you can build the vCenter on a notebook with workstation and then upload it), then import in your hosts and VMs. It may seem radical as an approach, but it removes all the unknowns and uncertainties from your setup. Also, you may end up fixing your problem along with others you have not found yet, and get some bonus points for swinging and upgrade at the same time. If you can't install another array or attach more storage, do a quick install to a thumbdrive and boot from USB - image a few USB drives, but you only need them connected at boot time.
Hey thanks for the additional suggestions...
However, disconnecting and then removing the host, and then readding the host solved the issue. And I am finally able to see executors local storage on vCenter, either through thickclient or web interface! Cheers thanks all for the suggestions!