VMWare Datastores Help

Posted on 2012-03-13
Last Modified: 2012-08-13
It seems our VMWare and Datastores is broken.

2 ESXi vSphere 5 hosts
1 Starwind SAN

On ESX1, all datastores look fine and visible.

On ESX2, it can only see local storage.

- If you go to "Add Storage" it can see the SAN Datastores, but the only option is to Format the store, not to keep existing signature.

- Under Storage Adapters, all the paths are there and mounted (all showing same LUN values - same as ESX1)

- If you try to add a datastore which is NOT on ESX1, Keep Existing Signatures is valid but the operation fails with error "Cannot change the host configuration"

Prior to this everything was working fine - both hosts could connect to the datastores (clustered mode on Starwind is enabled).

ESX servers have been rebooted several times as has vCentre VM (Linux version)

The only difference is that the vCentre was moved to a different host - from ESX1 SAN Storage to ESX2 Local Storage so we could reboot the host and keep vCentre up.

Of course now we cant move it back because we cant add in the datatstores...

Any ideas?
Question by:hongedit
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 5
LVL 121

Accepted Solution

Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 37714233
do the following at the console or remote via SSH

~ # esxcfg-volume -l
VMFS3 UUID/label: 4cc89503-f054d0d4-2865-00221958e471/nas3-vmfs
Can mount: Yes
Can resignature: No (the volume is being actively used)
Extent name: naa.600140588e9bab7d2b7ed4b53dadc1de:1     range: 0 - 1048319 (MB)

and then using UUID or friendly datastore label

esxcfg-volume -m 4cc89503-f054d0d4-2865-00221958e471


esxcfg-volume -m nas3-vmfs

Author Comment

ID: 37714284
Before I do that - is running vCentre on local storage supported? I.E how does it see/manage the other ESX servers if its not on SAN storage?
LVL 121
ID: 37714300
Yes, vCenter could be running on a standalone physical server with NO access to the SAN. Its the hosts that are configured and connected to shared storage.
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

LVL 121
ID: 37714306
it manages them via the network via 443 TCP.

Author Comment

ID: 37714357
That worked.

So now on ESX2 the VM's are showing, but a lot of them have red !'s on them?
LVL 121
ID: 37714382
what does the alert state for the VM?

Do you have a Cluster and use HA?

Author Comment

ID: 37714405
No HA.

Thats the thing - I see this Red ! but under alarms its empty.
LVL 121
ID: 37714412
Phantom Alert Bug in vSphere 5.0.

Author Comment

ID: 37714423

So why did this happen, and will we need to do this everytime we reboot etc?
LVL 121
ID: 37714449
this can happen on vSphere, the servers forget or do no mount correctly the iSCSI LUN, we have seen it in all versions, but seems to occur more often in 5.0.

you should find it mount normally, but you now have the fix or workaround if it does not.
LVL 121
ID: 37714458
check if running latest ESXi 5.0 build and Starwind iSCSI builds as well.

Author Comment

ID: 37714486
Know its not the latest for sure, its on a to do list that is ever growing!

Featured Post

Connect further...control easier

With the ATEN CE624, you can now enjoy a high-quality visual experience powered by HDBaseT technology and the convenience of a single Cat6 cable to transmit uncompressed video with zero latency and multi-streaming for dual-view applications where remote access is required.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Will try to explain how to use the VMware feature TAGs in the VMs and create Veeam Backup Jobs using TAGs. Since this article is too long, I will create second article for the Veeam tasks.
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to rename, unmount, delete and upgrade VMFS datastores. Open vSphere Web Client: Rename VMFS and NFS datastores: Upgrade VMFS-3 volume to VMFS-5: Unmount VMFS datastore: Delete a VMFS datastore:
Teach the user how to edit .vmx files to add advanced configuration options Open vSphere Web Client: Edit Settings for a VM: Choose VM Options -> Advanced: Add Configuration Parameters:

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question