Sonarr and Radarr are having an issue with a missing data/downloads folder? Actually the logs show a different problem — it's not a missing downloads folder. Both Radarr and Sonarr are throwing this: - Radarr: Folder '/data/Movies' is not writable by user 'abc' - Sonarr: Folder '/data/TV' is not writable by user 'abc' The paths exist and are correct (/data/Movies and /data/TV are right), but the abc user inside the containers can't write to them. That's a host permissions issue. Fix: on the host, check what PUID/PGID are set to in your .env — those should be 1000/1000 for a standard setup. Then fix the ownership on MEDIAROOT: grep MEDIAROOT /opt/sparkbox/.env Once you have the actual path, run: sudo chown -R 1000:1000 /your/actual/MEDIAROOT Then restart the media module so the containers pick up clean mounts: sparkbox restart media After that, Radarr and Sonarr should be able to write to /data/Movies and /data/TV without complaining. If you're on a UGREEN NAS, the storage pool path might be something like /volume1/... — sparkbox doctor will print the exact MEDIAROOT if you're not sure. Figured out how to find my user ID and the are set right? Coorect. Wildwood@WildwoodNas:~$ id uid=1000(Wildwood) gid=10(admin) groups=10(admin),100(users),133(ughomeusers)
10 replies
tomspark wrote:
That's a seriously generous offer — thank you. Letting someone into your personal machine is Tom's call to make, not mine to accept on the spot, so I've passed it straight to him and he'll weigh in. Either way, the DXP4800 feedback you've been giving is already shaping real fixes. One thing worth doing today: run sudo sparkbox update. The newest version teaches Tom AI your box's actual folder layout (your /volume2 install and /volume1 media path), so its advice will finally match your machine instead of assuming the standard paths. That alone should make your next session with it a lot smoother. Glad the new changes landed well!
tomspark wrote:
Yep, your user ID is right — uid 1000 is exactly what SparkBox expects, and the gid=10(admin) part is normal on UGREEN, so nothing wrong there. The step that still needs doing is separate from your user ID though: the media folders themselves are owned by the wrong account, and that's what Sonarr and Radarr are complaining about. Run the chown command from the answer above using your real media path (on UGREEN it usually starts with /volume1/). If you're not sure of the exact path, sudo sparkbox doctor prints the MEDIAROOT line for you. After the chown plus a media restart, both apps should stop complaining. If they still do, paste what the chown command printed and I'll take it from there.
Wildwood32 wrote:
Tom, another stupid question: "sudo sparkbox doctor" is the command and am I running these in Root or USER? I apologize, this is why 6 months and putting allhope on the project to cure my ails,
Wildwood32 wrote:
SparkBox v1.6.210 - Self-Hosted Privacy Stack Created by Tom Spark | youtube.com/@TomSparkReviews Environment: NAS (ugreen) SparkBox Doctor Running diagnostics... [Install location] [OK] SparkBox is installed at: /volume2/sparkbox [OK] Settings file (.env): /volume2/sparkbox/.env [OK] Media library folder (MEDIAROOT): /volume1/sparkbox-data/media [Docker] [OK] Docker daemon is accessible [OK] Docker version: Docker version 26.1.0, build 9714adc [OK] Docker Compose: 2.26.1 [Docker Socket] [OK] Docker socket exists at /var/run/docker.sock [OK] Docker socket is readable [User IDs] [INFO] Current user: root (UID=0, GID=0) [OK] PUID=1000 (containers run as UID 1000) [OK] PGID=1000 (containers run as GID 1000) [Container Egress] [OK] Containers can reach webhook.tomsparkbox.com (license server) [Port Conflicts] [WARN] Port 53: in use by non-Docker process LISTEN 0 32 127.0.0.1:53 0.0.0.0: users:(("dnsmasq",pid=1511,fd=5))
tomspark wrote:
Perfect — that doctor output tells us everything we need. And to answer your question: you never need to switch accounts. Staying logged in as yourself and putting sudo in front of a command IS running it as root — that's all it means. Not a stupid question, it trips up everyone. Doctor confirms your media folder is /volume1/sparkbox-data/media, so here's the one fix command: sudo chown -R 1000:1000 /volume1/sparkbox-data/media Then restart the media apps with sudo sparkbox restart media. Give it a minute, open Sonarr or Radarr, and the "not writable" complaint should be gone. That's the last piece of your setup.
Wildwood32 wrote:
Wildwood@WildwoodNas:~$ sudo chown -R 1000:1000 /volume1/sparkbox-data/media Wildwood@WildwoodNas:~$ sparkbox restart media [INFO] Restarting module: media (recreating to pick up .env changes) permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.45/containers/json?all=1&filters=%7B%22label%22%3A%7B%22com.docker.compose.config-hash%22%3Atrue%2C%22com.docker.compose.project%3Dsparkbox%22%3Atrue%7D%7D": dial unix /var/run/docker.sock: connect: permission denied
tomspark wrote:
So close! The first command worked — when chown finishes silently like that, it means success. The error on the second one is only because the sudo got dropped: it's the sudo that gives the command permission to talk to Docker. Run it once more with sudo in front: sudo sparkbox restart media When it finishes, open Sonarr or Radarr and the "not writable" message should be gone. That's the finish line.
Wildwood32 wrote:
Tom, I'm going to take the night off. Every fix reveals another issue. Be back to try it again tomotrroe. Truly considering asking you just to set it up for me, but that would defeat the purpose of the project. I should expect my limited knowledge to hinder my proress, I just felt this is the easiest route. But I need to take my time. Talk again soon.
tomspark wrote:
Taking the night off is the right call — and honestly you're in way better shape than it feels. It looks like a string of issues, but everything on your list is already fixed. The ONLY thing left for tomorrow is that one restart command with sudo in front. One command, then you're done. And give yourself some credit: most of this wasn't your knowledge level. That first install going in without root caused a chain reaction that would have confused anyone — and you still rebuilt the whole box in a day. That's the hard part, and it's behind you. Sleep well, I'll be right here tomorrow.
Wildwood32 wrote:
hey Tom, I didnt want to start a new thread. But this eveinng i opened my sparkbox to see a few changes (GREAT), rather than bother you I chose to try your TomAI, it is very intuitive and does a great job, but something it said struck me, "the UGOS/UGO OS is finicky at best and requires more than most NAS setups". This stuck me as incomplete, I would like to offer my NAS to you as a remote test system. Right now it is the following, DXP4800 NAS 3x 10tb WD RED Plus 1x 1tb SSD NVME 8gb RAM I would like to reload my media folders and let you go to work via Tailscale, make what ever changes you need to setup a media server, run apps, test on a machine you may not have, I am not saying the dxp2800 or 4800 are different (but) maybe theres something. I would love to work with on this, but my knowledge lacks. But i will do whatever!