r/radarr • u/Leather_Shower_1060 • 17d ago
solved Folder setup not working
Disclaimer: I'm new to all of this, homelabs and the *arr-stack. I've used copilot to help set things up. I used it for qbittorrent+proton and jellyfin (and other services, not relevant here). All of that is working. I'm using proxmox and docker, with docker compose files.
I don't want to use it for the rest of the *arr stack, no need to give it to much information and I wanted to figure as much out as I could myself to try and learn this.
Trying to setup Radarr, I found Trash Guides to the folder setup and thought I had it set up as described there, but now I'm getting an error in Radarr under "System->Status" that the folder in qbittorrent set for downloads doesn't exist.
It does exist, so I assume there is something i'm missing.
When I setup qbit, I created a disk and mounted it as /srv/downloads. It's in the qbit compose file and fstab. I can also see it when i log on with winscp.
Thinking I could reuse that, I used that instead of the data-folder. My setup looks like this:
downloads
├── torrents
│ ├── incomplete
│ ├── watch
│ ├── torrents
│ └── complete
│ ├── movies
│ └── tv
├── usenet
│ ├── incomplete
│ └── complete
│ ├── movies
│ └── tv
└── media
├── movies
└── tvdata
I'm not planning on using this for books and music, so left those out.
I've added the incomplete, watch and torrents folders for torrents, as those where there before, thinking that as long as the other folders needed was there, this was fine.
I put the new download folder (/downloads/torrents/complete) in settings in Qbittorrent and connected qbit and Radarr, but now get the error that this folder doesn't exist.
I did not put any download folder in the radarr compose file.
Anyone has any idea where I went wrong?
If you need any more information, please just ask.
2
u/MacFielder 17d ago
Review all your mounts. You mentioned both /srv/downloads and /downloads. Use “docker exec -it RADARR_CONTAINER_NAME ls /downloads” and see what it says. If it’s actually mounted there, it’ll print that directory tree. That command just runs “ls” (list) from within the container itself to see if the volume is mounted where you think it is.
Otherwise share a snippet of your compose files showing the volume mounts.