Highlighted
Contributor
Contributor

ESXi 4.1 can not add NFS Datastore on a Netgear READYnas 1100 ( Please Help)

Jump to solution

I have a Netgear ReadyNAS 1100 NAS

where I have set a NFS share so I can add a Datastore on my ESXi 4.1, I

used the following instructions in their site:

Every

time I try to attach the NFS share through the GUI i get the following

message: "Operation failed, diagnostics report: Unable to complete

Sysinfo operation. Please see the VMkernel log file for more details."

I

have also tried through the SSH console by using the command:esxcfg-nas

-a -o 10.0.0.10 -s /share/mynfs mynfs and I get the error:

"Connecting to NAS volume: mynfs

Unable to connect to NAS volume mynfs: Unable to complete Sysinfo operation. Please see the VMkernel log file for more details."

the Kernel log details are:

Aug 19 14:37:36 Hostd: Failed to read header on stream TCP(local=127.0.0.1:60962, peer=127.0.0.1:0): N7Vmacore15S ystemExceptionE(Connection reset by peer)

Aug 19 14:37:47 Hostd: PersistAllDvsInfo called

Aug 19 14:37:51 Hostd: Ticket issued for CIMOM version 1.0, user root

Aug

19 14:37:59 Hostd: [2010-08-19 14:37:59.311 2AAA3B90 info 'TaskManager'

opID=993D2353-0000037C] Task Created : haTask-ha-host-vim.host.DatastoreSystem.creat eNasDatastore-1124

Aug 19 14:37:59 Hostd: Creating datastore test

Aug 19 14:37:59 Hostd: AddNasVolume called

Aug

19 14:37:59 Hostd: [2010-08-19 14:37:59.312 FFFB0B90 verbose

'FSVolumeProvider' opID=993D2353-0000037C] LookupVmfs: Cannot find VMFS

volume with id <unset>,path, <unset>, or name test

Aug 19

14:37:59 Hostd: [2010-08-19 14:37:59.312 FFFB0B90 verbose

'FSVolumeProvider' opID=993D2353-0000037C] LookupNasByName: Cannot find

NasVolume with volume n ame test

Aug 19 14:37:59

vmkernel: 0:23:10:59.338 cpu0:5299)NFS: 149: Command: (mount) Server:

(10.250.50.93) IP: (10.250.50.93) Path: (/esx) Label: (test) Options:

(Non e)

Aug 19 14:38:29 vmkernel: 0:23:11:29.669

cpu2:5299)WARNING: NFS: 946: MOUNT RPCfailed with RPC status 13 (RPC was

aborted due to timeout) trying to mount Serve r

(10.250.50.93) Path (/esx)

Aug 19 14:38:29 vmkernel: 0:23:11:29.669 cpu2:5299)NFS: 160: NFS mount 10.250.50.93:/esx failed: Unable to connect to NFS server

Aug 19 14:38:29 vobd: Aug 19 14:38:29.727: 83489529043us: http://esx.problem.vmfs.nfs.mount.connect.failed Failed to mount to server 10.250.50.93 mount point /esx. E rror: Unable to connect to NFS server.

Aug

19 14:38:29 Hostd: [2010-08-19 14:38:29.727 FFFB0B90 error

'FSVolumeProvider' opID=993D2353-0000037C] VmkCtl mount or ProcessNas

failed: Unable to completeSysinfo operation. Please see the VMkernel

log file for more details.

Aug 19 14:38:29 Hostd: [2010-08-19

14:38:29.727 2AA15B90 info 'ha-eventmgr'] Event 79 : Failed to mount to

the server 10.250.50.93 mount point /esx. Unable to c

onnect to NFS server

Aug 19 14:38:29 Hostd: [2010-08-19 14:38:29.740

FFFB0B90 info 'App' opID=993D2353-0000037C] AdapterServer caught

exception: 2a6fb460

Aug 19 14:38:29 Hostd: [2010-08-19 14:38:29.740

FFFB0B90 info 'TaskManager' opID=993D2353-0000037C] Task Completed :

haTask-ha-host-vim.host.DatastoreSystem.cre ateNasDatastore-1124 Status error

Aug

19 14:38:29 Hostd: [2010-08-19 14:38:29.740 FFFB0B90 info 'Vmomi'

opID=993D2353-0000037C] Activation : Invoke done on

