[Array is spinning up after 1 hour]

Problem is completly solved!

Thanks for all the feedback tips and tricks.

[Array is spinning up after 1 hour]

It looks like that i found the problem with the file activity plugin.
The problem is at the moment in the docker container Minio, This will read every hour on one of the buckets.
But before i run without dockers and on that time the problem was also there. On the end i looks like there was a multipli issue not only the Minio app.

 

The array is no for 3 hours in standby.

Have someone experiece with the Minio container to set this up that it only wil read or write when the backup is running?

[Array is spinning up after 1 hour]

Nobody that can help me?
 

[Array is spinning up after 1 hour]

So after amany hour Test there is no different after changing the path. Disk are always spinning up every hour.

 

 

[Array is spinning up after 1 hour]

I'm Agree with you but the first periode it was working correctly with the same settup of shared folders. 
But only the last 2 weeks or maybe a week longer it is like this. I uninstalled everything what i can remeber and also i put all the settings back like i remember. 
but is looks like nothing got the right effect. 

UPDATE: To be sure i change all the docker and vm paths from /mnt/user/xxxx to mnt/cache_virtual/xxxx

 

[Array is spinning up after 1 hour]

3 hours ago, Vr2Io said:

VM and Docker service still enable and use /mnt/user/xxxxxxx path

 

If you want spindown as much as possible, move those to SSD and mount by UD in /mnt/disks/xxxxxxx

 

DOCKER_ENABLED="yes"
DOCKER_IMAGE_FILE="/mnt/user/system/docker/docker.img"
DOCKER_IMAGE_SIZE="80"
DOCKER_APP_CONFIG_PATH="/mnt/user/appdata/"

 

SERVICE="enable"
IMAGE_FILE="/mnt/user/system/libvirt/libvirt.img"
IMAGE_SIZE="1"
DEBUG="no"
DOMAINDIR="/mnt/user/domains/"
MEDIADIR="/mnt/user/VMData/"
VIRTIOISO="/mnt/user/VMData/VM Image/virtio-win-0.1.229-1.iso"

 

Thanks for youre reply! 
But like i write in the start post i Try to run without Docker and Without VM for more than 1 day but it got still the same effect. 
Also the folders are on the /mnt/user/xxxxx but all the folders what is reletated with the system, docker or vm on een ssd pool only. 

[Array is spinning up after 1 hour]

Hello All, 

I'm a overall happy user of Unraid! 
By the fresh install of it the disk go to standby an stay there till i need them, sometimes for some days other time it is a couple of hours. 
But the last 2 weeks the disk are only spin down when de delay time is less than a hour. Every hour i got the smart data is reading on the drive and the pairity. 
I know the smart read is not the reason only a domino effect for a read/write on the drive. 
But any way i cant find the reason why there is something using my disks. 

 

Unraid Version 6.11.5

What i try, Some things are enable again after the testing periode. 
* Run without VM's 
* Run witout Dockers
* Deinstall some plugins. 
* Disconnect from Unraid Connect. 
* Check shared folders ( Some using the disks but always with a cache drive. And some are using only the SSD drives ) 
* Disable SMB en NFS shares on the network. 
* Check active steams ( Plugin )
* Check open files ( Plugin )
* Check File Activity ( Plugin )
* Disable WIreguard 

 

Hardware:

 

Intel I5 13600
MSI Z790 Pro 
2x 32 GB DDR5 
2x 980 Pro NVME

2x 970 Evo NVME 
2x 18 TB Drives 

 

 

The last 1 or 2 days i put the spin down delay to 1 hour in that way you cant find a many spin down or spin ups but the last one like the screenshot in the bottum is in the diagnostics. 
Everytime after a spin down, they stay in spin down for 1 hour. 

Maybe can someone tell me were he can find the problem in the diagnostic, i take a look in many files but i cant find a reason. 
 

Screenshot of 18TB Drives at the moment they spin up again. 
First signal of  spin up is on 18:55:20 (hh:mm:ss) this must be findable in the diagnostics.
Everytime when this is happening it look  exactly the same like this screenshot ( amount of spikes, Lenght of spike, always afthe the first block i get a minute later a second different looking block of spikes). 

 

At this moment i don't know what i can try any more, i read a lot of topics about the same issue but i can't find it.

Thanks for helping! 
 

main-nas-diagnostics-20230601-1912.zip