Sonarr - Import failed, path does not exist or is not accessible by Sonarr

[pina]

I tried the step by step, and they lost me when they started the too many terminal commands So I just used the automated script and it works now

The reason why I didn’t do it in the first place is that I don’t like that structure very much. So I will try to alter it step by step now. The second reason is also that I like to be in control of what’s going on. The config has been done but I can’t replicate the steps by myself. But it’s good to know that I have a working config now and I will try to figure out how to alter it myself because I still want to know what went wrong. People doing this kind of stuff just like to understand what’s happening instead of getting it done by an automated script. At one point, we just give up and are forced to that script So I understand @AviatorTim’s concern.

I think it’s also very important to state the in nzbget you still have to add a command at the unpacking section: ${AppDir}/unrar x -ai Otherwise, the permissions will inherit them from the original file and not from the default group permissions

[AviatorTim]

@pina, I’m glad you also got it working. I came back to tell you how I got it working for me but I see you got it worked out.

I ended up giving up on the Docker install option and using the more automated install from the SynoCommunity. That had it’s own problem with SkyHook not being able to add series but I was able to resolve that by downloading an updated SSL certificate for Mono which was an easier solution that starting from scratch as @fanboy suggested.

@fanboy, I understand your point of view. I don’t fully agree with you but I appreciate your willingness to help others and I hope there’s no hard feelings.

To answer your question, I ran a script that made my Synology email me my PUID and PGID and they were the same as the guide I initially followed.

To answer your bigger question, I finally found someone who was willing to help me and, as I suspected, it was fixed in under two minutes. I get your point of view that Forums are only for “a gap in a guide”. Respectfully, I just see it differently. If I see my neighbor trying to shovel snow from his driveway from his wheelchair and it’s going to take him all day long to do it. If I can do something in 10 minutes that will take him hours, I go do it for him, not because he’s not capable of doing it but rather because I am able to do it so much more efficiently than him because I have an advantage in one particular area (physical). If he, in turn, has an advantage in one particular area of life (like computer knowledge) and he can fix something for me in 10 minutes that I’ve been struggling with for days, then maybe he’ll pay it forward. It’s a circle-of-life kind of thing in my humble point of view.

[AviatorTim]

@pina - which script are you referring to that fixed it for you? Time permitting, I may try to get the Docker version working.

Is that the install you worked out in the end? Or did you use the SynoCommunity install and fix the SkyHook problem with the script?

[fanboy]

Well, there’s working and there’s working. From what I understand from other posts, the Synocommunity stuff is sorely out of date and poorly maintained. Looks like the most recent version available is nearly one year old (Version 20210329-19 Update Sonarr to v3.0.5.1144.) So while things may now be up and running for you, it’s likely not an optimal setup. Getting Docker working will serve you better in the long run. And is possible by following the guide. Or using the automated script in the guide, which seems to have worked for @pina.

So the help you received that fixed it for you was someone telling you to run something automated to set it all up for you? Which is something I also suggested initially I might add. So that doesn’t really fit your analogy at all. They didn’t work with you or look through all your setup and config to troubleshoot where your settings were wrong. They didn’t do it for you because you were struggling to do it yourself. They told you to do it a different way that will do the bulk of the work for you. That’s not shoveling your driveway for you, that’s telling you to use a driveway shoveling service that will do it for you.

I agree with the pay-it-forward mindset, and I agree with wanting to learn and understand and do it for yourself. I’ve been helped plenty of times, which is why I take the time and effort to try and help in return when I’m able. But that’s after any otherwise readily available help has already been used. In this instance, that would be the rather meticulous guide that has been created.

I hope you will give Docker another try, and when you do (since you will now be starting from scratch?), follow the guide and you should be fine in the end.

As an aside: good to know about the PUID.So it was just a coincidence, or perhaps a Syno thing.

[pina]

@AviatorTim, I used the automated script in the link @fanboy provided us. Then I reversed engineered it step by step to try to make my own customisations. So as far as I understand, docker needs 1 common folder for their containers in order not to make it too difficult. So it created for me their structure f.e :

Data

• Usenet

  • tv
  • movies

• Torrent

  • tv
  • movies

• Media

  • tv
  • movies

I changed the structure slightly while remaining thie overall structure:

Media

• Downloads

  • Usenet

    • tv
    • movies

  • Torrents

    • tv
    • movies

• Media

  • tv
  • movies

I changed it step by step to make sure that I could take a step back when encountering an error.

[pina]

But I encountered strange behaviour. While new tv shows I started importing from scratch into sonarr imported flawlessly, I still got the problems with existing folders form tv shpows created by my previous sonarr setup. I think it’s because the owner was another account: the default sc-download group.

My manual fix was to delete the entire show, move the files to a temp folder sonarr has fully access too, and move them from that location. I did it a few times, because it just occured 2 times I don’t think I have to worry that all my shows need to be imported again…

I had a spiderman movie which I was monitoring from last year by radarr. So the folder was created a year ago. When the file was imported into that ‘old’ folder, I got the permission error. But when I deleted the older folder and removed it from radarr and added it again on radarr, the file could be imported. Just because radarr created the folder again with that setup.

[fanboy]

Almost certainly permissions related, yes. How to fix is covered in the guide (but involves the CLI which you mentioned earlier in the thread you got lost when trying to follow).

Since you were able to figure out a fix/workaround and it seems like it is only isolated folders and not the bulk of your library, you should be fine leaving it at that and doing the same thing if you encounter any further instances.

[pina]

ow, I just saw this in the guide:

If you copy files from a different library into the newly created library, you need to rerun these commands. !!!

sudo chown -R docker:users /volume1/data /volume1/docker

sudo chmod -R a=,a+rX,u+w,g+w /volume1/data /volume1/docker

[fanboy]

Because you used the script, your user should be the same, but because you have since changed your data structure, you would need to change the commands to match.

[pina]

that was clearly the missing link

@AviatorTim I suggest you trying the same thing as I did, just run the script, make sure everything has been setup and tested and after that, try to reverse engineer it step by step and alter things like you want but not too much. In the end you read the tutorial step by step again, then everything makes much more sense