Unable to mount unRAID NFS share to VMware


Recommended Posts

I'm trying to mount an NFS share as a datastore on ESX, but I keep getting an error.

 

Unraid NFS share set as follows:

Sharename: ESX_Datastore

Export: Yes

Security: Private

Rule: 172.16.0.3(rw),172.16.0.18(rw)  <- these IP's are the ESX and vCenter servers

 

When adding the datastore in VMware I am using these settings:

NFS Version: NFS 3 or NFS Version: NFS 4.1 (see below for corresponding error)

Datastore Name: Unraid_ESX_Datastore

Folder: /ESX_Datastore

Server: 172.16.0.4 <- unRaid server IP

 

If I choose NFS 3 the VMware error is

"An error occurred during host configuration.

NFS mount 172.16.0.4:/ESX_Datastore failed: The mount request was denied by the NFS server. Check that the export exists and that the client is permitted to mount it."

 

If I choose NFS 4.1 the VMware error is

"An error occurred during host configuration.

Operation failed, diagnostics report: Sysinfo error on operation returned status : Timeout. Please see the VMkernel log for detailed error information"

 

 

What is the correct version of NFS I should be using?

Am I doing something wrong?

Link to comment

Path should be IP:/mnt/user/ESX_Datastore

 

 

using a linux box with showmount -e $IP should show you all the exports if they have read access acl.

 

example:

root@raspberry:/orion# showmount -e 192.168.1.99

Export list for 192.168.1.99:

/mnt/user/vmbackup      *

 

 

Tim

 

 

 

I'm trying to mount an NFS share as a datastore on ESX, but I keep getting an error.

 

Unraid NFS share set as follows:

Sharename: ESX_Datastore

Export: Yes

Security: Private

Rule: 172.16.0.3(rw),172.16.0.18(rw)  <- these IP's are the ESX and vCenter servers

 

When adding the datastore in VMware I am using these settings:

NFS Version: NFS 3 or NFS Version: NFS 4.1 (see below for corresponding error)

Datastore Name: Unraid_ESX_Datastore

Folder: /ESX_Datastore

Server: 172.16.0.4 <- unRaid server IP

 

If I choose NFS 3 the VMware error is

"An error occurred during host configuration.

NFS mount 172.16.0.4:/ESX_Datastore failed: The mount request was denied by the NFS server. Check that the export exists and that the client is permitted to mount it."

 

If I choose NFS 4.1 the VMware error is

"An error occurred during host configuration.

Operation failed, diagnostics report: Sysinfo error on operation returned status : Timeout. Please see the VMkernel log for detailed error information"

 

 

What is the correct version of NFS I should be using?

Am I doing something wrong?

Link to comment

Thanks for your help Tim, I was able to get it mounted.  The showmount command was very useful in determining if the share was active after making a change in unRaid.  I found a bug in unRaid's NFS implementation, if you have more than one IP in the 'Rule' box the share is not active (eg: 172.16.0.3(rw),172.16.0.18(rw)).

 

I was only able to mount using NFS v3.  Below are my final settings for anyone else having trouble:

 

Unraid NFS share set as follows:

Sharename: ESX_Datastore

Export: Yes

Security: Private

Rule: 172.16.0.3(rw)  <- ESX server IP

 

VMWare settings:

NFS Version: NFS 3

Datastore Name: Unraid_ESX_Datastore

Folder: /mnt/user/ESX_Datastore

Server: 172.16.0.4 <- unRaid server IP

Link to comment

NFSv4 does not work at all, I recompiled the kernel to include NFSv4 support and found it slower then v3.

 

Tim

 

 

Thanks for your help Tim, I was able to get it mounted.  The showmount command was very useful in determining if the share was active after making a change in unRaid.  I found a bug in unRaid's NFS implementation, if you have more than one IP in the 'Rule' box the share is not active (eg: 172.16.0.3(rw),172.16.0.18(rw)).

 

