eudean

Terramaster F4-220 fan control

Recommended Posts

I recently installed Xpenology on a Terramaster F4-220 I picked up during the holiday sales that were going on. I noticed the hard drives were consistently operating at a very high temperature (50+ C while idle) so I decided to investigate how to control the fans. I had read elsewhere there is some BIOS option to drive the fans faster, but lacking the VGA dongle to get into the BIOS I figured I'd investigate how to control them from Linux.

 

So I discovered the hardware contains an IT8772E chip for which Google helpfully brings up this datasheet:

 

https://master-chip.ru/files/e0ec6325-b20e-079c-f0ce-275a3ec60f51/IT8772E-ITE.pdf

 

I noticed that there is already a kernel driver for this chip, but since I only needed very limited capabilities (just the ability to write the fan PWMs) I decided to just write a custom script to do this. I'm sharing it here so others can take advantage of it. I'm guessing it wouldn't be hard to also drive the LEDs to the right colors as well but I haven't spent time on that since I never look at the LEDs anyway.

 

The basic flow of the code is:

 

  • Initialize the IT8772E chip
  • Write a default PWM value for the fans
  • Read the max hard drive temperature and use a PID loop to calculate a new PWM value to drive the max hard drive temperature to some setpoint


After playing with the PID values for a few days I concluded that just using a P value was sufficient to give decent behavior so I just left kp = 1, ki = kd = 0. I just modified the script to make all of these things overridable in case someone wants to play around with it further without having to recompile. With defaults I find it settles to reasonable values in about 30 minutes. By default the script uses a setpoint of 37 C but again this can be overridden. I chose this after looking at various suggestions online, it seems 30-40 C is the safest range to maintain for average temps in terms of drive failure rate, so 37 C should give some buffer in case of sudden spikes in utilization that PID doesn't react to quickly enough.

 

My argument parsing is really simple, you can use ./fancontrol -h to see how to use the script. Here are some sample uses:

 

  • ./fancontrol (default behavior)
  • ./fancontrol -h (print out usage info)
  • ./fancontrol 1 40 (enable debug logging, setpoint = 40)
  • ./fancontrol 0 37 255 (use the maximum PWM value initially before entering the PID loop)
  • ./fancontrol 0 37 150 10 50 80 0 0 0 0 (use PWM value 150 initially and disable PID by setting all coefficients to 0, this would be like hard-coding the PWM to 150 forever)

 

Anyway, I hope other Terramaster users find this useful. I suspect this will also work on similar Terramaster NASes that use the same chip for fan control but I have only tested on the F4-220 since that's what I own. I've attached the cpp source and a binary built for x86_64 running DSM 6.2 using Synology's build environment (ds.x64-6.2).

 

Some side notes:

 

  • The synostorage daemon already reads drive temperatures and reports them in /var/run/synostorage/disks/sd[abcd]. I initially used these to drive my code but later realized these values may be updated very infrequently (as in many minutes) so I decided to poll via smartctl. I still rely on the disks listed in /var/run/synostorage to know which drives to query.
  • I don't read the CPU temp (or any other sensors). I think keeping the drives at 40 C or below will likely be a stronger constraint on fan speed than CPU usage, but if you expect heavy CPU usage at times when there isn't heavy storage utilization (unlikely for a NAS) then this may not be what you want.
  • I chose an MIT license for the source
  • I don't really intend to maintain this long term except for myself but if people have suggestions let me know and I can try to tackle them.
  • You can run this at boot time using "Task Scheduler"

 

fancontrol

fancontrol.cpp

Edited by eudean

Share this post


Link to post
Share on other sites

HI

 

I have an F2-420 on DS918+ 6.2.1-23824U4 and would like to try this

 

I have searched and read a bit about custom scripts, but if you can help me understand how I would go about executing this

 

Thanks in advance

KP 

Share this post


Link to post
Share on other sites
13 hours ago, kgp721 said:

I have searched and read a bit about custom scripts, but if you can help me understand how I would go about executing this

 

So when developing I logged in via ssh to run the script from a shell.

 

But for general usage you should use "Task Scheduler" (in the Control Panel) to create a task that runs at boot up that just executes the script. See https://www.synology.com/en-us/knowledgebase/DSM/help/DSM/AdminCenter/system_taskscheduler for details. Then just reboot your NAS. The fans will take some time to stabilize so after you boot it, wait an hour or two, then check the hard drive temperatures in Storage Manager and they should be pretty close to 37 C (unless you're room is super hot or cold, in which case it may take longer). Then check on it periodically and it should be very close to 37 C just to make sure it's working fine.

 

