Fans go on full and stay there after doing an update in OMV web control panel... Helios64 NAS

  • Did an update - fans now stuck on full - suspect there was an error in the update and config. was changed... any generic suggestions?


    Some details;


    Helios64 NAS with OMV 5.6.21 (Usul) / Linux 5.15.25-rockchip64

    Only plug ins are 'flashmemory' and 'OMV extras' (base plugin) - (probably need shell in a box or similar)


    Uptime was 357 days :) and used 'Update Management' from the web control page.

    It looked like it didn't go 100% smoothly (?) did a couple of reboots... it comes back (files are available, etc)

    The only problem is with the fans... they stay on full...


    Do I;

    1. log in via SSH and look at config? (I'm at the noob+ level...) - &/or try to run 1st aid OMV tool (I'm rusty on this...)

    2. goto the Helios [Kobol.io] doco's and forum also... it may be device specific

    3. Nuke it all and Reinstall OMV from Orbit... ^^


    This device is accessed on a home office LAN from LINUX (Mint) and Windows 8.1 (yep! :D ) devices...


    The NAS is available despite the fans being on full, I will shut it down because I use the older Helios 4 as my daily NAS... also a good device (they don't make either any more!)

    Helios4 [ARM SBC] with OMV6... seemples! :) >> AXZEZ carrier + CM4 RPi [ARM 'SBC' ] with OMV6 (in dev't) 8)

  • OK... doing some reading, if anyone else has this problem, or something similar (I've had some fan speed issues with notebook PCs running Manjaro &/or Mint (I think?) )


    I found a pretty detailed page on kobol.io (who make the device)

    https://wiki.kobol.io/helios64…m-fan-control-under-linux


    Quote

    UDEV rules

    Since hwmon order can change between kernel version or even between reboot, on Armbian we use udev rules as workaround. The rules can be found here (mainline) or here (legacy kernel 4.4) and need to be copied to /etc/udev/rules.d/

    /dev/fan-p6, /dev/fan-p7, /dev/thermal-cpu and /dev/thermal-board are symlinks generated by the udev rules.


    ... I don't know ANYTHING about this so any suggestions would be great. If I work out a solution, of course, I will share, it may be of use?


    Next; going to make a coffee, have a good read through and see if there's any way fwd.

    Time for a tinkerin' ;)

    Helios4 [ARM SBC] with OMV6... seemples! :) >> AXZEZ carrier + CM4 RPi [ARM 'SBC' ] with OMV6 (in dev't) 8)

    • Official Post

    OMV doesn't do anything with the fans on any system. This is probably caused by an Armbian update and since Kobol is defunct, the helios64 is going to die a slow death (I have two of them).

    omv 6.9.0-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.16 | compose 6.10.3 | cputemp 6.1.3 | mergerfs 6.3.7


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Yep, I would also say you have to consult the kobol-forum. I remember some threads about the fan issue which I never had. Here is one thread for example (https://forum.armbian.com/topi…3-fan-not-working-at-all/) there might be others, too.


    ryecoaaron I do hope it's gonna be a sloooooooow death although it is inevitable as Kobol pulled the plug. But I love that unit very much and I do believe that I will have fun with it for another long period.

    • Official Post

    I do hope it's gonna be a sloooooooow death although it is inevitable as Kobol pulled the plug. But I love that unit very much and I do believe that I will have fun with it for another long period.

    Mine have been sitting unplugged for months. The 2.5GBe port was horribly unstable.

    omv 6.9.0-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.16 | compose 6.10.3 | cputemp 6.1.3 | mergerfs 6.3.7


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    I do believe I got one of the last shipments (but I am unaware if they changed anything with these ports btw).

    I have a developer board and one of the first shipments. I also haven't tried it in months. So, maybe the driver got better.

    omv 6.9.0-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.16 | compose 6.10.3 | cputemp 6.1.3 | mergerfs 6.3.7


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • OMV doesn't do anything with the fans on any system. This is probably caused by an Armbian update and since Kobol is defunct, the helios64 is going to die a slow death (I have two of them).

    Agreed... I went to Armbian and there are a couple of posts that cover keeping H64 going... I will experiment and summarise here... (over the weekend?)

    The 2.5GBe port was horribly unstable.

    Apparently there is a fix but it involves making physical changes to the board... possible to break something... when I find the link I will post, may be of interest. It is from the Kobol team, not a 3rd party hack.

    But I love that unit very much and I do believe that I will have fun with it for another long period.

    Me too! :)

    It's a shame that the Helios4 has a support member on Armbian but the Helios64 does not... I don't have the skill/knowledge. But there are a couple of postings from people who are keeping them going so there is hope.

    Helios4 [ARM SBC] with OMV6... seemples! :) >> AXZEZ carrier + CM4 RPi [ARM 'SBC' ] with OMV6 (in dev't) 8)

    • Official Post

    Apparently there is a fix but it involves making physical changes to the board... possible to break something... when I find the link I will post, may be of interest. It is from the Kobol team, not a 3rd party hack.

    They might have mentioned it to me when I was working with them but I honestly don't remember. I was pretty mad that I had a unstable nas that I paid for a bunch of stuff including a 2.5GBe switch I didn't need.


    It's a shame that the Helios4 has a support member on Armbian but the Helios64 does not... I don't have the skill/knowledge. But there are a couple of postings from people who are keeping them going so there is hope.

    As far as I know, it was same people who developed both boards but I can't say that for sure. Hopefully support keeps coming. It really doesn't have any exotic components. I would like for my boards to not be paperweights.

    omv 6.9.0-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.16 | compose 6.10.3 | cputemp 6.1.3 | mergerfs 6.3.7


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    I found the link to a possible fix if this is relevant to you

    Thanks but I am connecting the 2.5G port to a 2.5G switch. So, that isn't affecting me. The driver was actually segfaulting or dropping connection. Maybe that has been fixed but I haven't plugged mine in in month.

    omv 6.9.0-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.16 | compose 6.10.3 | cputemp 6.1.3 | mergerfs 6.3.7


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Did you ever managed to solve this SidAny ? I updated and now i have the same problem, the fans are spinning at 100% constantly. Like before the update the 1 second when starting or shutting down.

    I could not find any solution in the armbian forum :/

    I actually managed to solve it with some help in a chat:
    `/etc/fancontrol` is the path `FCTEMPS=/dev/fan-p6/pwm1=/dev/thermal-cpu/temp1_input /dev/fan-p7/pwm1=/dev/thermal-cpu/temp1_input` but `/dev/thermal-cpu/` does not exist (anymore?), but `/dev/thermal-board/` is available -> changed the path, `sudo systemctl restart fancontrol.system` and everything is silent.


    Additionally it is possible to recreate the fancontrol file with pwmconfig, but the service need to be stopped for that.

  • marianne /dev/thermal-board is below the CPU temp by 15 degrees. The fan will never triggers.

    Can you give the output from:

    Code
    head -v /sys/devices/virtual/thermal/thermal_zone0/hwmon*/name

    and:

    Code
    sudo udevadm info /sys/devices/virtual/thermal/thermal_zone0/hwmon*


    Those should be detected and the symlink to /dev/thermal-cpu created by udev rule /etc/udev/rules.d/90-helios64-hwmon.rules which is part of armbian-bsp-cli-helios64 (which should be there as it also creates /dev/thermal-board, but who knows, it is better to check)

  • Did you ever managed to solve this SidAny ?

    HI!! sorry, have been away from OMV forums for a long time. Regarding helios64; the 'Armbian' support looks like it is legacy only... I have been relying on the Helios 4 kit with 4 NAS HDD's (WD_REDS) has worked well. Still on OMV 5!! (see below).


    Result; Helios 4 is my 'daily driver' (still in use ~3.5 yrs) while; Helios 64 is on HOLD for now... not in active use...


    NEW PROJECT; NAS build based on the AXZEZ CM4 carrier board... see how this one goes!

    Helios4 [ARM SBC] with OMV6... seemples! :) >> AXZEZ carrier + CM4 RPi [ARM 'SBC' ] with OMV6 (in dev't) 8)

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!