Nextcloud preventing HDD spin down

[raphael1-w]

Hi all, 
I'm facing a problem where the Nextcloud container is preventing my HDD from spinning down. 

 

I have the spin down delay set to 1 hour. Standby monitor shows that the drives are able to spin down for 15 mins around every 3-4 hours sometimes (can only test this at night so not sure if this is always true). However, there are times where if I manually spin down the drives, it can stay spun down for 3 or 4 hours. I have verified that the Nextcloud container is the problem, as stopping the container allowed the drives to automatically spin down for up to 8 hours before drive usage spun it back up. 

 

I have already moved the appdata and systems share to the cache (cache only), and I've also moved the log file to the cache (I think). The file activity plugin does not show any activity, yet the drives stay spun up. 

 

Since both the parity drive and the data drive are active and standby at the same time, and there are no reads on the parity drive, I'm fairly certain that the activity is a write instead of a read. 

 

Does anyone have any insights as to what the problem might be? 

 

Thanks in advance. 

 

Setup details:
OS: Unraid 6.12.10
Array: 2x Seagate Ironwolf 4tb (1 parity 1 main)
Cache: 1x Crucial 1tb nvme ssd

server-r1-diagnostics-20240809-1203.zip

[king79]

Hello, I have been experiencing the same behavior on my Unraid server for about 4 weeks.

It would be nice if someone could help with the problem.

 

Setup details:
OS: Unraid 6.12.11

Docker Container: Linuxserver´s Nextcloud

[shansen008]

Ditto this topic.

[Tonio]

Hello, I'm leaving this post here in case it's helpful to anyone. In my case I use the linuxserver docker, I've been investigating the reason. I knew it was something related to "nextcloud" because if I turned off the container, the disks spin down without any problem. Then I started looking for the reason why reading and writing was being done on my disks with the "inoitywait" command, because that was another problem, there were continuous writes that made my parity disk wake up too. Well, to sum it up, the culprit was the "collabora" container, since the last updates something must be wrong, now I've changed to onlyoffice and my disks are spinning down again.