Jump to content
  • 0

[Invalid] - Any idea to make the Fan of M4V2 SATA hat always running?



I have a M4V2, and want to build a mini NAS with OpenMediaVault 5 under Armbian (OMV5 can only run under Armbiam/Debian, but not in Ubuntu)


The M4V2 has a SATA hat, and it can support up to 4 hard drives (2.5 inches size), so the SATA hat is powered separately, and I guess this is why this hat always gets overheat.




There is a 12V fan interface (2pin) on this SATA hat, just right biside the power button. And I found that there are already some solution in this forum, all kinds of scripts, can drive the Fan according to the CPU's temperature, or even SSD/HDD's temperature, this are so amazing. 


And then when I tried these scripts, I realized this PWM scripts won't solve the issue I am facing. bacause the SATA hat is getting heater and heater, whilr at this time the CPU's temperature remains in 100F, and the fan is not running. I guess if I can let the fan keep running in full speed, this issue would be solved.


So I went to the FriendlyARM's Wiki page, and found they did provide a scrips to change working method of the  FAN, here is the code:



echo 0 > /sys/class/pwm/pwmchip1/export
sleep 1
echo 0 > /sys/class/pwm/pwmchip1/pwm0/enable
echo 50000 > /sys/class/pwm/pwmchip1/pwm0/period
echo 1 > /sys/class/pwm/pwmchip1/pwm0/enable
echo 45000 > /sys/class/pwm/pwmchip1/pwm0/duty_cycle


I have tried this script with the image name "Friendly Core" (branch of Ubuntu 18.04) image, it works fine.

When system lights up, the fan will keep running, when system is done, the fan will shut down also.

(before I have try the GPIO with another 5V fan, while in this case, the fan wont shutdown even the system is poweroff )


And now my problem is, this script can only run under Ubuntu, how can I make it available in Armbian also?


Will be really appreciate to hear any response from you. 








Link to comment
Share on other sites

2 answers to this question

Recommended Posts

  • 0

Your issue report is not a valid bug report per the Armbian bug reporting instructions (https://www.armbian.com/bugs).  With limited resources the Armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported.  Your report is invalid for one or more of the following reasons (non-exhaustive list):


  • it is for an unsupported board or image (CSC/EOS/WIP/edge)
  • it is for software that is not supported (such as userspace modules installed on top of the core operating system)
  • it has been logged in the wrong forum (for example requests for help that are not actual bug reports)
  • it lacks requested data (armbianmonitor output)
  • it could have been easily solved by a quick search and/or reading documentation


Please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as Common issues / peer to peer technical support or General chit chat)

Link to comment
Share on other sites

Donate your old hardware to community. Start a giveaway Raffle!

  • 0

Werner is right that this probably should have gone in peer to peer support or general chat. This forum is for bug reports with supporting debug information (armbianmonitor).


Maybe he'll move this for you.


In the meantime, maybe this would be worth a read.



Link to comment
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.
Note: Your post will require moderator approval before it will be visible.

Answer this question...

×   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.

  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines