I'm pulling my hair out trying to figure out why my disks keep spinning up.  I have spindown set to 15min.  I run a large cache so that disks wont get spun up unless media older than 2 months gets requested.  

 

Using the File Activity plugin, under Disk Activity It looks like something is opening a file 3 times

 

Apr 10 08:46:31 OPEN => /mnt/disk4/data/media/movies4k/{Movie 1}/{Movie 1}.mkv

Apr 10 08:46:31 OPEN => /mnt/disk4/data/media/movies4k/{Movie 1}/{Movie 1}.mkv

Apr 10 08:46:34 OPEN => /mnt/disk4/data/media/movies4k/{Movie 1}/{Movie 1}.mkv

Apr 10 08:46:43 OPEN => /mnt/disk4/data/media/movies4k/{Movie 2}/{Movie 2}.mkv

Apr 10 08:46:43 OPEN => /mnt/disk4/data/media/movies4k/{Movie 2}/{Movie 2}.mkv

Apr 10 08:47:03 OPEN => /mnt/disk4/data/media/movies4k/{Movie 2}/{Movie 2}.mkv

Apr 10 08:48:41 OPEN => /mnt/disk4/data/media/movies4k/{Movie 3}/{Movie 3}.mkv

Apr 10 08:48:42 OPEN => /mnt/disk4/data/media/movies4k/{Movie 3}/{Movie 3}.mkv

Apr 10 08:48:44 OPEN => /mnt/disk4/data/media/movies4k/{Movie 3}/{Movie 3}.mkv

 

Under Share activity, same thing, file being opened 3 times.  

 

I'm running the full media stack (plex, sab, sonarr, radarr, overseerr, bazarr....) 

Diagnostics attached.  

tower-diagnostics-20250410-0939.zip

Your appdata share has files on disk11

appdata                           shareUseCache="prefer"  # Share exists on cache, disk11

 

Some other things Fix Common Problems has been telling you about your shares.

Apr 10 09:39:34 Tower root: Fix Common Problems: Warning: Share domains set to not use the cache, but files / folders exist on the cache drive
Apr 10 09:39:34 Tower root: Fix Common Problems: Warning: Share Transcode set to not use the cache, but files / folders exist on the cache drive

Those don't have files on the array when the diagnostics were taken, but they are set to not use cache, so anything new written to them would also be on the array, and wouldn't be moved.

 

Also a couple of plugins need removing.

ca.mover.tuning.plg - 2024.09.05.0222  (Deprecated)  (Up to date)
NerdTools.plg - 2024.02.17  (Up to date)  (Incompatible)

Probably not related to drive spinup though.

 

57 minutes ago, trurl said:

Your appdata share has files on disk11

appdata                           shareUseCache="prefer"  # Share exists on cache, disk11

 

Some other things Fix Common Problems has been telling you about your shares.

Apr 10 09:39:34 Tower root: Fix Common Problems: Warning: Share domains set to not use the cache, but files / folders exist on the cache drive
Apr 10 09:39:34 Tower root: Fix Common Problems: Warning: Share Transcode set to not use the cache, but files / folders exist on the cache drive

Those don't have files on the array when the diagnostics were taken, but they are set to not use cache, so anything new written to them would also be on the array, and wouldn't be moved.

 

Also a couple of plugins need removing.

ca.mover.tuning.plg - 2024.09.05.0222  (Deprecated)  (Up to date)
NerdTools.plg - 2024.02.17  (Up to date)  (Incompatible)

Probably not related to drive spinup though.

 

Thanks!

 

So i went ahead and set the appdata share to cache only and ran the mover (after shutting down the docker engine).  It still left a binhex-radar and binhex-sonarr with nothing in it,  so i went ahead and deleted them.  

 

Domains and Transcode shares dont get used, so that shouldn't cause the spin up issue, but i went ahead and fixed them anyways.  

 

I removed nerdtools but left the mover.tuning.  I believe the other mover tuning doesn't have a "smart cache" feature where it will keep media on the cache as long as it can and move oldest media onto the array when needed.  

 

Attached updated diagnostics

tower-diagnostics-20250410-1226.zip

Any time you are having problems with mover, the first step in troubleshooting is to remove the mover tuning plugin. Then we can see how built-in mover is working with the share settings you have made, and probably adjust the share settings appropriately.

 

Then, if you still want to use mover tuning, and it isn't working like you want, you should post to its support thread.

 

1 hour ago, danimal86 said:

set the appdata share to cache only and ran the mover

Even if you had been using the built-in mover, that wouldn't have worked. Mover ignores cache only shares. A share has to have a Mover action set, and it can't have a Mover action unless it has Secondary storage.

 

Also, nothing can move open files. Typically, you need to disable Docker and VM Manager in Settings if you need to work with appdata, domains, system shares.

Do you still have the spinup issue?

28 minutes ago, trurl said:

Do you still have the spinup issue?

So far no, i did have one file that was opened a ton of times, but i think radarr was trying to import it.  I just went ahead and deleted it to see if that was the issue.  I'll keep an eye on it and let you know if disks are still spinning up.  

 

34 minutes ago, trurl said:

Even if you had been using the built-in mover, that wouldn't have worked. Mover ignores cache only shares. A share has to have a Mover action set, and it can't have a Mover action unless it has Secondary storage.

 

Also, nothing can move open files. Typically, you need to disable Docker and VM Manager in Settings if you need to work with appdata, domains, system shares.

Thanks for this.  I'll go ahead and set a secondary storage for those shares to the array and set the mover to move Array ->Cache.