Sonarr version (exact version): 126.96.36.19952
Mono version (if Sonarr is not running on Windows):188.8.131.52
OS: FreeBSD 11
Debug logs: NzbDroneErrorPipeline Invalid request Validation failed: – Folder is not writable by user sonarr
Description of issue:
Sonarr is running and has been working perfectly fine with local storage. However, i used mount_smbfs to mount files that are stored on another network device that I would like sonarr to manage. This is the command I used:
mount__smbfs -I 192.168.1.55 -f 777 -d 777 //guest@NAS/dlna /mnt/NAS
I have entered the CLI and verified that all of the files and directories on the SMB share are accessible by using touch and nano etc. At least from the shell, I can write the files. These are the permissions for the directory: drwxrwxrwx
and for the files: -rwxrwxrwx
That indicates that anyone should be able to write.
In sonarr, I can navigate the directory tree, so it can at least see all the directories. But for some reason, sonarr insists it can’t write.
EDIT: As a test, changed the completed folder for sab to the same smb share I’m trying to get to work with sonarr. Sab was able to extract files to that folder–so we know that the folder is writable. However, sab had some problems with moving/renaming on the share, which I think is because sab tried to rename the files too quickly. I can recreate this by touching a new file in the CLI and then immediately trying to remove it; I need to wait a second before trying to remove it. It’s possible that this particular NAS device is a little slow, which is fine and I accept. Is it possible that the way sonarr checks whether something is writable is related to this? And if so, how do I solve? Or is this totally unrelated and is it just a sonarr glitch?
I guess I include this information just to confirm that the smb share is correctly mounted, with correct permissions.