Drive won't spin down

[SP67]

Hello, 

 

Two of my drives won't spin down since a few weeks ago. One is the parity so I guess the culprit is the other one.

 

I have checked the active streams plug-in and no active stream is reported. 

 

Can you please help the troubleshoot? 

 

Thanks!

nas-diagnostics-20230228-1030.zip

[itimpi]

You currently have part of the ‘system’ share on disk1 - is that the one that will not spin down

 

if you want to get it all onto the cache then disable the docker and system services and run mover. You need to disable these services because they keep files open all the time they are running and mover will not move open files.  When mover finishes you can then re-enable these services.

[SP67]

Done. Anything else I need to be aware off? I'm attaching the updated diagnostics file. 

 

Thanks!

 

nas-diagnostics-20230228-1628.zip

[itimpi]

The ‘system’ share now shows as being entirely on the cache pool.   Be interested to hear if that has improved things - it should for docker containers.    For VMs the ‘domains’ share seems to exist on multiple drives (I assume contains vdisk images) so running VMs may spin up array drives.

[SP67]

Great! I’ll let you know. 
 

I’d like to move some files from the array to the cache (downloads_cache in my case) so that the array can indeed spin off (recently downloaded files are active).

 

I suppose that I can rsync from /user/mnt… but I’m unsure about the destination.

[trurl]

Set the share to cache:prefer and run mover to get it moved from array to cache. Nothing can move open files as already noted, so you would need to make sure nothing was using the share when you run mover.

[SP67]

But in this case I don’t want to move the full share (as it’s bigger than the cache), only a subfolder. Is this possible?

 

Thanks!

[trurl]

You can move them manually. If you also want to prevent Mover from moving files on a share, set the share to cache:no (new files go to array, never moved) or to cache:only (new files go to cache, never moved)

[SP67]

Hello again, 

 

A couple days have passed and two of my drives (the same ones) still won't spin down. Anything else that might be affecting it?

 

Edited: it happens even with the VM turned off. If I force the sleep from the webUI it only lasts ~5s before those drives are up again. 

 

 

 

nas-diagnostics-20230308-1359.zip

Edited March 8, 2023 by SP67

[SP67]

According to the File Activity plug-in, qBittorrent is opening files (even though nothing is being transferred ATM) and paperless is modifying the database (even though no one is doing anything with it).