Unraidmule

I’ve been running this for three days but it’s only keeping the files which are on the txt file when I executed the script manually. Is the text file meant to be created in the script dir or another location? How do I check if the mover tuner plug-in has permissions to execute the ignore script? EDIT: I used chmod +x command then tested mover manually, and I think now the .txt file is being created. Is this the correct command, or is there a safer way, so only root can execute the script?

I fixed the line endings, I realized that was causing the error of the script executing. I have 3 different clients, so I am still figuring out how to get them to pause the torrents which only need to be moved and then resumed after the move.

I only set up the cache drive today — before downloads were going to array directly, so I really don't have a method to pause torrents yet. I will have to look into this as I never really pause torrents and keep them seeded permanently, and I don't really know how to modify the script, unfortunately. I tried to run the script manually with two files inside the cache and got this result: The data dir exists on the cache now IDK why it can't find it and returns that it does not exist. Also, I use hard links — this is how I permanently seed all torrents. Using a cache drive will cause a big issue?

If torrents are actively being seeded, can you safely run this script? Or do they need to be paused, moved and resumed?

Possible to add this Multithreaded PNG optimizer written in Rust https://github.com/shssoichiro/oxipng

Thanks for the reply. Will test out removing those parameters completely. With the script and changing to folder structure I got my writes from ~5 GB per hour to ~2 GB per hour. Is there a solution to reduce it further like having some appdata in RAM disk which also syncs back for chatty dockers like the arr apps?

If anyone reads this, using the solution Kilrah mentioned here: I got the writes down to around ~2 GB per hour

Thanks for pointing that out to me, just checked the go file, and I'm using: RAM-Disk for Docker json/log files v1.6 for 6.12.5 I will upgrade to latest and report back! I really appreciate the help Kilrah. EDIT: Ran the latest script and found these two in the syslog Before starting docker: Tower kernel: RAMDISK: [mem 0x64b36000-0x6689ffff] After starting docker: Tower docker: RAM-Disk created So it looks like the script is working now. Thank you for all the help! Will report back with TBW once I give it enough time. I have some extra parameters on some containers I tried as a solution before this script, for example: --log-driver none --no-healthcheck --mount type=tmpfs,destination=/tmp,tmpfs-mode=1777,tmpfs-size=256000000 --log-driver syslog --log-opt syslog-address=udp://127.0.0.1:541 --no-healthcheck --mount type=tmpfs,destination=/tmp,tmpfs-mode=1777,tmpfs-size=256000000 Should they be removed so they don't interfere with the script?

Yes I upgraded to version 6.12.10 before trying this mod.

Thanks for the reply, I checked the syslog and found an error: docker: Error: RAM-Disk Mod found incompatible files: 8d6094c1d113eb67411e18abc8aaf15d /etc/rc.d/rc.docker 9f0269a6ca4cf551ef7125b85d7fd4e0 /usr/local/emhttp/plugins/dynamix/scripts/monitor IDK how to fix the issue or why it is occurring.

I am testing this on Unraid v6.12.10 What is the best way to know if it is working as intended or functioning correctly? Just log SSD usage using power on hours and the TBW? That's what I have been doing at the moment. Thank you for this!

I set a limit on the qBit containers, but they crash internally which is very bad — creates ghost peers and wiped out my upload stats that are not registered due to no announcement

I will test the script on v6.12.9 of Unraid OS. Is there anything I should change before using it so I don’t have any compatibility issues?

Thank you so much for the reply. This looks promising! Does it work on Unraid OS v6.12.9? Or the latest? Currently, I am on v6.12.9

Does anyone else have any suggestions to fix the issue?