theonlydude1

Hello, I'm facing the exact same issue (no fan after a reboot until I click on Detect button to force it to start even if the plugin is in working state). Anybody was able to find a solution ? Thanks

Thanks ! I'll wait for the next update so.

Yes you are correct. No issue after a full reboot of my unraid server, just when I perform a stop / start of the array

Hello, I've made more testing on my side and my issue wasn't due to the array operation but to fact that I had to stop and start the array for adding my disks. I can reproduce the issue just by doing a stop / start on the array. To restore the access, i need to restart the NFS server service on unraid with the command: usr/local/etc/rc.d/rc.nfsd restart This behavior is expected ?

On unraid side the share is visible, seems to run fine and my array is started. NFS export is set to yes and security is set to public But from my ubuntu server (or from macOS) I'm not able to parse it, to unmount it or to force mount it

Hello, Maybe beginner question here since I'm only using unraid for few days. I'm running unraid 6.12.11 with, until recently, a simple array with 1 cache disk and 1 TB drive. All my data are access throught NFS from an Ubuntu 22.04 server with no issue. My NFS configuration from unraid is the standard one (I've just activated support for hard link). I've bought 2 new disks to serve as parity drive and to extend the global capacity. I've follow-up the documentation to add the parity drive first (stop array, plug drive, assign drive to parity and start array), and during the whole time of the parity drive creation my NFS share was not accessible from my ubuntu server. Everything was green on unraid side (share visible, no change in NFS configuration, docker and VM running fine) but my data was unaccesible remotely. Once the parity drive finished to be fully configured, a restart of my server gibe me back access through NFS. I'm now in the middle of the second drive implementation (as data drive) and... issue is back. On client side, my NFS mount configuration is really simple: 192.168.x.x:/mnt/user/data /media/UNRAID/data nfs defaults 0 0 (used nfs version is 4.2) but when I try to umount or mount again the share, I face a never ending operation. Did I miss something ? Is it an expected behavior from unraid ? Thanks ! tower-diagnostics-20240719-1320.zip