February 11, 20251 yr Posting this to document a "mover not moving" problem I was able to solve after reading similar threads. Updated to v7.0.0 recently; no obvious issues. I have two 1 TB NVMe BTRFS cache drives. Noticed yesterday (via sabNZBd) that cache drive pool was full. Tried to invoke mover manually; didn't seem to do anything. Hmm. Read some posts here that suggested a possible corrupted boot flash drive. Backed up flash, just in case. Ordered new flash drive. Read another post that suggested uninstalling Mover Tuning plugin. Uninstalled, reinvoked mover manually, and... success! Have now reinstalled Mover Tuning (newest version; there are somehow two different ones available in Apps "store"). Guess I can return the new flash drive I ordered... or maybe I'll hang on to it as a spare. Edited February 21, 20251 yr by Karyudo
February 18, 20251 yr Solution Just wanted to say that this post helped me. I was in basically the same situation except my cache pool is 2x2TB drives so it didn't fill up as fast as yours. After a few days of seeing notifications about the cache drive reaching high levels of utilization I started trying to figure out what was wrong and eventually I was lead here. My plug-in was still called "CA mover tuning" so it must have been very out of date.
February 19, 20251 yr I am so thankful that people like Karyudo exist in this world. You saved my bacon. ❤️
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.