November 9, 201312 yr I'm trying to set up an unRAID share as a NFS datastore is ESXi. but I 'm having some connectivity issues. I can set it up ok and works fine, however, when I re-start the array, it stays grayed out and shows as 'inactive' on the datastores list. If I do esxcfg-nas -l from the console I get: ~ # esxcfg-nas -l nfs.backup is /mnt/user/backups/esxi.backup from 192.168.1.160 mounted unavailable Any ideas on how can I make it available again? And why it doesn't reconnect automatically? I have a ZFS server (NAS4Free), and nfs shares do reconnect automatically on startup?
November 20, 201312 yr I use FreeNAS as my NFS store and it reconnects as soon as that VM comes up. I've never tried unRAID as a VM store but I thought that NFS was pretty stable on unRAID. Weird that ESX can't reconnect... Sent from my iPad using Tapatalk
November 20, 201312 yr Author I've stopped trying to get this to work. My VMs are served from NAS4Free with no issues so far. I then created a script that once per week mounts unraid, backs up the VMs (with ghetto VCB) and unmounts the share. Not the most elegant solution but it works! Sent from my GT-I9305 using Tapatalk
November 20, 201312 yr I'm trying to set up an unRAID share as a NFS datastore is ESXi. but I 'm having some connectivity issues. I can set it up ok and works fine, however, when I re-start the array, it stays grayed out and shows as 'inactive' on the datastores list. If I do esxcfg-nas -l from the console I get: ~ # esxcfg-nas -l nfs.backup is /mnt/user/backups/esxi.backup from 192.168.1.160 mounted unavailable Any ideas on how can I make it available again? And why it doesn't reconnect automatically? I have a ZFS server (NAS4Free), and nfs shares do reconnect automatically on startup? Working fine here. I have several NFS shares created via unRAID webui. ~ # esxcfg-nas -l Apps is /mnt/user/Apps from 192.168.0.3 mounted available Downloads is /mnt/user/Downloads from 192.168.0.3 mounted available store2 is /mnt/user/vmdk_datastore from 192.168.0.3 mounted available vmbk_array is /mnt/user/Backups from 192.168.0.3 mounted available vmbk_usb is /mnt/disk/SeagateExt/VMBK from 192.168.0.3 mounted available Never had ESX see them as unavailable after an array restart. Saying that, I did, but that's because the last share in the example above points to a location on an external USB drive mounted via SNAP and as it's not managed from the stock unRAID webui, I had to edit /etc/exports file myself. Then I realised I should be editing "/etc/exports-" as this is used as the template every time NFS is restarted (like during an array stop/start) and /etc/exports was being re-created with just the unRAID defined NFS shares, causing my manually added entry to disappear. Now I just have an exports- file on my flash and an entry in my go script to overwrite the stock /etc/exports- file upon unRAID reboot.
Archived
This topic is now archived and is closed to further replies.