freed00m

/usr/sbin/fancontrol
line 44 >> Max=
precisely defines the nominal speed when fancontrol is inactive,
which means, at the ignition of the device before the launching of the processes (including fancontrol) and at the extintion of the device when the processes are interrupted (including fancontrol)
and it can last several minutes when you have installed OMV and some containers.
But yes indeed you hear the fans roar for a second at the start and the end before the unit shuts down completely.
 
I leave MAX=80 because from memory during my previous tests, the fans make an audible noise, which allowed me to verify that my unit restarted or turned off when I sent a command from my phone.
A memory because it's been a while...
 

 
 
/usr/sbin/fancontrol
 
 
 
Line 394 >> declare -A PWM_ENABLE_ORIG_STATE
Line 395 >> declare -A PWM_ORIG_STATE
>> /usr/sbin/pwmconfig
 
 
 
 
line 46  >> function LoadConfig
line 108 
 
Line 521 >> function UpdateFanSpeeds
Line 609
 

Hi,
 
updating Helios64 (Armbian Bullseye) to the latest kernel (Armbian 22.02.1 with Linux 5.15.25-rockchip64) went flawlessly - it seems to be stable so far (Thanks!).
However, emmc read/write speed is still reduced by a factor of 2 compared to linux 5.10.43.
 
@piter75 Do you know if there is anybody trying to re-enable high emmc read/write speeds in newer kernels  ?

Long shot. In the wiki on the corresponding screenshot you have the choice between /dev/sda1, /dev/sdb1 and /dev/sdc1, which are all partitions. Your sda isn't partitioned. Nor is your md0, but maybe the algorithm simply skips all device nodes which does not end in a number.
So put a partition on your disk.

Added to watchlist. If it stays cheap enough, I'll buy it. 
 
Can't guarantee you "Supported" flag, but I will have it running edge and notice problems
 
 

This is a quirk for UAS device applied to all Armbian release, it is not specific to Helios64.
https://github.com/armbian/build/blob/2b1306443d973033c6f2cef7b221f5c25f0af98d/packages/bsp/common/usr/lib/armbian/armbian-hardware-optimization#L379

@freed00m
Could you disable NCQ and see how if you manage to complete the SMART extended test.
 
Edit /boot/armbianEnv.txt and add the following line :
 
extraargs=libata.force=noncq  
 

Hello,
 
I've bought 3 new identical drives and put 2 of them in the Helios64 and 1 onto my desktop.
I ran smartctl longtest+shortest on both drives simultanously but all of them were aborted/interupted by host.
 
`# /usr/sbin/smartctl -a /dev/sda`
Output: http://ix.io/2OLt
 
On my desktop the longtest from smartctl succeeds without error and all 3 drives received the same care, I just bough them and installed them, so unlikely the drives are physically damaged. 
 
The complete diagnostic log: http://ix.io/2OBr
 
So anyone got an idea why are my SMART extended tests being canceled?
 
Note: I've tried even the trick with running background task to prevent drives from some vendor sleep `while true; do dd if=/dev/sda of=/dev/null count=1; sleep 60; done`