ReadyNAS NV+ and VMWARE ESX NFS Share

Hahah this if funny because I thought I was the only crazy guy running ESX with the NV+ as my storage... OK Guys, here's the scoop with this error or it least my experience the last time this happened with me... nfsd was running but not rpcd on my ReadyNAS NV+ (RAIDiator 4.01c1-p1 [1.00a041]), even though my share that I setup was NFS. When I tried to mount this filesystem on my FreeBSD box, I would get an rpc time out error also. There isn't a way to gracefully restart a sub-system like NFS on the ReadyNAS because it usually just works. Would be nice if there was a process that monitored services and if one dies it tries to restart X times if it doesn't then log an error in the log that you can read under Health, Logs. I simple restart of my ReadyNAS via the web interface resolved the problem. On the ESX server, login via the console, become root so that all the esxcfg* commands are in your path and you can execute, then type: "esxcfg-nas -l" which will list all NFS storage containers you setup via the VIC. IE:
[root@flyingZ root]# esxcfg-nas -l
Falcor is /artax from 10.0.0.31 mounted

If the filesystem is failing to mount, you'll see "unmounted" instead of "mounted". You can type: "esxcfg-nas -r" to attempt a restore of the NFS volume/container but remember ESX 3.x* will continually retry mounting automatically so you should never really have to run this.

Anyway, bottom line is I installed the SSH component on my ReadyNAS NV+ and 'ps' for rpc and nfsd, only nfsd was there, after a gracefull reboot of the ReadyNAS+ both processes were there running:) and my ESX automatically remounted all is good.

L8r!
Gecko