I have read a number of differing posts about this and peoples solutions seem to be different. I started using unraid about 2 weeks ago and have finally got all my data on the system and the parity built. However in that time Disk 1 has never spun down on its own. I had it set to spin down after an hour, but have dropped that to 30 mins to see if i could get it to stay, but as soon as it spins down it spins immediately back up.

 

I have a number of dockers that are set to use my drive cache (originally when i set the dockers up i had them using the array as that was how it was set by default. I then followed a forum post, moved appdata to the cache and changed the share to use the cache and restarted the dockers. Functionally this worked.

 

If i stop all the dockers i can keep the drives spun down but i have gone through all the settings and share usage and i cant see what is set to write or read a load of data from the array and not from the cache. I have installed file activity and the only data stored there is the iCloudpd docker writing an update to the drive cache.

 

As soon as i start a docker image then disk 1 will spin back up and start a number of reads and writes to the drive, this slows down after initial start up but nothing is recorded in the file activity plugin.

 

Is there something i have missed in moving when i moved my docker images. Happy to take a backup and completely rebuild them if that is what is needed. I have attached the diagnostics and would really appreciate the help here more for my own understanding of how the shares and cache even operates.

shield-diagnostics-20240616-0827.zip

Edited June 16, 20242 yr by HumanSkunk

3 hours ago, HumanSkunk said:

when i set the dockers up i had them using the array as that was how it was set by default

By default, if you have cache installed when you first start Docker service in Settings, the docker related shares will be created on cache. If you don't have cache installed when you first start Docker service, it has to create them on the array.

 

There are some other things about the way you have things configured that are not default, and/or inconsistent. Perhaps you have done this trying to fix your issue.

 

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

 

That link lists the user shares that are created by Docker and VM Manager.

 

appdata, domains, system shares should have all their contents on cache or other fast pool, with nothing on the array, so Dockers/VMs will perform better, and so array disks can spin down since these files are always open.

 

domains  is for VM vdisks so is not involved in your situation. appdata is all on drive_cache, so that is OK.

 

You have configured system is to be moved to the array. You want it to stay on cache instead. Probably that is the reason for your problem.

 

But...

 

Diagnostics seems to indicate system share is empty or non-existent, but docker.img is mounted and is stored on that share, so that is very confusing.

 

What do you get from command line with this?

ls -lah /mnt/user/system

 

So yes I created a bit of a mess for myself in that I accidentally deleted a number of shares that I didnt think were being used as there was nothing stored in them. I clearly didnt look very hard. I read warnings of the file manager app being able to cause damage and I removed a number of key files whilst I was trying to work out what was causing the drives to remain active.

 

Long and short I did accidentally delete a number of the shares unknowingly when posting that file that the dockers need. When I started the dockers all their contents and configurations had been lost which I noticed about 5 mins after doing it with a lot of swearing. I have now recreated the system share entirely on the cache and recreated all my docker images again after deleting them. What was meant to be a quick tidy up of some files has now meant spending a good number of hours rebuilding things. Lesson learnt I guess. 

 

Plus side is that the drives have remained spun down during all of this. System share is now present when I run the command and all the dockers have loaded. Downside is I am getting a weird behaviour with the binhex-sabnzbdvpn docker that wont load its gui when the vpn is set to yes in the docker settings, but it functions correctly even with the vpn active I just cant access it, I have posted elsewhere with that issue.

shield-diagnostics-20240616-1311.zip

44 minutes ago, HumanSkunk said:

spending a good number of hours rebuilding things

You can reinstall any of your dockers by simply using Previous Apps on the Apps page. We often have people recreate docker.img and reinstall.

 

https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file

 

https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications

 

46 minutes ago, HumanSkunk said:

binhex-sabnzbdvpn

You can go directly to the correct support thread for that container by clicking its icon in your Unraid webUI and selecting Support.

Doh well that would have saved me a bit of time. At least it was practice more than anything. And yes I have posted on the main support for sabznzb and hopefully I can get that resolved.