NickS

Members
  • Content Count

    15
  • 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. 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 :}
  2. 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
  3. 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 1.18 Kind regards ... Nick
  4. Hi Igor, Yes, this is a test system - fresh new latest Stretch image downloaded and installed yesterday.
  5. 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 exactly the same speed - unchanging. So I find it hard to believe that its a fan problem. I wish I had a scope to put across the fan pins - but sadly I don't. But PWM fans in general work at full power if no PWM signal is present - so I'm surmising that there is a signal on the PWM pin that is providing a short duty cycle keep the speed low. Very odd. Any idea how I might locate the driver and trace what its doing?
  6. 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
  7. 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
  8. 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 the actual fans don't spin any faster? ... here's the DEBUG output of regular fancontrol first followed by my hacked 99C version ===================================================== Loading configuration from /etc/fancontrol ... Common settings: INTERVAL=10 Settings for /dev/fan-j10/pwm1: Depends on /dev/thermal-cpu/temp1_input Controls MINTEMP=55 MAXTEMP=95 MINSTART=50 MINSTOP=50 MINPWM=50 MAXPWM=255 Settings for /dev/fan-j17/pwm1: Depends on /dev/thermal-cpu/temp1_input Controls MINTEMP=55 MAXTEMP=95 MINSTART=50 MINSTOP=50 MINPWM=50 MAXPWM=255 Enabling PWM on fans... Starting automatic fan control... pwmo=/dev/fan-j10/pwm1 tsens=/dev/thermal-cpu/temp1_input fan= mint=55000 maxt=95000 minsa=50 minso=50 minpwm=50 maxpwm=255 tval=74642 pwmpval=255 fanval= min_fanval=1 new pwmval=150 pwmo=/dev/fan-j17/pwm1 tsens=/dev/thermal-cpu/temp1_input fan= mint=55000 maxt=95000 minsa=50 minso=50 minpwm=50 maxpwm=255 tval=73690 pwmpval=255 fanval= min_fanval=1 new pwmval=145 ======================================================== Loading configuration from /etc/fancontrol ... Common settings: INTERVAL=10 Settings for /dev/fan-j10/pwm1: Depends on /dev/thermal-cpu/temp1_input Controls MINTEMP=55 MAXTEMP=95 MINSTART=50 MINSTOP=50 MINPWM=50 MAXPWM=255 Settings for /dev/fan-j17/pwm1: Depends on /dev/thermal-cpu/temp1_input Controls MINTEMP=55 MAXTEMP=95 MINSTART=50 MINSTOP=50 MINPWM=50 MAXPWM=255 Enabling PWM on fans... Starting automatic fan control... ***************** +99000 pwmo=/dev/fan-j10/pwm1 tsens=/dev/thermal-cpu/temp1_input fan= mint=55000 maxt=95000 minsa=50 minso=50 minpwm=50 maxpwm=255 tval=99000 pwmpval=255 fanval= min_fanval=1 new pwmval=255 ***************** +99000 pwmo=/dev/fan-j17/pwm1 tsens=/dev/thermal-cpu/temp1_input fan= mint=55000 maxt=95000 minsa=50 minso=50 minpwm=50 maxpwm=255 tval=99000 pwmpval=255 fanval= min_fanval=1 new pwmval=255 =================================================================
  9. 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, after boot, during shutdown and even after shutdown. I turned on DEBUG in fancontrol and it appears to be doing what it is supposed to do. Every 10 seconds or so it reads the temp and calculates a new fan speed value which it then writes to the two fan control files. I even modified fancontrol to write values 1 to 255 incremented every 10 seconds and saw absolutely no change to the physical fan speed. It looks as if either the fan driver is not using the values set in /dev/fan-j1x/pwm1 to control fan speeds or the physical fans are not responding to the driver. Can you suggest how I debug this please? Overall the continuous low fan speed appears to keep the temperature of the board & CPU at a reasonable level (below 50C) - but the HDDs do get a bit hot from time to time - so I would like to try and fix this. I am running Jessie 4.4.112-mvebu with OMV 3.0.99 (Erasmus)
  10. 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
  11. 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 ^/caldav(.*)$ /remote.php/caldav$1 redirect; rewrite ^/carddav(.*)$ /remote.php/carddav$1 redirect; rewrite ^/webdav(.*)$ /remote.php/webdav$1 redirect; index index.php; error_page 403 /core/templates/403.php; error_page 404 /core/templates/404.php; location = /robots.txt { allow all; log_not_found off; access_log off; } location ~ ^/(data|config|\.ht|db_structure\.xml|README) { deny all; } location / { # The following 2 rules are only needed with webfinger rewrite ^/.well-known/host-meta /public.php?service=host-meta last; rewrite ^/.well-known/host-meta.json /public.php?service=host-meta-json last; rewrite ^/.well-known/carddav /remote.php/carddav/ redirect; rewrite ^/.well-known/caldav /remote.php/caldav/ redirect; rewrite ^(/core/doc/[^\/]+/)$ $1/index.html; try_files $uri $uri/ index.php; } location ~ ^(.+?\.php)(/.*)?$ { try_files $1 = 404; include fastcgi_params; fastcgi_param SCRIPT_FILENAME $document_root$1; fastcgi_param PATH_INFO $2; fastcgi_param HTTPS on; fastcgi_pass $socket; } # Optional: set long EXPIRES header on static assets location ~* ^.+\.(jpg|jpeg|gif|bmp|ico|png|css|js|swf)$ { expires 30d; # Optional: Don't log access to assets access_log off; } add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" ;
  12. 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.
  13. Fan Control - again... I'm now running 4.4.112 + OMV 3.0.97 At power I get maximum fan speen until, I presume, normal fan controls take over. This is fine. However during and after shutdown is complete the fan speed is at also at its maximum and remains at maximum until my power timer cuts the power to the box. Any way you guys can prevent the return to max fan speed during shutdown?
  14. OpenMediaVault image comes with SABNZBD plug-in. I have used SABNZBD for years on several different OS's - installs have usually been issue free. However I cannot get this implementation to access any storage share. Config folder options are restricted to the base folder - which with Helios4 - is the microSD card - a bit useless really for a NAS. Has anyone worked out how to move SABNZBD's incomplete & complete folders to a storage share on one of the HDDs?
  15. Running OpenMediaVault image on Helios4 Supplied fans connected to fan headers continue to spin after shutdown or in standby mode.