I was only able to mount using NFS v3.  Below are my final settings for anyone else having trouble:

 

Unraid NFS share set as follows:

Sharename: ESX_Datastore

Export: Yes

Security: Private

Rule: 172.16.0.3(rw)  <- ESX server IP

 

VMWare settings:

NFS Version: NFS 3

Datastore Name: Unraid_ESX_Datastore

Folder: /mnt/user/ESX_Datastore

Server: 172.16.0.4 <- unRaid server IP

Link to comment

Thanks for your help Tim, I was able to get it mounted.  The showmount command was very useful in determining if the share was active after making a change in unRaid.  I found a bug in unRaid's NFS implementation, if you have more than one IP in the 'Rule' box the share is not active (eg: 172.16.0.3(rw),172.16.0.18(rw)).

 

I was only able to mount using NFS v3.  Below are my final settings for anyone else having trouble:

 

Unraid NFS share set as follows:

Sharename: ESX_Datastore

Export: Yes

Security: Private

Rule: 172.16.0.3(rw)  <- ESX server IP

 

VMWare settings:

NFS Version: NFS 3

Datastore Name: Unraid_ESX_Datastore

Folder: /mnt/user/ESX_Datastore

Server: 172.16.0.4 <- unRaid server IP

 

When NFS is set to private, a specific format is needed:

192.168.2.0/24(sec=sys,rw,no_root_squash,insecure) 192.168.1.5(sec=sys,ro,insecure,anongid=100,anonuid=99,all_squash)

 

Refer to http://lime-technology.com/forum/index.php?topic=38988.msg362847#msg362847 for more details:

Link to comment

My previous settings didn't work, I could mount and read the volume, but I couldn't write to it.  Ive added the NFS options as suggested and Read/Write are working.  Thank you both for your help.  Updated settings below.

 

Unraid NFS share set as follows:

Sharename: ESX_Datastore

Export: Yes

Security: Private

Rule: 172.16.0.3(sec=sys,rw,no_root_squash,insecure)  <- ESX server IP

 

VMWare settings:

NFS Version: NFS 3

Datastore Name: Unraid_ESX_Datastore

Folder: /mnt/user/ESX_Datastore

Server: 172.16.0.4 <- unRaid server IP

Link to comment

Please tell me how you make out, Unraid working with anything but a worm type workload has been terrible experience.  I love unraid for what it is, block storage is something unraid simply is not good at.  I use ghetto-vcb for vm backups from my ESX server and noticed the sleep function of the disks played havoc with ESX with no running workload attached and the dreaded nfs stale file handle caused issues too.  If your using unraid as a backup device i would recommend only having the NFS mount at time of backup, not using a cache disk your backup times will be pretty significant.

 

Tim

 

 

My previous settings didn't work, I could mount and read the volume, but I couldn't write to it.  Ive added the NFS options as suggested and Read/Write are working.  Thank you both for your help.  Updated settings below.

 

Unraid NFS share set as follows:

Sharename: ESX_Datastore

Export: Yes

Security: Private

Rule: 172.16.0.3(sec=sys,rw,no_root_squash,insecure)  <- ESX server IP

 

VMWare settings:

NFS Version: NFS 3

Datastore Name: Unraid_ESX_Datastore

Folder: /mnt/user/ESX_Datastore

Server: 172.16.0.4 <- unRaid server IP

Link to comment
  • 1 year later...

I have put it in public and I can not use it either.
Every time I'm going to write something through ESXI, it gives an error and disconnects.

Have you been able to solve the problem?

 


Copy Datastore File
Clave

haTask--vim.FileManager.copyFile-630902455
Descripción

Copia el archivo o la carpeta de origen al centro de datos de destino
Estado

Error - Error provocado por el archivo /vmfs/volumes/658bee17-658405af/Test2_2/Test.nvram.
Errores

 

Edited by Nebur692
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.