Hey, I read a lot of posts on this topic, but unfortunately none of them helped me. I am new to unraid and installed it on my server a few days ago. I was just using my 2 hdds for everything at first until I thought about using my ssd as a cache. I set up the shares for my media server as cache -> array share so that everything is saved to the cache first and loaded to the hdd at night. I thought that was all, but the Disk1 HDD stays spun up, even though I am not using plex or any other docker container that uses stuff from that media share. 

I then moved all files and folders (appdata, system) off the array except for the media data to the cache ssd. On Disk1 only remains my media data for plex. Docker should also run completely on the cache SSD. First I used the mover. After not all the data within the appdata and system folder was moved, I moved it myself using the Unraid Page File Manager.

Although the Disk1 HDD stays up no matter what I do. I downloaded the Active Streams, File Activity and Open Files plugins but I cant see anything connected to Disk1. 

 

Is it not possible to spin down Disk1 while running Docker Containers like Plex? I thought while no one is using plex, there should be no data transfer and the disk 1 can go off until

1. someone want to upload files to the share - which should be only uploaded to the ssd without waking up the hdd OR
2. someone want to watch movies stored on that hdd

Maybe someone here can help me out. I am also considering a complete reinstall of unraid if nothing else helps.

homelab-diagnostics-20250412-1205.zip

Disable docker service and VM services and see if it spins down.

Yes, after disable docker disk1 and also the cache spins down completely. 

But shouldn't that be possible with enabled docker? 

https://docs.unraid.net/unraid-os/manual/shares/user-shares/#default-shares

Ideally, the "default" shares should have all files on cache or some other pool, with no files on disk1 or any other array disks, so Docker/VM performance will not be impacted by slower array reads and especially writes, and so array disks can spin down since these files are always open.

 

Nothing can move open files, so to work on this, you need to go to Settings - Docker and disable that, and go to Settings - VM Manager and disable that.

 

Set each of the default shares to

Primary:cache; Secondary:array; Mover action:array->cache

 

Run mover, wait for it to complete, post new diagnostics.

Looks like appdata and system are already on cache, and you probably never enabled VM Manager. So no need to change any of that.

 

I assume your only other user share

p------a                          shareUseCache="yes"     # Share exists on cache, disk1

has dockers reading/writing it. If there is ongoing activity on an array disk it can't spin down.

1 hour ago, bowshed said:

I am also considering a complete reinstall of unraid if nothing else helps.

No reason to expect that to help. Unraid is already a clean install at each boot.

 Man, I feel so dump right now. I thought stopping all docker containers is like stopping docker. After that in shares appeared an old share that I had deleted yesterday and also some apps were deleted too. But that's no problem, because now the disk1 finally stays down. Thank you both very much! 

15 minutes ago, bowshed said:

in shares appeared an old share that I had deleted yesterday

All top level folders are automatically a user share. Something recreated it by writing a top level folder, probably one of your containers.

17 minutes ago, bowshed said:

some apps were deleted too

Not sure exactly what you mean there. If some container seemed to "start over", that might suggest you had its appdata mapped to a path that wasn't actually mounted storage. Any path that isn't mounted storage is a path in RAM.

 

You should install Fix Common Problem plugin.