Aug 19 14:38:29 Hostd: Arg spec:

Aug 19 14:38:29 Hostd: (vim.host.NasVolume.Specification) {

Aug 19 14:38:29 Hostd: dynamicType = <unset>,

Aug 19 14:38:29 Hostd: remoteHost = "10.250.50.93",

Aug 19 14:38:29 Hostd: remotePath = "/esx",

Aug 19 14:38:29 Hostd: localPath = "test",

Aug 19 14:38:29 Hostd: accessMode = "readWrite",

Aug 19 14:38:29 Hostd: type = "nfs",

Aug 19 14:38:29 Hostd: userName = <unset>,

Aug 19 14:38:29 Hostd: password = <unset>,

Aug 19 14:38:29 Hostd: }

Aug 19 14:38:29 Hostd: Throw vim.fault.PlatformConfigFault

Aug 19 14:38:29 Hostd: Result:

Aug 19 14:38:29 Hostd: (vim.fault.PlatformConfigFault) {

Aug 19 14:38:29 Hostd: dynamicType = <unset>,

Aug 19 14:38:29 Hostd: faultCause = (vmodl.MethodFault) null,

Aug 19 14:38:29 Hostd: faultMessage = (vmodl.LocalizableMessage) [

Aug 19 14:38:29 Hostd: (vmodl.LocalizableMessage) {

Aug 19 14:38:29 Hostd: dynamicType = <unset>,

Aug 19 14:38:29 Hostd: key = "com.vmware.esx.hostctl.default",

Aug 19 14:38:29 Hostd: arg = (vmodl.KeyAnyValue) [

Aug 19 14:38:29 Hostd: (vmodl.KeyAnyValue) {

Aug 19 14:38:29 Hostd: dynamicType = <unset>,

Aug 19 14:38:29 Hostd: key = "reason",

Aug

19 14:38:29 Hostd: value = "Unable to complete Sysinfo

operation. Please see the VMkernel log file for more details.",

Aug 19 14:38:29 Hostd: }

Aug 19 14:38:29 Hostd: ],

Aug 19 14:38:29 Hostd: message = <unset>,

Aug 19 14:38:29 Hostd: }

Aug 19 14:38:29 Hostd: ],

Aug 19 14:38:29 Hostd: text = "",

Aug 19 14:38:29 Hostd: msg = ""

Aug 19 14:38:29 Hostd: }

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Enthusiast
Enthusiast

Check your DNS server settings on the NFS Datastore. I had a nasty time-out issue w/ my NFS server. We set it to OPENDNS temporarily and the NFS store popped up right away.

Joe

View solution in original post

0 Kudos
19 Replies
Highlighted
Immortal
Immortal

have also tried through the SSH console by using the command:esxcfg-nas -a -o 10.0.0.10 -s /share/mynfs mynfs and I get the error:

Aug 19 14:38:29 vmkernel: 0:23:11:29.669 cpu2:5299)NFS: 160: NFS mount 10.250.50.93:/esx failed: Unable to connect to NFS server

I see two different IP addresses. Can you ping the NAS device from the ESXi host?

-- David -- VMware Communities Moderator
0 Kudos
Highlighted
Contributor
Contributor

Sorry, and thank you for your prompt answer.

the real ip is 10.250.50.93 and yes it is pingable from the ESXi box, see below:

  1. vmkping 10.250.50.93

PING 10.250.50.93 (10.250.50.93): 56 data bytes

64 bytes from 10.250.50.93: icmp_seq=0 ttl=64 time=6.613 ms

64 bytes from 10.250.50.93: icmp_seq=1 ttl=64 time=0.222 ms

64 bytes from 10.250.50.93: icmp_seq=2 ttl=64 time=0.190 ms

--- 10.250.50.93 ping statistics ---

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

round-trip min/avg/max = 0.190/2.342/6.613 ms

~ #

0 Kudos
Highlighted
Immortal
Immortal

I don't know what Netgear means by "Root privilege enabled hosts" on the share permissions page but I would try checking that box.

-- David -- VMware Communities Moderator
0 Kudos
Highlighted
Contributor
Contributor

