Alistar Posted January 30 Share Posted January 30 (edited) Hi, I've been trying to spin down Parity drive when not used for some time now, but seems like constantly something is keeping it active. Even if I try to spin it down manually, it goes up after some seconds. Two other drives go down - no issues. Im using 1 ssd cache + 4 exos drives + 1 usb for backup. Unraid 6.12.6 Checked manually paths etc. in dockers and at first glance all looks good. Spin down delay enabled - double checked. New user here, and run out of ideas. Maybe I misconfigured something or missed some of the settings? Highly appreciated if someone could take a look at diag logs, and advise what could be improved. tower-diagnostics-20240130-2116.zip Edited January 30 by Alistar formatting Quote Link to comment
itimpi Posted January 31 Share Posted January 31 Your ‘system’ share has files on disk1. If this includes the docker.img file then even having the docker service started will keep disk1 and parity spun up as writes to any array drive automatically update parity at the same time. 1 Quote Link to comment
Alistar Posted January 31 Author Share Posted January 31 (edited) 2 hours ago, itimpi said: Your ‘system’ share has files on disk1. If this includes the docker.img file then even having the docker service started will keep disk1 and parity spun up as writes to any array drive automatically update parity at the same time. Thanks for taking time to take a look on my case! I have checked the settings of 'system' share: Thought it looks good. Should I set secondary storage to none, or change anything here? Indeed theres a docker.img file on disk1: And same location is empty on cache: How can I safely move it now from Disk1 to Cache? Edited January 31 by Alistar Quote Link to comment
Solution itimpi Posted January 31 Solution Share Posted January 31 You should: Disable the Docker service under settings (it needs to be disabled to stop it keeping files open) Run mover to transfer the contents of the 'system' share to the cache (optional) When that completes you might want to confirm that there is now no sign of the 'system' share on disk1 Set the secondary storage option for the 'system' to None Enable the option to use Exclusive shares under Settings->Global Share settings to get the performance advantage of bypassing the Unraid Fuse layer Reenable the Docker service Once this is done then docker will not be keeping disk1 and parity spun up all the time. 1 Quote Link to comment
Alistar Posted January 31 Author Share Posted January 31 (edited) 2 hours ago, itimpi said: You should: Disable the Docker service under settings (it needs to be disabled to stop it keeping files open) Run mover to transfer the contents of the 'system' share to the cache (optional) When that completes you might want to confirm that there is now no sign of the 'system' share on disk1 Set the secondary storage option for the 'system' to None Enable the option to use Exclusive shares under Settings->Global Share settings to get the performance advantage of bypassing the Unraid Fuse layer Reenable the Docker service Once this is done then docker will not be keeping disk1 and parity spun up all the time. During cleanup process I have realized that in VM Manager and Docker service itself I still had paths pointing to /mnt/user instead /mnt/cache. I have changed that as well to avoid similar issue in the future with vms: Other than that I have made all mentioned changes and it works now Btw is my understading correct, that in best scenario - parity should remain in standby if 'Write' is happening to cache, and only activate when mover kicks in? Also Parity remains in standby if only "read" is happening from Disk 1-3? Edited January 31 by Alistar Quote Link to comment
itimpi Posted January 31 Share Posted January 31 3 hours ago, Alistar said: During cleanup process I have realized that in VM Manager and Docker service itself I still had paths pointing to /mnt/user instead /mnt/cache. This is not necessary if the share is an Exclusive share. 3 hours ago, Alistar said: Btw is my understading correct, that in best scenario - parity should remain in standby if 'Write' is happening to cache, and only activate when mover kicks in? Also Parity remains in standby if only "read" is happening from Disk 1-3? Parity is realtime so any write to the array also causes a write to the parity drive. You may find this section of the online documentation accessible via the Manual link at the bottom of the Unraid GUI useful in understanding how writes to the array are handled. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom. The Unraid OS->Manual section covers most aspects of the current Unraid release. 1 Quote Link to comment
Alistar Posted January 31 Author Share Posted January 31 5 hours ago, itimpi said: This is not necessary if the share is an Exclusive share. Parity is realtime so any write to the array also causes a write to the parity drive. You may find this section of the online documentation accessible via the Manual link at the bottom of the Unraid GUI useful in understanding how writes to the array are handled. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom. The Unraid OS->Manual section covers most aspects of the current Unraid release. Got it. Thank you for support. Will mark this one as resolved. Quote Link to comment
Recommended Posts
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.