Unfortunately I don't see a way for DSM to send a notification if the temperature goes outside of a certain range (only it if goes above the hard drive operating temperature, which is kind of late to send a notification). Maybe someday I'll add something to the script for that.

Edited by eudean

Share this post


Link to post
Share on other sites
Posted (edited)

HI - Thanks for developing this. I just tried it out on my f4-220 running the 1.04b (ds918) bootloader. fancontrol -h works, but anything else gives me "segmentation fault" - any clues? Running as admin from a putty ssh session. Thx

 

Edited by richv31

Share this post


Link to post
Share on other sites

Try using sudo (i.e., sudo ./fancontrol). If you aren't root iopl will probably fail and you'll be writing to invalid memory very quickly (I don't have a lot of error checking for these kinds of things).

Share this post


Link to post
Share on other sites
Posted (edited)

 

Thanks alot for sharing this! I just signed up for this.

 

 I'm not actually using Xpenology but rather Openmediavault and the fans seem to kick in to 100% and then ramp down. Your code helped me figure out how to manage the  fans.

 

For reference to anyone stumbling on this thread and wants to port it to OMV:

1.  You need to change where the drives are detected since it's different from DSM. For me it was located in /run/disks

EDIT: These did not exist by default. I've created this directory and just created empty files inside (as root):

mkdir /run/disks
cd /run/disks
touch sda sdb sdc

This far from perfect and if you're a Linux wizard you probably can do something better with regex, e.g.  /dev/sd*[a-z]

 

2. Replace the directory in line 51 (fancontrol.cpp) with the directory containing your drives. For me that was: 

const static char * synostoragedir = "/run/disks";

3. Compile fancontrol.cpp and run with sudo. 

 

 

Tip: You can use a docker gcc image to avoid installing dependencies on OMV/Debian/Ubuntu

Pull the image:

docker pull gcc

Compile fancontrol.cpp (you must be in the same directory)

docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp gcc gcc -o fancontrol fancontrol.cpp

Make sure run with fancontrol with sudo.

Edited by DONIII

Share this post


Link to post
Share on other sites
Posted (edited)

I am trying that on f2-220 DS3615xs

compiled the fancontrol

(sudo)running it with any argument gives me Segmentation fault

Edited by Regi1442

Share this post


Link to post
Share on other sites
Posted (edited)

HEY I AM LOOKING FOR THIS FOR A SIMILAR REASON

LMSENSOR SAYS:

sensors | grep fan
fan1:           0 RPM  (min =   41 RPM)  ALARM
fan2:           0 RPM  (min =   18 RPM)  ALARM
fan3:         241 RPM  (min =   28 RPM)  ALARM

 

I THINK MY BOARD IS STILL GOOD MY FANS ARE JUST SHOT.

I AM POSTING HERE AS newest member

BUT MY ID ON OMV ID IS seth.nordmeyer

 

PLZ

PM ME THERE

 

SORRY ABOUT CAPS  I AM BLIND  ANY IDEA WHERE TO GET FANS?

 

PEACE,

SNN

 

 

 

 

Edited by SNN72

Share this post


Link to post
Share on other sites

Could somebody please explain how to implement / use this script in DSM. Thank you.

Share this post


Link to post
Share on other sites

I am completely new to this and have done my best to ask others for help before posting here.  How/where do we upload this script so that we can run it as a scheduled task?

Share this post


Link to post
Share on other sites
3 hours ago, TylerGo said:

I am completely new to this and have done my best to ask others for help before posting here.  How/where do we upload this script so that we can run it as a scheduled task?

You can put it anywhere Task Scheduler can read from, which includes in the DSM filesystem or in your NAS storage. You just need to pass the full path to the script in the "User-defined script", e.g., in mine I put /usr/local/bin/fancontrol

Share this post


Link to post
Share on other sites
On 8/17/2019 at 9:15 PM, Regi1442 said:

I am trying that on f2-220 DS3615xs

compiled the fancontrol

(sudo)running it with any argument gives me Segmentation fault

 

works after installing lm-sensors

😳

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.