I Have tried and have the root host listed as the IP address as per NETGEAR's instructions, I can load up from a Ubuntu box, install the NFS client (sudo apt-get install nfs-common), mount the share to a folder (Sudo Mount 10.250.50.93:/ESX /home/ubuntu/NFS ), write to it, and see it save files on the server. so I know the Netgear Share works. it is something to do with ESXi, NFS versioning, I don't know. I do appreciate your help and hope my rant is helpful to you and anyone suffering with this issue.

0 Kudos
Highlighted
Immortal
Immortal

I see an upper case ESX in the Ubuntu mount string. Case is important.

-- David -- VMware Communities Moderator
0 Kudos
Highlighted
Contributor
Contributor

Good catch but no cigar, same error, I even tried another NAS just in case this one was defective and i got this

Aug 19 18:10:06 shell[167257]: esxcfg-nas -a -o 10.250.50.94 -s /ESX DATA1

Aug 19 18:10:06 vmkernel: 1:02:43:06.501 cpu1:168083)NFS: 149: Command: (mount) Server: (10.250.50.94) IP: (10.250.50.94) Path: (/ESX) Label: (DATA1) Options: (None)

Aug 19 18:10:20 Hostd: HostCtl exception Unable to complete Sysinfo operation. Please see the VMkernel log file for more details.

Aug 19 18:10:37 vmkernel: 1:02:43:37.322 cpu3:168083)WARNING: NFS: 946: MOUNT RPC failed with RPC status 13 (RPC was aborted due to timeout) trying to mount Server (10.250.50.94) Path (/ESX)

Aug 19 18:10:37 vmkernel: 1:02:43:37.322 cpu3:168083)NFS: 160: NFS mount 10.250.50.94:/ESX failed: Unable to connect to NFS server

Aug 19 18:10:37 vobd: Aug 19 18:10:37.377: 96217179426us: http://esx.problem.vmfs.nfs.mount.connect.failed Failed to mount to server 10.250.50.94 mount point /ESX. Error: Unable to connect to NFS server.

Aug 19 18:10:37 Hostd: Event 99 : Failed to mount to the server 10.250.50.94 mount point /ESX. Unable to connect to NFS server

Aug 19 18:10:40 Hostd: HostCtl exception Unable to complete Sysinfo operation. Please see the VMkernel log file for more details.

0 Kudos
Highlighted
Immortal
Immortal

ESX(i) uses the equivalent of anonymous access. I don't know what the settings are like in the Netgear device. There isn't much you could change in ESX(i). When the settings are right on the NFS device it just connects.

-- David -- VMware Communities Moderator
0 Kudos
Highlighted
Enthusiast
Enthusiast

Check your DNS server settings on the NFS Datastore. I had a nasty time-out issue w/ my NFS server. We set it to OPENDNS temporarily and the NFS store popped up right away.

Joe

View solution in original post

0 Kudos
Highlighted
Contributor
Contributor

Joe,

The NAS had a static IP entry and did not allow me to add any DNS server entries manually, I decided to change it to DHCP so it autopopulates and sure enough, the NFS share started to work. it shouldn't have matter but it did I guess, thanks everyone for all your help.

0 Kudos
Highlighted
Enthusiast
Enthusiast

Glad that little tid bit helped. That's a nugget I will hold close to me forever, because I struggled with it for about 4 hours thinking it was something else...

0 Kudos
Highlighted
Contributor
Contributor

ROTFLMAO!!!!!!!!!!!!I just spend 7 hours with this, I even installed iSCSI (Not supported) and after I had just finished all this PITA iSCSI installation process, you send the simplest solution and it worked!!! my desk has half of my torn off hair and my bloddy scalp has the rest!!!!!! Hehehehe

Thanks a bunch!!!!!

0 Kudos
Highlighted
Contributor
Contributor

Sweet! This also fixed my problem. To be more exact, just make sure the ReadyNAS can reach a DNS server. Damned if I know why it needs to, but there we are. Thank goodness, I was certain that my vCenter and/or ESXi server was broken.

0 Kudos
Highlighted
Enthusiast
Enthusiast

I know that this question has already been answered but I have recently had a client experience a very similar issue with VMware esxi 4.1 and another brand of NAS NFS.

So rather than recreate a whole thread I will add the solution on to this one.

