January 19, 20251 yr I’m running a media server and setup everything and had to all running smoothly. I then decide to add my cache drive to my data share to speed up writing and moving files around. Doing this has now caused qBittorrent to throw file permission errors. Has anyone else had this problem before and how did you get past it? I spent a few hours trying many things to no avail. Any help will be greatly appreciated.
January 19, 20251 yr Author I'm running 7.0 4x 12TB HDD in Array with XFS. 2x 1TB SSD as Cache Shares appdata = cache only (not sure if it was array) data = cache and array (was array only) docker = cache only (was array only) standard dockers installed for media server. sonarr, radarr, qbit, plex etc. It was all working fine. Spent a few days on it, reading watching videos etc. I was so happy with it. Love unraid, love how my new media server was working for the family, pretty impressed overall. Then, after some bulk file copies to my data share were complete I added my cache to the data share as cache > array. After that, qbittorrent just gives file permission errors only. It's as if it doesn't have permission to write to the share anymore. I've looked at the share permission on the array and the cache and all seems normal to me with read&write. I've reinstalled the docker with the exact same config as before, I took a screenshot, still no different. I removed the cache from the data share, still the same errors. I've since put the cache back into the data share as removing didn't fix the issue and resolving the problem with it in is the preference. Please let me know what other info I can provide. Happy to jump into a voice/video chat with remote access if someone has the time to assist.
January 19, 20251 yr Community Expert 1 hour ago, bdherring said: qbittorrent just gives file permission errors only Can you post the exact text or screenshot of that?
January 19, 20251 yr Author Error in qbittorrent is; File error alert. Torrent: "***filename***". File: "/movies-4k/***filename***". Reason: "***filename*** mkdir (/movies-4k/***filename***) error: Permission denied" I have replaced the actual filename with ***filename***
January 20, 20251 yr Author Here it is; docker run -d --name='qbittorrent' --net='mediaserver' --pids-limit 2048 -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="OptimusPrime" -e HOST_CONTAINERNAME="qbittorrent" -e 'PRIVOXY_ENABLED'='false' -e 'UNBOUND_ENABLED'='false' -e 'VPN_ENABLED'='false' -e 'VPN_CONF'='wg0' -e 'VPN_PROVIDER'='generic' -e 'VPN_LAN_NETWORK'='' -e 'VPN_EXPOSE_PORTS_ON_LAN'='' -e 'VPN_AUTO_PORT_FORWARD'='true' -e 'VPN_AUTO_PORT_FORWARD_TO_PORTS'='' -e 'VPN_KEEP_LOCAL_DNS'='false' -e 'VPN_FIREWALL_TYPE'='auto' -e 'VPN_PIA_USER'='' -e 'VPN_PIA_PASS'='' -e 'VPN_PIA_PREFERRED_REGION'='' -e 'VPN_PIA_DIP_TOKEN'='no' -e 'VPN_PIA_PORT_FORWARD_PERSIST'='false' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='002' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8080]' -l net.unraid.docker.icon='https://hotio.dev/webhook-avatars/qbittorrent.png' -p '8080:8080/tcp' -p '6969:6969/tcp' -p '6969:6969/udp' -v '/mnt/cache/appdata/qbittorrent':'/config':'rw' -v '/mnt/user/data/torrents/':'/data':'rw' --hostname=qbittorrent.internal --cap-add=NET_ADMIN --sysctl="net.ipv4.conf.all.src_valid_mark=1" --sysctl="net.ipv6.conf.all.disable_ipv6=1" 'ghcr.io/hotio/qbittorrent:latest' df70cefae02533146a18f1929ece18c85276d878a9286f56aeb2f3c6923df467
January 20, 20251 yr Community Expert I don't use that container, but it seems to me there isn't a mapped path to /movies-4k. Any idea why the application is trying to use a path that begins /movies-4k ? You have a user share named data. Does it have a folder in it named movies-4k?
January 20, 20251 yr Author Correct. Well there is a folder “torrents” inside “data” and then “movies-4k” inside that. Same with “movies”, “movies-kids”, “tv”, “tv-kids” etc. All were working fine. I’m using categories in qBittorrent. It was smooth with a number of different categories and folders. Prior to adding the cache drive to the share that is. I also tried linuxserver container and getting the same error. Edited January 20, 20251 yr by bdherring
January 20, 20251 yr Community Expert Solution So that means the movies-4k folder has host path /mnt/user/data/torrents/movies-4k. The container folder /data is mapped to the host path /mnt/user/data/torrents. So, in the container, the path to the movies-4k folder would be /data/movies-4k, not /movies-4k
January 20, 20251 yr Author Ok I’ll give that a try. It’s just odd because it was working. I think I tried it like your suggestion before but it created like /data/data/torrents/movies-4k type of scenario. so I figure the /mnt/user/data/torrents was the root host path so I just put /movies-4k and it started working. I had 19 torrents successfully downloaded and pulled into plex via radar/sonarr etc. and I didn’t change anything regarding the paths. All I did was add the cache drive to the share. But, leave no stone unturned, I will try and report back soon. Maybe I changed some pathing and don’t remember 😆 It’s definitely possible.
January 20, 20251 yr Community Expert 2 minutes ago, bdherring said: so I figure the /mnt/user/data/torrents was the root host path so I just put /movies-4k and it started working. Since /movies-4k begins with a '/', it would be a root folder in the container, which is not mapped to the host. It might make sense to use movies-4k without the '/' As I mentioned, I don't use that container so maybe something else going on. In the applications Download Options, what do you have for Default Save location?
January 20, 20251 yr Author You did it mate. Crazy because I'm 99.99% certain I didn't change the paths. All I did was add the cache to the share. However, I did also do some updates to the apps. So maybe that changed something IDK. Ty mate. Solution was using \data\folder as the container path for the category. So simple. MB and thank you again.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.