January 1, 20251 yr I think I have a fairly simple Unraid setup running with 2x 6 TB HDD and a 1 TB SSD drive. All my docker stuff resides on the SSD and still the HDDs are spinning all the time throughout the day. How can I find out what makes them spinning all the time?
January 2, 20251 yr Author Sorry to have missed that, attached here. Edited January 4, 20251 yr by Moerky
January 2, 20251 yr Community Expert appdata shareUseCache="prefer" # Share exists on cache, disk1 domains shareUseCache="yes" # Share exists on disk1 isos shareUseCache="yes" # Share exists on disk1 system shareUseCache="yes" # Share exists on disk1 All the system shares have data on the array, move them all to the cache pool
January 2, 20251 yr Author Thank you! Done! But when looking at the read/writes it's still continuously accessing the array - about 150 writes/sec.
January 2, 20251 yr Community Expert appdata shareUseCache="only" # Share exists on cache, disk1 domains shareUseCache="only" # Share exists on disk1 isos shareUseCache="only" # Share exists on disk1 system shareUseCache="only" # Share exists on disk1 They are still on disk1, just changing the share settings won't move the files, you can use the mover, see this procedure, mostly the 2nd part: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/#findComment-511923
January 2, 20251 yr Author Tried to follow the instructions but when clicking on Move on the Main Tab nothing happens. Normally I'd see a message that the mover is running.
January 2, 20251 yr Community Expert Probably the shares are not correctly configured, verify all settings and if it still fails post new diags.
January 2, 20251 yr Author How could I configure them wrong? I set everything to Cache which can be seen on my last config post - nothing changed apart from that I took everything offline - Dockers, Docker-Compose, VMs.... Shouldn't there be an error message at least if the mover can't run properly?
January 2, 20251 yr Community Expert 25 minutes ago, Moerky said: I set everything to Cache which can be seen on my last config post That's no the correct option for the mover to work, see the link above.
January 3, 20251 yr Author Ok, that did work now and my array is spinning down correctly and the server consuming 50% less power than before! Very cool as I wanted this since months. What I still have is the following errors when executing the fix common problems. Is there a way I can get rid of these too?
January 3, 20251 yr Community Expert The 3 shares you mention are not configured correctly to get all their files moved to the cache! you need: primary storage set to cache secondary storage set to array mover direction set to be array->cache temporarily disable Docker and VM services under Settings as they will keep files open stopping them from being moved run Mover to move all array files to cache for these shares When mover completes and all files are on the cache then you can remove the secondary storage option. You should also enable the option for Exclusive Shares under Settings->Global Share settings as this can improve performance for shares which are only on the cache and have no Secondary Storage set. note that the above assumes there is enough space on the cache to hold all files for these shares
January 4, 20251 yr Author I've done as supposed by you. But I don't get rid of the array files for app data. Secondary storage set to Array Mover set to array > cache temporarily disable Docker and VM services Invoked mover Removed secondary storage option Leaving all docker and VM setting disabled Running Fix-Common-Problems > still get the error for Share appdata set to cache-only, but files / folders exist on the array Diagnostics attached. Shall I manually delete these files? Where do they reside? I'd like continue with my setup of other containers but want to sort this out first. Edited January 4, 20251 yr by Moerky wording
January 4, 20251 yr Community Expert Solution You should check between steps 4 and 5 that there are no files (or folders) for the share left on the main array. You can do this using the Dynamix File Manager. Note that mover will not overwrite files that are in both locations so if that scenario exists you will have to manually delete one copy and you have to decide which one (typically the oldest ).
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.