Some NAS NFS standalone servers may have their NFS access permissions set to their same domain name.

for example:

NAS NFS share named: NFSVOLUME
may have its permissions set to only allow mounting from: *.somedomain.com


if this is the case and the vmkernel network connection (ip address) you are connecting to the share from is *NOT* resolvable via the DNS server on the NAS NFS to a host within the allowed domain, the same or similar error message to the following will result:

"Call "HostDatastoreSystem.CreateNasDatastore"
"Operation failed, diagnostics report: Unable to complete Sysinfo operation"


This occurs because the VMWare esx/esxi host is not being allowed access to mount the NFS share by the NAS NFS server.


To FIX the issue:

Simply add the ip address of the vmkernel network (vmkernel network is the "vmk#" in esx/esxi 4.1) to the NAS' NFS permissions and it try again on the host and you'll see it will connect!

Alternatively, if you have your own DNS server running on your network, make sure the IP address of the vmkernel network (vmk#) that you are connecting to the NAS NFS share from is resolvable to a host and ptr record in the same domain as the allowed domain permission on the NAS NFS share.

Hope this helps anyone that encounters this issue,


-redsi

0 Kudos
Highlighted
Contributor
Contributor

I have a N4100 PRO and for the life of me, I cannot get this thing to work.  /raid0/data/VM is the NFS mounting location  The NAS has a reservation in DHCP on my router.  I've updated the /etc/hosts file and proved to be pingable to both of my VMHOST machines.  I've put /nfs in front of /raid0.... as a forum suggested, I've paid very particular attention to case as LINUX is finicky.  I'm flat out lost.  I did configure 150 GB of the NAS to be ISCSI and that mounted w/o issue.  The concept is simply to be able to use the RAID 5 2.5TB of space availble (I've got it configured to only be 1.5TB) on the VM Share, as a storage location.  I have Esxi 4.1.  This has been a NIGHTMARE.  Any help is greatly appreciated.  I'm a NEWB to vmware, but I'm pretty on the ball with concepts so let me have it.  Thanks!

0 Kudos
Highlighted
Contributor
Contributor

Hi outdoorsman23,

What are your settings on the ReadyNAS? I have left my NVX and Duo pretty much on defaults, nothing checked for NFS on the shares.

Are you using IP addresses for the Server field? In other words, I'd fill it out as

Server: <ipaddress>

Folder: /raid0/data/VM (assuming that's actually the share name and not the path on the ReadyNAS--check what the NAS thinks the share name is)

Datastore name:

doesn't really matter.

--Ken

0 Kudos
Highlighted
Contributor
Contributor

Hi Ken,

Thanks for the response.  I should clarify - I have a Thecus N4100 PRO vs the Netgear; however, my issue of connecting NAS as a hardware storage device similiarly fails.  As far as the path, that is exactly as it is listed in the NAS under the NFS properties.  I'm still pretty lost on this - it could very well be a hardware compatiblity issue, I just really doubt it due to my inexperience with this particular setup/hardware.  Thanks for responding and let me know if you have any more ideas Smiley Happy

0 Kudos
Highlighted
Contributor
Contributor

Thank you for your posting. That solved my problem by adding the ip address to nfs server's /etc/exports file. I tried to use both ip and hostname before, but did not noticed it was not allowed for dup entries.  After I correct the syntax, the NFS datastore was created successfully.

0 Kudos
Highlighted
Contributor
Contributor

I had the same problem, I resolved to downgrade the firmware to version 4.1.4 readynas1100
time and 'ok.
Hello

0 Kudos
Highlighted
Contributor
Contributor

Probably everybody has solved this problem by now, but the steps to add a NAS NFS volume to ESXi are:

1. Make sure the NAS is reachable, ping the IP adress

2. Check the time settings on the NAS. Time and date should be equa to the ESXi

3. Check if the NFS service on the NAS is enabled (THECUS has this service disable by default)

4. Find the storage settings and enable NFS on the folder you want to mount (Host name: *, writable, OS Support etc). The string to mount this folder is often displayed here also (example for the new Thecus firmware: raid0/data/_NAS_NFS_Exports_/VirtualMachines)

5. Add the NAS to ESXi, use the IP adres in the server field if the NAS is not in the DNS and the string as folder name.

That should do it...

0 Kudos