NickS

  • Content Count

    18
  • Joined

  • Last visited

About NickS

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Just happened to be in my office when I heard a sharp crack from one of my 2 Helios4 servers which were both up and running at the time. Noticed that the LED display on one had frozen and could not get that server to respond. Recycled the power on it and although it came up with LED shining, on investigation no power to HDDs or fans. Suprising it booted at all, but it did! Swapped power supplies and issue moved with the PSU so looks like I have a deadish PSU. Pulled it apart and can see 2 of the 1000mf capacitors have blown. Would have replaced them but the massive heat sink is in the way and
  2. Unfortunately no. You'll want to transcode ahead of time and use direct play if you want to use helios as plex server I do, and although I try to rerender content manually, occasionally I just let the software carry the load. I use serviio as my DLNA server on the Helios4. It has the capacity to set up different render profiles for a plethora of target devices so you can present full quality and bitrate to say a TV but less so for a tablet. For remote viewing you'll have to pay the small subscription, but there is a 30day full free test. I'm not sur
  3. The following patch makes fans revert to slow on shutdown rather than top speed! ================================================================================ --- /usr/sbin/fancontrol 2018-02-17 13:54:50.065478090 +0800 +++ /usr/sbin/fancontrol 2018-02-17 13:58:56.910831481 +0800 @@ -334,7 +334,7 @@ # No enable file? Just set to max if [ ! -f $ENABLE ] then - echo $MAX > $1 + echo $MINPWM > $1 return 0 fi @@ -433,9 +433,9 @@ fi # If fanspeed-sensor output shall be used, do it
  4. Hi sirleon, I'm running OMV4 in my deployment, and a recent set of updates broke "psutil.disk_io_counters()". If you are using this routine in your OLED code to fetch disk information then this may be your problem. Anyway you should SSH into your NAS and run the OLED code directly from the SSH terminal and let us see all the nice error messages it throws up :}
  5. OLED panel Here's my version of the sys-oled script with various panels for... System Logo; System Load, Fan & Temperature; HDD activity; Network activity; Temperature & Clock Anyone wishing to deploy it will need to change the location of their HDDs in status_hdd() Also change location of temperature sensor in cpu_temp() depending on your Kernel Apologies for the crude code - Python is not my favourite! oled.py
  6. Hi gprovost Well more and more strange - I checked voltages across ground and all pins for both J10 & J17 at fan values of 255, 50 & 1 (always with fancontrol stopped). Of course with a meter I can only see the mean voltage and not the waveform and duty cycle length. The PWM voltages look a bit random. Does this help you? 12V SENSE PWM-255 PMW-50 PWM-1 J17 12.19 9.2 0.14 0.04 0.01 J10 12.19 9.1 1.19 1.18
  7. Hi Igor, Yes, this is a test system - fresh new latest Stretch image downloaded and installed yesterday.
  8. Igor - that's how it should work I know! But if you read the thread you'll see that they just stay at low speed all the time now. Anyway ... moving on ... following on from gprovosts suggestion... I found a brand new Arctic F8 PWM rev.2 4 pin fan in my workshop and substituted that for one of the Helios4 kit fans. #> echo 255 > /dev/fan-j10/pwm1 #> echo 255 > /dev/fan-j17/pwm1 #> echo 50 > /dev/fan-j10/pwm1 #> echo 50 > /dev/fan-j17/pwm1 Above commands have no effect. Both fans (kit & new replacement) run
  9. Hi gprovost, Yes - I am using the original fans supplied with the Helios4 kit. They were working fine after I applied the fan patch. ie they would go to full speed on boot then settle down to a slower speed and occasionally I would hear them change pitch. I noticed that the fans stopped going to full speed on boot about 6 weeks ago - and only just got around to trying to understand what's going on. I may have some old fans lying around that i could substitute one of them with. Will any 4-pin fan work? Kind regards ... Nick
  10. Hello gprovost, thanks for the quick reply. I stopped fancontrol & tried all 3x2 direct updates to the pwm1 files. A cat of the 2 files showed they had both taken the new values. I saw/heard no change in physical fan speeds - they both just run at a constant low speed. test system used... Linux Helios4 4.14.70-mvebu #266 SMP Wed Sep 19 10:35:09 CEST 2018 armv7l GNU/Linux Kind regards ... Nick
  11. OK yesterday I installed a brand new test system (well it was until you guys slipped 4.14.66 in overnight!) Armbian_Helios4_Debian_Stretch_4.14.20.img.xz Debian 9 Stretch (Kernel 4.14.20) Build date : 17/02/2018 Size : 229 MB I'm seeing exactly the same symptoms. I turned DEBUG=1 on in fancontrol and let it rip and pasted the output below. I then hacked fancontrol to report a temperature value of 99C (99000) and tested again. You will note that fancontrol sets the fan speeds to 255 (max allowed) so fancontrol seems to be working as designed However th
  12. Helios4 Fan problems again! OK, I got hold of an OLED display and have it installed and set up - it works really well - thankyou. I significantly changed your script and included a panel for CPU load, system temperature and system fan speeds. This is where I noticed that fancontrol does indeed increase the fan speed values in /dev/fan-j10/pwm1 and /dev/fan-j17/pwm1 as the temperature value in /dev/thermal-board/temp1_input is seen to rise. However I never see or hear any change to the physical fans' speed. The fans' speed remain constant at boot, a
  13. OK I just found my notes on this and it was a little more complex than I led you to believe. I've added a text file with all my install and update notes. I guess you follow the install notes first and only the update if required. I now remember that I got a lot of this info from a web search, and it did get me up and running with ownCloud. But oC had several red flags that were annoying so I researched fixes for those and included in this text file. Good luck ... Nick owncloud.txt
  14. I have ownCloud running under OpenMediaVault on the Helios4. You need some "NginX Extra Options" and ensure that you give it a "Pool" with user & group set to "www-data" Give pool "Extra Options" of env[PATH] = /usr/local/bin:/usr/bin:/bin Don't forget that whatever you set as your directory in NginX for this server, should be set up as a share with www-data having Read/Write access In your NginX server definition for oC have the following "Extra Options"... client_max_body_size 10G; # set max upload size fastcgi_buffers 64 4K; rewrite ^/c
  15. Thanks gprovost for your quick turn-around. I applied the fancontrol patch and I can confirm that both fans now spin slow after shutdown. Last_phil: if you want a media server that ONLY transcodes when your target device can't support the media file then look at serviio. I've just installed it on my Helios4 and its working well. Typically no dicernible delay when transcode is not required. Only a few seconds delay when transcode is required. If you want serviio install info. for Helios4 platform, let me know and i'll post them here.