October 26, 2025Oct 26 As the title states, torrent downloads are failing when I have the cache set as primary storage, but when I have the array as primary storage it is working fine. All drives pass SMART tests and the cache drive is almost entirely empty. I have tried multiple docker torrent containers and it is not limited to just my primary client or to one docker author.
October 27, 2025Oct 27 Community Expert most likely Permission and share settings misconfiguration... not enouth data and info to diag nose... please post a unraid diag file...Make sure only primary is set...confirm your share settings...I prefer the linux server / linux IO transmission docker. lib torrent.https://docs.linuxserver.io/images/docker-transmission/ note the advance toggle at the top and show more...change UID and PID to 0 to use the root user.pre make the file paths on cache disk....mkdir -P /mnt/user/appdata/torrent-downloadcd /mnt/user/appdata/torrent-downloadchmod 777 -R *chown nobody:users -R * Edited October 27, 2025Oct 27 by bmartino1
October 27, 2025Oct 27 Author 1 hour ago, bmartino1 said:most likely Permission and share settings misconfiguration... not enouth data and info to diag nose... please post a unraid diag file...I would agree if not for the fact that it was working fine a few days ago and started acting up without any changes being made that I can think of. I upgraded to the latest RC update a few days before this issue started. A few weeks ago I redid my storage to match the TRaSH guides for automating everything and it was working great, in the multiple years I have ran Unraid I have never encountered this issue before. My torrent client of choice is binhex-qbittorrentvpn but I tried Transmission and Deluge with the same result. I have attached two diagnostics, one with the cache enabled as primary storage and array secondary, and one with only the array as the primary storage. As soon as I switched the share to array only I hit resume on a torrent for a Fedora Linux Silverblue ISO and the download worked instantly as an example. ARRAY ONLY-unraid-diagnostics-20251027-0002.zipWITH CACHE-unraid-diagnostics-20251026-2358.zip
October 27, 2025Oct 27 Community Expert thank you I will review the diags. I ahven't cehcekd out 7.2 RC or beta yet. ok following the trash guides as I asume you setting up or had a Ars system.did you edit or make changes for sym/hardlinks? -as this will afect how data can be stored access and messes with unraids fuse system underneath...https://trash-guides.info/File-and-Folder-Structure/Hardlinks-and-Instant-Moves/ https://trash-guides.info/File-and-Folder-Structure/How-to-set-up/Unraid/
November 2, 2025Nov 2 Author I didn't edit any of those settings when I did this recent change, I cannot remember if I adjusted it sometime in the past few years though. That said, after updating to the full 7.2 release the cache appears to be working, knock on wood.
November 4, 2025Nov 4 Community Expert whats the share setting and data at?When using cache it shas to be mover moving the files...?set it to your cache disk and set primary only for your cache setup...Otherwise check out and use a compose file...https://forums.unraid.net/topic/194760-dockers-fail-to-communicate-on-unraid-72/#findComment-1588190
November 4, 2025Nov 4 Community Expert Solution This is a known issue for some users with zfs as primary; 7.2.1 should have a fix. For now, you can do a zfs mount -a
November 7, 2025Nov 7 Community Expert 7.2.1-rc.1 is out, and it should resolve this issue, please retest.
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.