skallox

Thank you for digging into my diognostis. I linked that excerpt in my inital post with the below image showing it marked as automount. So, circling back: Am I missing something? Would using the User Scripts plugin to mount it be an appropriate way to bandaid this issue?

Confirmed UD is the latest version, still no automount. Fresh diagnostics after reboot below.skallox-diagnostics-20210307-1211.zip

Hello! I'm struggling to get my scratch disk to automount on boot via the unassigned device plugin. It seems like this is a standard usage but it isnt quite working for me. I'm not sure what "mountpoint 'temp' is not set to auto mount." means in this context. I believe I have filled out all the sliders properly. Is the intent that people do a script to mount via fstab? Am I missing something? I've already been burned once by treating Unraid like a bog standard linux distro so I am gun shy of trying to punch my way through this problem with general linux knowledge. Cheers!

#EDIT# For those who come here seeking answers, just use the GUI. Set your rule in the NFS set up for each share. It isnt worth the struggle. #/EDIT# Hi Everyone, I'm coming from freeNAS and need to get my Unraid NFS setup to match the old FreeNAS one so compatibility is maintained with my Proxmox host. I have authored an /etc/exports file the works but am having issues making it persistent. I have copied my good exports setup to /boot and setup up /conifg/go to copy the file over /etc/exports. My understanding is that 'go' is initiated towards the end of the start up process and I seen not errors in the log. When I do a quick tail /etc/exports after the machine is restarted the file is in its default state. I can't tell if it is working or not but I'm showing the content of 'go' below. To try and determine if 'go' was the issue I installed the User Scripts Plugin and set up the below script to run at first array startup. I confirmed it was running successfully however /etc/exports still showed the default content. The logs show it ran at 12:12.34 when I did a restart test. Checking the logs it looks like the default NFS server daemon started at 12.12.30 based on when exportfs -r ran.. so the User Script ran after the daemon was started but something must have reset the contents of /etc/exports. When I run the script manually it works perfectly but it seems like something randomly turns on and overwrites export back to the bog standard file. Has anyone ever ran into this? Is there part of operation I'm missing that takes the disappointing GUI driven NFS settings and periodically rewrites them to the export file? Why wouldn't Unraid just have an "NFS Extras" entry in the GUI like they have for SMB? I would appreciate any insight the fine people of this forum can offer.