VMware Cloud Community
shoaibsuleman
Contributor
Contributor

Datastore not appear on all esxi servers

i have vcenter 4.1 and esxi /esx 4.1 server, i have probem with datastore only some esxi servers datastore is appear and other 3 servers datastore is not appear i also chenon  HBAs LUN is available but its not available as datastore event when i try to add datastore it also not appear there.

can any one help me?

Reply
0 Kudos
7 Replies
AWo
Immortal
Immortal

Is the LUN presented to each host with the same LUN number?

Does the masking configuration allow each host in question access?

AWo

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
Reply
0 Kudos
Walfordr
Expert
Expert

Are you using iSCSI or Fiber Channel storage?

-Make sure that your LUN masking is correct

--Make sure that all the hosts are in the intitiator group that the LUN is mapped to on the storage side.

-If Fiber channel make sure that your Zoning is correct.  Make sure all hosts and storage are in the same zone in the Fiber channel fabric.

In vCenter 4.1 when you add a new datastore its automatically added to all hosts so something is wrong....

Robert

Robert -- BSIT, VCP3/VCP4, A+, MCP (Wow I haven't updated my profile since 4.1 days) -- Please consider awarding points for "helpful" and/or "correct" answers.
Reply
0 Kudos
shoaibsuleman
Contributor
Contributor

yes LUN is available on all esx server and I am using FC 

Reply
0 Kudos
a_p_
Leadership
Leadership

Did you verify that the LUN is presented to all hosts with the same host LUN ID (see AWo's question)?

If this is the case, run a rescan on one of the ESXi hosts and then immediately check the entries in /var/log/messages. Maybe the LUN is recognized as a snapshot LUN. In this case - and if you are sure everything is correct - you could try to force mount the datastore from the command line.

Anré

Reply
0 Kudos
shoaibsuleman
Contributor
Contributor

these are the messages when i am try to rescan

Jan   1 00:51:18 vmkernel: 0:00:25:02.441 cpu10:4225)WARNING: NMP: nmpPathClaimEnd:  Device, seen through path vmhba1:C0:T0:L0 is not registered (no active  paths)

Jan   1 00:51:18 vmkernel: 0:00:25:02.444 cpu12:4222)WARNING: NMP: nmpPathClaimEnd:  Device, seen through path vmhba1:C0:T0:L0 is not registered (no active  paths)

Jan   1 00:51:18 vmkernel: 0:00:25:02.481 cpu8:4223)WARNING: NMP: nmpPathClaimEnd:  Device, seen through path vmhba1:C0:T0:L0 is not registered (no active  paths)

Reply
0 Kudos
a_p_
Leadership
Leadership

Please double check your FC and Storage configuration. Like Walfordr already mentioned, make sure the zoning is correct and the LUNs are presented correctly. Please compare the paths that you see in "Storage Adapters" on a host that's working and one that's not working. Maybe some screen shots can help!?

André

Reply
0 Kudos
shoaibsuleman
Contributor
Contributor

hi, another error which i would like to share with you, can anyone recognize

Disk /dev/disks/naa.60050768018e82ea4800000000000049: 2040.1 GB, 2040109465600 bytes
255 heads, 63 sectors/track, 248029 cylinders, total 3984588800 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk /dev/disks/naa.60050768018e82ea4800000000000049 doesn't contain a valid partition table
Reply
0 Kudos