I may have figured it out.
My mount seems to have stopped reconnecting after reboot. I guess that’s easy to miss (for me) if you are just browsing the folder structure via ssh gui. Everything was still showing up but not actually mapped to the network drive.
I ran a “sudo mount -a” and got error 2 (No such file or directory) opening credential file /.nascred
The password file I was using stopped working.
I put the username and password into the actual string and rebooted.
Fixed that problem but got another one something like “can’t write to data directory”
Which lead me here:
I ran some chown 777 commands and got this error:
Please change the permissions to 0770 so that the directory cannot be listed by other users
Eventually I found this:
I changed my fstab to this replicating some examples other people have posted. Nextcloud loaded up fine with no GUI errors.
//172.30.1.111/DataA/NextCloudData /mnt/nasdata cifs username=nasuser,password=nasuserpassword,uid=33,dir_mode=0770,file_mode=0666
It’s probably better to use an NFS share rather then SMB from the NAS but that’s what I had setup already.
From my laptop I can open the Nextcloud “app” and create a new folder and I see it populate over to my NAS location. However if I UNC to the NAS data location and create a folder it doesn’t populate into Nextcloud - but I think that is expected behavior.
I need to try it with some test users and see if the folders / permissions are actually working. But so far, much better.