Fan control, ups shutdown

[mkz1975]

These two things need to be improved: fan control, so it can be smoothly adjusted to the individual needs (noise-level) , and the energy level of the emergency power supply ups at which NAS will take a certain action (i.e. shut down at 50%)- now it is just time (5 mins oraz 10 mins).

[Nazar78]

Open a ticket with Asustor to make suggestions.

[noebr]

Can't talk about ups but I've been using the tips I found in this thread for many years.

At the time the drop in disks temperature was significant and since then I have never tested the standard ADM fan profiles again to see if they improved it.

Recently migrated from an AS3202T to an AS5402T and kept the script.

[Nazar78]

Can't talk about ups but I've been using the tips I found in this thread for many years.

At the time the drop in disks temperature was significant and since then I have never tested the standard ADM fan profiles again to see if they improved it.

Recently migrated from an AS3202T to an AS5402T and kept the script.

I maybe wrong, think there's a reason why Asustor didn't implement the fan control tied to the disk temperature. When you query the disk, it will wake the disk if its asleep. Continuous queries will eventually cause the disk to no longer sleep. You can try test it, let the disk sleep (or force it) for awhile. Try query the disk temp once, you'll notice it'll take a while for the disk to wake up and the disk temp will remain low. Then keep querying the temp on any short specific intervals and you'll notice the disk temp will continue to rise till equilibrium.

Instead of checking the disk temp, think it's better to probe the CPU instead since the disks placement is quite close to the CPU? `cat /sys/class/thermal/thermal_zone0/temp`. There's another way though, that's to check if the disk is asleep and skip the probe.

[noebr]

Can't talk about ups but I've been using the tips I found in this thread for many years.

At the time the drop in disks temperature was significant and since then I have never tested the standard ADM fan profiles again to see if they improved it.

Recently migrated from an AS3202T to an AS5402T and kept the script.

I maybe wrong, think there's a reason why Asustor didn't implement the fan control tied to the disk temperature. When you query the disk, it will wake the disk if its asleep. Continuous queries will eventually cause the disk to no longer sleep. You can try test it, let the disk sleep (or force it) for awhile. Try query the disk temp once, you'll notice it'll take a while for the disk to wake up and the disk temp will remain low. Then keep querying the temp on any short specific intervals and you'll notice the disk temp will continue to rise till equilibrium.

Instead of checking the disk temp, think it's better to probe the CPU instead since the disks placement is quite close to the CPU? `cat /sys/class/thermal/thermal_zone0/temp`. There's another way though, that's to check if the disk is asleep and skip the probe.

Well, you have a good point but but my equipment only has two bays in Raid 1 with applications like Docker, VMs and many others so the disks are normally spinning all the time.

As I said before, I don't know if Asustor's default profile (Auto) improved but at that time the Low and Auto settings left the disks too hot (40+ºC all the time) while Medium setting was very noisy, with the script the reduction in disk temperature was at least 10ºC almost with no noise, so I left the script there when I changed my NAS (in practice I just moved the disks from the old one to the new one and turned it on, and that was great).

This file you pointed apparently shows a temperature of 27.8ºC (without variance) while the ADM shows ~55ºC (CPU) and ~35ºC (system) so I believe it is not the most accurate, but it's just a guess.

Code: Select all

$ cat /sys/class/thermal/thermal_zone0/temp
27800

Anyway, it would be nice if we had better control of these settings and also if we could use the temperature of the CPU and/or disks as reference.

[Nazar78]

Well, you have a good point but but my equipment only has two bays in Raid 1 with applications like Docker, VMs and many others so the disks are normally spinning all the time.

It doesn't have to spin all time, it depends on how you setup your NAS, take a look at my signature. I have 4 disks raid10 on the 4 bay (sleeping most of the time) and another 4 disks raid0 on external USB enclosure (sleeping except midnight running backups). Lots of apps running using 50%+ of 16GB RAM. Less power + heat + noise, I blast the fan automatically only during midnight backups. The idea of using the CPU is to gauge the overall temperature which I can auto blast the fan when doing intensive stuffs like compiling or playing nvidia stream games on the NAS viewtopic.php?t=13001, this without waking up the disks.