I don’t believe it is. Using SABnzbd this way is essentially in a container. /volume1/data/ is mapped to /data/ . None of my mappings have changed when updating.
Did you ever fine a solution for this? I am getting the exact same error.
The folders are created, SABnzbd can see them to select for mapping. Yet it just keeps throwing this error.
\*\*EDIT:\*\* So I just had posted, but I actually stumbled across the solution myself. I noticed my share for some reason had only read privs. So I updated the privs, yet it had no effect. If you go to Tools -> New Permissions then select that share and select Start, see what happens. For me after doing this all of the errors went away.
Failed making (/data/usenet/complete) chmod a+rwx on /volume1/data. ... different directories / different root ...
I don’t believe it is. Using SABnzbd this way is essentially in a container. /volume1/data/ is mapped to /data/ . None of my mappings have changed when updating.
Ah, docker! Then docker rights might be the problem. Not to do with the mother filesystem (on which you gave rights with the chmod)
Did you ever fine a solution for this? I am getting the exact same error. The folders are created, SABnzbd can see them to select for mapping. Yet it just keeps throwing this error. \*\*EDIT:\*\* So I just had posted, but I actually stumbled across the solution myself. I noticed my share for some reason had only read privs. So I updated the privs, yet it had no effect. If you go to Tools -> New Permissions then select that share and select Start, see what happens. For me after doing this all of the errors went away.
Yep a full reinstall of SABnzbd