I think I have just done something very very wrong!
Here is my setup.
1 x ESX 4.1
2 x ESX 3.5
1 x DELL MD3000i
The two esx 3.5 hosts are managed by a vCenter (version 4.1) but the ESX 4.1 host isn't. All hosts however access the same virtual disks on the MD3000i.
In a desperate move to add some more storage to some guests on the ESX 4.1 host I have extended the VMFS on the shared datastore. This seems to have worked fine on the ESX 4.1 host as I can now see the additional space.
However on one of the ESX 3.5 hosts I refreshed the storage view and the shared datastore has completely disappeared.
The second ESX 3.5 server still shows the datastore at the previous unexpanded size but I dare not refresh that one.
The guest servers on the server that the datastore has disapeared from are still running fine so I think the storage is still attached but I just can't see it in the console.
My guests are all still running so I don't want to do anything that will break them.
I can shut all down at the weekend if required.
Any suggestions on how to recover the datastore on my ESX 3.5 hosts?
I am a bit wary about performing fdisk operations on the file system as the files appear to be intact.
On the ESX4.1 server I can browse the datastore and see all of the VMDK files etc on there. The guests on the missing datastore are running.
Under Storage Adapters on the ESX3.5 hosts I can see the newly increased LUN but I don't see it as a datastore.
If I click on Add Storage I can also see the LUN with the missing datastore but If I select it the console shouts about deleting the current disk layout.
Not sure what you mean by error message.
I'm not currently getting an error which is the odd thing. All guests are running. There is one event showing on the host:
Removed datastore [datastore name] from [host name] in [datacenter name]
I have looked in var/log but there are that many log files I wouldn't know where to start.
Sorry. After somuch research, the problem is all about resignature and I would recommend to take a complete backup of the current datastore. Found some info. on the below link and also I would recommend to contact VMware support if they might help.
Not sure but can you try this when vm's are offline, I mean on a weekend or so.
Hope your problem will be fixed.