February 27, 20242 yr Sorry for being a newbie! I have a few docker containers running as well as a few shares. But im noticing the parity and the Disk 1 doesnt spin down. Im not sure i have unraid setup correctly to spin down and need some help. I have attached my diag file to maybe better help. Thanks unraid-diagnostics-20240227-1444.zip
February 28, 20242 yr Community Expert That is probably due to this: system shareUseCache="prefer" # Share exists on cache, disk1 Ideally you want all of this share to be on the cache to avoid keeping disk1 and parity spun up.
February 28, 20242 yr Author So to fix this i need to unselect the secondary storage and set to none?
February 28, 20242 yr Community Expert No, the settings in your screenshot are correct to get them moved off the array. But, nothing can move open files. You have to disable Docker and VM Manager in Settings before these can be moved. Then run Mover and post new diagnostics when it finishes.
February 28, 20242 yr Author Makes sense! I just ran it. Heres the latest log. unraid-syslog-20240228-0217.zip
February 28, 20242 yr Community Expert 22 minutes ago, brad2388 said: Heres the latest log That is not the diagnostics.
February 28, 20242 yr Author Does everything else look ok as well? As far as the cache drive and where stuff is stored?
February 28, 20242 yr Community Expert Solution 2 hours ago, brad2388 said: Does everything else look ok as well? As far as the cache drive and where stuff is stored? Most of your non-system shares are set to go straight to the array and not be cached. Nothing wrong wit this, but it does means write speed for new files will be limited by the overhead of updating parity.
February 28, 20242 yr Author Ok so if i wanted the files to go to the cache first id set the Primary storage to cache and the secondary to Array. Then have mover setup to move them say every 6 hrs? or every day? Im not using this daily. This is only for my NAS.
February 28, 20242 yr Community Expert 12 minutes ago, brad2388 said: have mover setup to move them Default mover schedule is daily in the middle of the night. Mover is intended for idle time. If you need to write more than cache can hold, don't cache. It is impossible to move from fast cache to slow array as fast as you can write to cache, and trying to move while still writing only makes it worse.
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.