Unable to mount NFS Datastore ESXi 4.1.0 (U1)

[stuarty18742011]

When I attempt to mount a data store to our ESXi 4.1.0 (U1) hosts I get the following error... 

Call "HostDatastoreSystem.CreateNasDatastore" for object "datastoreSystem-1264" on vCenter Server "OurVCENTER.OurDomain.ca" failed.

Operation failed, diagnostics report: Unable to complete Sysinfo operation.  Please see the VMkernel log file for more details.

This was mounted without issue on our ESX 3.5 (U5) host before we upgraded it to ESXi 4.1.0 (U1)

Any ideas?

[DSTAVERT]

Make sure the name resolves or try the IP.

[stuarty18742011]

We are using the IP.

Its strange as this was working previous to upgrading to ESXi 4.1.0 (U1)

[DSTAVERT]

Test the mount to some linux machine or if you have command line access on the NFS machine try to mount the share to another local folder on that machine to make sure everything is functional. Try using a different name for the mount in ESXi.

[DSTAVERT]

What information do you get from the NFS logs?

[stuarty18742011]

It mounts without issue to the other ESX 3.5 hosts. I did an unmount and mount and it does work on a 3.5 host

I tried to mount to the i4 host using another name but that failed.

I checked  /var/log/messages but thats not being very helpful.

What NFS log can I look at?  Is that on the filer itself?

Ps.. thanks for helping

[DSTAVERT]

See what information is in the logs on the filer.

[paulkdickson]

What do you have on your export auth list?

Try making one such as

/export/test *(parametersHere)

and connecting to that.

I've seen esxi4.1 get wonky with nfs4 auth.  *shrug*.

[stuarty18742011]

Storage guys is off today.  I'll see if I can get hold of him later.

Are there any logs on the ESXi host that I can look at?  

[DSTAVERT]

I've seen esxi4.1 get wonky with nfs4 auth.  *shrug*.

ESXi only supports NFS3.

I do agree though that setting up a test share would be a good idea.

[DSTAVERT]

If you have SSH enabled on the ESXi host you can use scp to copy the file /var.log/messages You can also just use the Tech Support console to view the files directly.

[stuarty18742011]

We resolved the issue.

• On our ESX 3.5 Hosts we had the Vmotion IP configured in our NFS Export (vmk0)
  
• On our ESX 3.5 Hosts the Service Console is named vswif0
  

When we upgraded to ESXi 4.1.0 (U1)

• the Management Network (Service Consol) became (vmk0) which is used by NFS.
  
• on ESXi 4.1.0 (U1) Vmotion is now on (vmk1)
  

Solution; we updated the NFS export to use the Management Network IP (vmk0) and it works.

This article helped us work it out...

http://www.gavinadams.org/blog/2010/07/19/esxi-41-and-the-9000-byte-mtu-on-vmk0

"The Problem
I couldn’t provision my NAS storage into a different VLAN / physical network, which would be best practices for storage for the ESXi hosts. And I didn’t realize that with ESXi there is no way to set tell the hypervisor which port group / vmk to use for NFS access. It’s based on the configured network of the NAS device or based on the lowest numbered vmk of the machine. And since vmk0, Management Network, is created by default with an MTU of 1500 bytes, getting that to 9000 bytes is a problem."

Hope this helps someone else... and thanks for everyones help.