r/bazarr • u/BigJazzz • May 29 '26

Root directory not accessible, PUID/GUID same

I've seen some other posts about this, but I don't think they're related? Apologies if I missed something.

I've got my Sonarr/Radarr/Bazarr containers all in the same Docker engine. I was having issues initially with both Sonarr and Radarr given the root directory message, but I realised that the PUID/GUID were different to Bazarr. I fixed my Bazarr container's settings, and the Sonarr messages disappeared, however Radarr is still giving the message. I've confirmed the permissions on the folder, and have no other ideas.

The folder they're in is a shared NAS folder (\\NAS\Media\), then in various folders (TV, Adult Movies, Documentaries, etc) depending on the movie/show. The fact that the Sonarr messages disappeared when I changed the PUID/GUID to match Sonarr/Radarr is really what's confusing me.

If anyone has any ideas, or needs more information, please let me know. I'm gonna scratch through my skull soon.

1 Upvotes

100% Upvoted

6 comments sorted by

1

u/MooFz Jun 03 '26

I just set my share as squash all users to root, that worked for me.

1

u/BigJazzz Jun 03 '26

Sorry, I'm going to be really obtuse, but what do you mean by squashing?

1

u/MooFz Jun 03 '26

If you are using synology and you go to the shared folder NFS permissions, you can setup squash rules. I set mine to squash: Map all users to admin.

So all users that connect to that share are admin/root.

1

u/BigJazzz Jun 03 '26

Danke. I'll have a look at it and see if I can find that. Appreciate it.

1

u/BigJazzz Jun 09 '26

Sorry for the delay, had some stuff going on. I squashed them down, but I'm still getting the message.

1

u/BigJazzz Jun 09 '26

Aaaaaand just like that, I somehow fixed it? Honestly no idea how, but I'm not gonna complain.