October 21, 2025Oct 21 Hi everyone, I have the following problem:I replaced my cache SSD. To do this, I first transferred all data from the SSD to the array using Mover, and after replacing the disk, I reversed the Mover and wrote everything back. Now I've noticed that one of my array disks and the parity disk are no longer going into spindown. When checking the array disk, I saw that there are still parts of the system directory there and, logically, they are constantly being used (individual items in /usr/system/docker/docker/) and the disk (and thus also the parity) cannot rest. Is there a solution for me to clean this up properly? Tibbs
October 21, 2025Oct 21 Community Expert Did you make sure that the Docker and VM services were disabled in Settings before running mover to transfer files back? If not they will keep files open and that stops them being transferred by mover. In particular this is relevant to the ‘system’ share.
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.