sakmer

Dear cirkator I think you're right about cache_dirs. When I renamed find, cache_dirs went into stop state. So it was probably cache_that initiated find. Any ideas? By the way I am running cache_dirs 1.6.9

Other actions include deactivation of PLEX and uninstalltion of MySQL. No possitive effect again. I have temporarily renamed find to find.orig hoping that I will see something in a log.The only thing I have managed is to sucessfully stop the drives from spinning up, but I don't consider this a solution.

Yes, but I have already tried to deactivate it with no effect

Ok. Initially I though the issue was resolved after upgrading to 5.0.6. My joy nevertheless was not to last long. A few minutes after the upgrade, the disks spun up again. After snooping around with lsof and fuser, I found out that /usr/bin/find is running for some reason constantly thus keeping my drives awake. I cannot whatsoever find out what is the root cause of this. Any help will be much appreciated.

Solved by upgrading to 5.0.6

I have noticed lately that my drives, except parity, won't spin down. I also noticed that read counts of disks are increased exponentially. So I guess, some process is keeping my drives awake. Since I am not a linux expert, it is very difficult for me to find what is happening and I would appreciate any help. My system is an unRAID Server Plus, Version 5.0.5 running on an ASRock - C226 WS equipped with an Intel® Pentium® CPU G3220 @ 3.00GHz and 4 Gigs of RAM. I have plex server installed but I have tried stopping it with no change. I also have mysql installed. I have attached the syslog and some screenshots that show details of the system. https://www.dropbox.com/s/vn5yu5moandfjq1/disks.jpg?dl=0 https://www.dropbox.com/s/34b2ekuy8k7hr7d/settings.jpg?dl=0 syslog.zip