May 11, 20251 yr I have 2 questions. After I did the upgrade a couple things changed. 1. everything seems slower. I first noticed when I tried to connect to my plex from another computer not on my network, away from home. Seemed slower. Downgraded to 6.15 and seemed faster. 2. See the attached picture. I had this message when I went into fix common errors to see what was slowing me down. There is no more cache only setting so that is throwing me off. I just installed appdata backup plugin, after seeing this. So how do I get rid of this? I want my selected appdata and flash to backup on my cache since that is external and saved me last week from a big issue. I use NVME cache for my file transfers. Like to see if I can figure this out before upgrading to 7.2 Actually thinking of rolling back to 6.15. Thanks folks tower-diagnostics-20250511-0941.zip
May 11, 20251 yr Community Expert To fix the cache only setting you just set the “Primary Storage: Cache” and leave secondary storage set to none. this makes it “cache only” it just seems that fix common problems has not been updated to match the current version nomenclature. However the advice is still relevant.
May 11, 20251 yr Author MowMdwon..Thanks for the reply I've done that setting a couple of times using the logic you confirmed for me. Thanks for that. However, still getting the same exact warning. So, are you saying not to worry about the warning since it the fix common problems nomenclature hasn't updated? Edited May 11, 20251 yr by isrdude clarification
May 11, 20251 yr Community Expert You have appdata located on disk3, you need to check it and move it to the cache pool. (because this says "yes" and not "only" here you're getting the appdata error in FCP.) appdata shareUseCache="yes" # Share exists on cache, disk3 Set secondary storage back to "array" and then set mover action "Array -> Cache" and run mover AFTER you stop docker service entirely. this should fix it. If mover does not move the data there is likely duplicate data on the cache pool already and you will have to figure out which copy is correct. Otherwise set the secondary storage back to "none" and ignore the error or rescan problems and it should go away. Edited May 11, 20251 yr by MowMdown
May 12, 20251 yr Author Took some time but that did the trick. Thanks Mow! Now I hope the speed issue goes away. Not holding my breath though!
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.