raphael1-w

I might have explained it a bit poorly. Let me try again. Nextcloud writing to the logs was the cause of my HDD not spinning down. I'm fairly certain about this because the first time I ran those commands to make a new log file, I had most of the data on the array. That solved the problem until the mover ran that night. I have also managed to replicate this one other time, with that being the only other time. I was not able to find the log on the array, but that might be a me problem because I'm honestly still not that familiar with the file structure, and might have missed the file. Also, regarding open files, it did not show that nextcloud.log was open anywhere.

How so? It's clearly causing a problem, making my drives spin down and up unnecessarily for ~20 times a day, wasting drive life and electricity. I'm genuinely curious why you think the log being moved isn't my problem.

I wasn't able to find a different log file anywhere else after running the mover. /config/log/nextcloud.log is in appdata, which is set to cache only. The only log file I could find was in /mnt/cache/appdata/nextcloud/log. I could not find a log file in either /user0 or /disk1.

Hi all, I have a problem regarding the mover moving the nextcloud log file from the cache to the array, which is preventing my HDD from spinning down, and I don't know why it's happening. The nextcloud container logging has prevented my HDD from spinning down for long periods of time, with them spinning back up ~3 mins after spinning down, every hour. I have successfully solved this by changing the location of the log file to '/config/log/nextcloud.log', and by running the following commands: docker exec -it nextcloud bash sudo -u abc touch /config/log/nextcloud.log chmod 777 /config/log/nextcloud.log From here However, every time the mover runs, the problem returns. I assume the problem is because the mover is moving the file, which is on the cache, back to the array. I have tried to prevent the move by using the mover tuning plugin and excluding the files '/mnt/cache/Nextcloud/nextcloud.log and '/mnt/cache/./Nextcloud/nextcloud.log'. Even though the mover logs show that the log file has not been moved, the problem still returned. If I move the whole Nextcloud data share from the array back to the cache, the problem goes away. Can someone tell me what might have caused this? Thanks in advance. server-r1-diagnostics-20240815-0041.zip

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

Hi all, I cannot spin down both drives in the system, the cache drive and disk 1. Every time I spin down the drives, they spin back up after a few seconds. They seem to also get some writes every few seconds. I'm pretty sure this is caused by docker, as stopping docker stops most of the writes. However, I have not managed to find out what the problem is. The file activity plugin was unable to log any writes or reads. Both the appdata share and the system share are cache only already. Drive setup: 2x Seagate Ironwolf 4tb on array 1x Curcial 1tb nvme ssd as cache Does anyone know what the problem is? Many thanks server-r1-diagnostics-20240804-2229.zip