Slystuff

I know this is quite some time later, but just wanted to thank @warwolf7 for detailing the steps that they had taken for this. I recently replaced my cache drive, though in my case it was a 1 for 1 replacement, and afterwards was seeing the same disk spin up issues that Warwolf was despite the likes of Docker being disabled, appdata etc being purely on the cache drive. I stumbled upon this thread though and was able to see the same issue with calls for a btrfs uuid that wasn't valid would occur when the disks would spin up. Likewise the uuid that was being called showed in the config file for the cache pool, since updating the config file to remove that everything is now back to running as expected with drives spinning down, and staying spun down until actually in use.