vmmax2479
Contributor
Contributor

unable to add NFS to ESX 3.5

trying to add NFS to esx3.5 and getting this error:

error during the configuration of the host: Unable to create object, volume name not valid.

I am using Allegro NFS on windows pc

nfs is accessible by typing the

when adding NFS I have provided

server: 192.168.10.102

Folder: vm

Datastore Name: Datastore1

0 Kudos
17 Replies
eoporto
Contributor
Contributor

It is always possible the CIFS shared path is different from the NFS

shared path. Have you checked whether the path is "vm" or "Vm" or "VM"

or something totally different on the NFS side?

Can you NFS mount the "vm" share on 192.168.10.102 from other hosts?

Beware of he who would deny you access to information, for in his heart, he dreams himself your master.

Beware of he who would deny you access to information, for in his heart, he dreams himself your master. P.S : If you think that the answer is helpful please consider rewarding points.
0 Kudos
vmmax2479
Contributor
Contributor

How do I mount NFS using command line in ESX?

0 Kudos
eoporto
Contributor
Contributor

/usr/sbin/esxcfg-nas -a -o $nfsserver -s $nfsmount $mountname

Beware of he who would deny you access to information, for in his heart, he dreams himself your master.

Beware of he who would deny you access to information, for in his heart, he dreams himself your master. P.S : If you think that the answer is helpful please consider rewarding points.
0 Kudos
JoJoGabor
Expert
Expert

Can you confirm that the VMKernel can ping the NFS server using vmkping 192.168.x.x.?

The VMkernel will need to be able to reach the NFS server before it can mount the export

0 Kudos
vmmax2479
Contributor
Contributor

Able to ping by name and ip address

# vmkping lafile

PING lafile (192.168.10.120): 56 data bytes

64 bytes from 192.168.10.120: icmp_seq=0 ttl=255 time=6.383 ms

64 bytes from 192.168.10.120: icmp_seq=1 ttl=255 time=1.861 ms

64 bytes from 192.168.10.120: icmp_seq=2 ttl=255 time=13.596 ms

--- lafile ping statistics ---

3 packets transmitted, 3 packets received, 0% packet loss

round-trip min/avg/max = 1.861/7.280/13.596 ms

# vmkping 192.168.10.120

PING 192.168.10.120 (192.168.10.120): 56 data bytes

64 bytes from 192.168.10.120: icmp_seq=0 ttl=255 time=2.475 ms

64 bytes from 192.168.10.120: icmp_seq=1 ttl=255 time=2.299 ms

64 bytes from 192.168.10.120: icmp_seq=2 ttl=255 time=18.858 ms

This is what i get when mounting

# /usr/sbin/esxcfg-nas -a -o lafile -s users export

Connecting to NAS volume: export

Unable to connect to NAS volume export: NFS Error: Unable to Mount filesystem: The mount request was denied by the NFS server. Check that the export exists and that the client is permitted to mount it

0 Kudos
eoporto
Contributor
Contributor

So are other systems able to mount that NFS share?

Does the NFS server have any exports restrictions which might be preventing a successful mount?

Beware of he who would deny you access to information, for in his heart, he dreams himself your master. P.S : If you think that the answer is helpful please consider rewarding points.
0 Kudos
vmmax2479
Contributor
Contributor

has anyone used allegro. can you verify my settings?

see attached

Also what do you mean by other system, another esx host?

this is the test environment and I do not have a lot of servers to play around.

0 Kudos
vmmax2479
Contributor
Contributor

i think i got closer

# /usr/sbin/esxcfg-nas -a -o adminpc2 -src export

Error performing operation: Unable to create new NAS volume. adminpc2:rc is already exported by a volume with the name export

# /usr/sbin/esxcfg-nas -l

export is rc from adminpc2 unmounted

so how do i mount

0 Kudos
cmacmillan
Hot Shot
Hot Shot

Use "/export/src" as the "Folder" name and "192.168.10.120" as the "Server" name, with "allegro-srs" as the Datastore name (or whatever) and mount read-only (useful for ISO) or not depending on use.

--Collin C. MacMillan

SOLORI - Solution Oriented, LLC

Collin C. MacMillan, VCP4/VCP5 VCAP-DCD4 Cisco CCNA/CCNP, Nexenta CNE VMware vExpert 2010-2012 SOLORI - Solution Oriented, LLC http://blog.solori.net If you find this information useful, please award points for "correct" or "helpful".
0 Kudos
vmmax2479
Contributor
Contributor

the reason I amtrying to mount this is for vmts backup.

so it has to be r/w

woukd you please type the full command...

thanks

0 Kudos
weinstein5
Immortal
Immortal

A quick question - what is the IP address of you NFS share? - in this post you are trying vmkping 192.168.10.120 while in the original question you have your NFS datastore with a 192.168.10.102 IUP address. Also make wure that the NFS server is NFS version 3 over TCP and that the ESX host has full root access to the NFS share - this is very important

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
vmmax2479
Contributor
Contributor

IP address 192.168.10.102. another one was a typo. as you can see in print screen i have attached the entire subnet has access to it.

Anyone accomplish this with Allegro? this is testing environemnt i am trying to setup so any other free NFS software welcome

0 Kudos
JeffDrury
Hot Shot
Hot Shot

Have you allowed the NFS client in the ESX firewall? It should open ports 111,2049 (UDP,TCP). By default this is not enabled.

eoporto
Contributor
Contributor

NFS comes free with a free Linux distro like CentOS. 😃

Beware of he who would deny you access to information, for in his heart, he dreams himself your master. P.S : If you think that the answer is helpful please consider rewarding points.
0 Kudos
dmn0211
Enthusiast
Enthusiast

Use the showmount command to check if you can see the export.

showmount -e NFSservername

0 Kudos
vmmax2479
Contributor
Contributor

works now.

enanbled ports in FW and used /export/src as folder

thank you all

0 Kudos
vmmax2479
Contributor
Contributor

works

0 Kudos