OMV Sensos not working anymore

jhmiller · 27. September 2016

I have updated the main script, to use it do the following

Code

rm /usr/share/openmediavault/mkconf/sensors
wget -O /usr/share/openmediavault/mkconf/sensors https://raw.githubusercontent.com/OpenMediaVault-Plugin-Developers/openmediavault-sensors/master/usr/share/openmediavault/mkconf/sensors
chmod +x /usr/share/openmediavault/mkconf/sensors
/usr/share/openmediavault/mkconf/sensors

Refresh OMV webui before checking the graphs.

epicfail · 27. September 2016

You are the man

Its now working again....what was the bug?

Can you tell me why only the cpu temp can be shown on my Asrock Q1900 Board? Are there no other sensors or did i something wrong...i mean...that there are no fanspeeds is logical....but MP Temp should be shown or am i wrong?

jhmiller · 27. September 2016

The section for your sensor was missing a vital instruction, i must have removed it without noticing before and thats why it was working but stopped Sorry about that.

The plugin relies on lm-sensors to detect available sensors, if your motherboard has more sensors a newer version of lm-sensors might detect them, most motherboards have a list of available sensors somewhere.
You could also run sensors-detect and see what it says at the end, sometimes it need modules loaded manually to get other sensors to work correctly.

epicfail · 27. September 2016

This is the output of sensors-detect:

Code

root@openmediavault:~# sensors-detect
# sensors-detect revision 6031 (2012-03-07 17:14:01 +0100)
# Board: ASRock Q1900-ITX


This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.


Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): yes
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 15h power sensors...                             No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No


Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Nuvoton NCT6776F Super IO Sensors'                   Success!
    (address 0x290, driver `w83627ehf')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No


Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): yes
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No


Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): yes
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No


Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): no
Now follows a summary of the probes I have just done.
Just press ENTER to continue:


Driver `w83627ehf':
  * ISA bus, address 0x290
    Chip `Nuvoton NCT6776F Super IO Sensors' (confidence: 9)


Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)


To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
w83627ehf
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!


Do you want to add these lines automatically to /etc/modules? (yes/NO)no


Unloading cpuid... OK

Alles anzeigen

Can you give me some advice what i should do now?

jhmiller · 27. September 2016

Run it again but on the last Do you want to add these lines automatically to /etc/modules? (yes/NO)no choose yes
Once it has finished check /etc/modules by doing cat /etc/modules you should see something like

Code

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.


loop


# Generated by sensors-detect on Fri Oct 23 18:00:02 2015
# Chip drivers
coretemp
w83627ehf

Alles anzeigen

reboot OMV and once restarted run sensors to see if you have more sensors available.

If you want to try without loading it to /etc/modules you could manually add them using

modprobe coretemp
modprobe w83627ehf

Then run sensors

I would try this first to see if it works for you, if it does you can do the above to make it permanent.

epicfail · 27. September 2016

Ok tested it and then then make it permanent

It works...now its showing Core Temps and MB Temp....very cool...

Code

root@openmediavault:~# sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +26.8Â°C  (crit = +90.0Â°C)


coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +35.0Â°C  (high = +105.0Â°C, crit = +105.0Â°C)
Core 1:       +35.0Â°C  (high = +105.0Â°C, crit = +105.0Â°C)
Core 2:       +37.0Â°C  (high = +105.0Â°C, crit = +105.0Â°C)
Core 3:       +37.0Â°C  (high = +105.0Â°C, crit = +105.0Â°C)


nct6776-isa-0290
Adapter: ISA adapter
Vcore:        +0.72 V  (min =  +0.00 V, max =  +1.74 V)
in1:          +1.85 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
AVCC:         +3.42 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:        +3.41 V  (min =  +2.98 V, max =  +3.63 V)
in4:          +0.93 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:          +1.68 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
3VSB:         +3.46 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:         +3.30 V  (min =  +2.70 V, max =  +3.63 V)
fan1:        1122 RPM  (min =    0 RPM)  ALARM
fan2:        1170 RPM  (min =    0 RPM)  ALARM
fan3:           0 RPM  (min =    0 RPM)  ALARM
SYSTIN:       +35.0Â°C  (high =  +0.0Â°C, hyst =  +0.0Â°C)  ALARM  sensor = thermistor
CPUTIN:       +32.5Â°C  (high = +80.0Â°C, hyst = +75.0Â°C)  sensor = thermistor
AUXTIN:       +33.0Â°C  (high = +80.0Â°C, hyst = +75.0Â°C)  sensor = thermistor
cpu0_vid:    +0.000 V
intrusion0:  ALARM
intrusion1:  ALARM

Alles anzeigen

Thank you so much....

jhmiller · 27. September 2016

I always try to help where i can, glad you are all setup now.

Aiakos · 9. Oktober 2016

Zitat von jhmiller

I have updated the main script, to use it do the following

Code

rm /usr/share/openmediavault/mkconf/sensors
wget -O /usr/share/openmediavault/mkconf/sensors https://raw.githubusercontent.com/OpenMediaVault-Plugin-Developers/openmediavault-sensors/master/usr/share/openmediavault/mkconf/sensors
chmod +x /usr/share/openmediavault/mkconf/sensors
/usr/share/openmediavault/mkconf/sensors

Refresh OMV webui before checking the graphs.

I have the same problem like epicfail described in his first post (OMV 3.0.43 and 4.7.0 backports kernel). I followed the steps above and since I was not sure what you mean with "refreshing the WebGUI" I rebooted my NAS. However, this did not solve the problem - everything looks exactly like before... Did I miss something?

jhmiller · 9. Oktober 2016

Did sensors ever display graphs for you under OMV2?
What sensors does running sensors show?

Aiakos · 10. Oktober 2016

I have to admit that I never tried in OMV 2. I just stumbled over it when I saw this topic.

Code

root@NAS:~# sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +30.0°C  (high = +90.0°C, crit = +90.0°C)
Core 1:       +30.0°C  (high = +90.0°C, crit = +90.0°C)
Core 2:       +31.0°C  (high = +90.0°C, crit = +90.0°C)
Core 3:       +35.0°C  (high = +90.0°C, crit = +90.0°C)

jhmiller · 11. Oktober 2016

coretemp should work but only for CPU and i think you must have cores enabled in the plugin, try it with cores enabled and without everything else should be off.

If that does not work you could run sh -x /usr/share/openmediavault/mkconf/sensors and let me see the output so i can try to figure out where it's going wrong.

Aiakos · 12. Oktober 2016

Thank you, enabling the "cores" option worked. I also followed your instructions to detect all available sensors. The output now looks like this:

Code

root@NAS:~# sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +31.0°C  (high = +90.0°C, crit = +90.0°C)
Core 1:       +31.0°C  (high = +90.0°C, crit = +90.0°C)
Core 2:       +32.0°C  (high = +90.0°C, crit = +90.0°C)
Core 3:       +32.0°C  (high = +90.0°C, crit = +90.0°C)


nct6776-isa-0290
Adapter: ISA adapter
Vcore:          +0.66 V  (min =  +0.00 V, max =  +1.74 V)
in1:            +0.17 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
AVCC:           +3.44 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:          +3.42 V  (min =  +2.98 V, max =  +3.63 V)
in4:            +0.54 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:            +1.85 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:            +1.66 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
3VSB:           +3.38 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:           +3.12 V  (min =  +2.70 V, max =  +3.63 V)
fan1:             0 RPM  (min =    0 RPM)
fan2:           617 RPM  (min =    0 RPM)
SYSTIN:         +40.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = therm                 istor
CPUTIN:         +32.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN:         -11.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
PCH_CHIP_TEMP:   +0.0°C
PCH_CPU_TEMP:    +0.0°C
PCH_MCH_TEMP:    +0.0°C
cpu0_vid:      +0.000 V
intrusion0:    OK
intrusion1:    OK
beep_enable:   disabled

Alles anzeigen

So there are some additional temperatures and fan speeds now. However, enabling the corresponding options in the plugin does not work. The sad smiley appears instead of a graph... How can I fix this?

jhmiller · 13. Oktober 2016

The nct6776 sensor is in the list of supported hardware, you could check /var/lib/rrdcached/db/localhost/ and see if there are any folders starting with sensors-nct6776 if not you could run sensors-detect and see if it generates the folder and files.

You could also run sh -x /usr/share/openmediavault/mkconf/sensors and give me the output.

Aiakos · 13. Oktober 2016

The folder exsists:

Code

root@NAS:/var/lib/rrdcached/db/localhost/sensors-nct6776-isa-0290# ls
fanspeed-fan1.rrd      temperature-temp3.rrd  voltage-in0.rrd  voltage-in4.rrd  voltage-in8.rrd
fanspeed-fan2.rrd      temperature-temp7.rrd  voltage-in1.rrd  voltage-in5.rrd
temperature-temp1.rrd  temperature-temp8.rrd  voltage-in2.rrd  voltage-in6.rrd
temperature-temp2.rrd  temperature-temp9.rrd  voltage-in3.rrd  voltage-in7.rrd

Since it is too long for this reply, please find the output of the script attached.

//EDIT: After refreshing the graphs it now seems to work!

scorpius.milo · 24. Oktober 2016

Hi,

I'm new and I have a problem with sensors my Motherboard is a Asus Aximus Formula ( Chipset X38 ) a can't have graph sensors working.

My error is " omv-mkconf sensors balls 2>&1 " I have this error in OMV 2.X and 3.X ... I spend a lot of hours try to mke working but nothing I don't understand

command line sensors work fine

Here my output from the command line sh -x /usr/share/openmediavault/mkconf/sensors

If you have a solution thanks and sorry for my bad English

jhmiller · 24. Oktober 2016

Check /var/lib/rrdcached/db/localhost/ and let me know what folders are the that start with sensors- and files inside each folder
Run sensors and let me see the output.

The output.txt file does no have the complete output as the beginning section is missing, that is the most important part.

scorpius.milo · 24. Oktober 2016

Hi, and thanks for the answer

I reinstall all since beginning ( fresh install OMV 2 )

1 - I do all the Update Manager update
2 - I Install "openmediavault-omvextrasorg_latest_all.deb"
3 - I Install Extra and activate Download Manager and Download Manager Testing Repo
3 - I Install Backports Kernel and Reboot
4 - I Install omv-sensors
5 - I Activate all Items sensors except Fahrenheit
6 - I reboot a second time

All it working, I post the files, maybe you can see something, I don't know what I make wrong on the first OMV install

Thanks for all

epicfail · 21. November 2016

Hi jhmiller!

I´ve upgraded to omv 3 (fresh install) and installed the sensors plugin....it works but is not showing the Motherboard Temperatur anymore....i did sensors-detect and let it write to /etc/modules

On omv 2 it worked with that...

Output of sensors:

Code

root@openmediavault:~# sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +26.8Â°C  (crit = +90.0Â°C)


coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +35.0Â°C  (high = +105.0Â°C, crit = +105.0Â°C)
Core 1:       +35.0Â°C  (high = +105.0Â°C, crit = +105.0Â°C)
Core 2:       +37.0Â°C  (high = +105.0Â°C, crit = +105.0Â°C)
Core 3:       +37.0Â°C  (high = +105.0Â°C, crit = +105.0Â°C)


nct6776-isa-0290
Adapter: ISA adapter
Vcore:          +0.93 V  (min =  +0.00 V, max =  +1.74 V)
in1:            +1.86 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
AVCC:           +3.42 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:          +3.41 V  (min =  +2.98 V, max =  +3.63 V)
in4:            +0.93 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:            +1.68 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:            +0.96 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
3VSB:           +3.46 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:           +3.30 V  (min =  +2.70 V, max =  +3.63 V)
fan1:          1126 RPM  (min =    0 RPM)
fan2:          1183 RPM  (min =    0 RPM)
fan3:             0 RPM  (min =    0 RPM)
SYSTIN:         +35.0Â°C  (high =  +0.0Â°C, hyst =  +0.0Â°C)  ALARM  sensor = thermistor
CPUTIN:         +31.5Â°C  (high = +80.0Â°C, hyst = +75.0Â°C)  sensor = thermistor
AUXTIN:         +33.0Â°C  (high = +80.0Â°C, hyst = +75.0Â°C)  sensor = thermistor
PCH_CHIP_TEMP:   +0.0Â°C
PCH_CPU_TEMP:    +0.0Â°C
PCH_MCH_TEMP:    +0.0Â°C
cpu0_vid:      +0.000 V
intrusion0:    ALARM
intrusion1:    ALARM
beep_enable:   disabled

Alles anzeigen

Output of sensors-detect:

Code

root@openmediavault:~# sensors-detect
# sensors-detect revision 6209 (2014-01-14 22:51:58 +0100)
# Board: ASRock Q1900-ITX


This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.


Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): y
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No


Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Nuvoton NCT5577D/NCT6776F Super IO Sensors'          Success!
    (address 0x290, driver `nct6775')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No


Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): y
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No


Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): y
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No


Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): n


Now follows a summary of the probes I have just done.
Just press ENTER to continue:


Driver `nct6775':
  * ISA bus, address 0x290
    Chip `Nuvoton NCT5577D/NCT6776F Super IO Sensors' (confidence: 9)


Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)


To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
nct6775
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!


Do you want to add these lines automatically to /etc/modules? (yes/NO)n


Unloading cpuid... OK

Alles anzeigen

/etc/modules

Code

root@openmediavault:~# cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.




# Generated by sensors-detect on Sun Nov 20 19:57:19 2016
# Chip drivers
coretemp
nct6775

Alles anzeigen

DJ-AS · 21. November 2016

Hi, i just follow the instructions, all sensors are enabled but only have graphs for CPU.
CPU Fan Speed tab show sad faces.

root@NAS-SOLIS:~# sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +40.0°C (high = +76.0°C, crit = +100.0°C)
Core 1: +37.0°C (high = +76.0°C, crit = +100.0°C)

w83627ehf-isa-0290
Adapter: ISA adapter
Vcore: +1.07 V (min = +0.00 V, max = +1.74 V)
in1: +1.08 V (min = +1.84 V, max = +2.04 V) ALARM
AVCC: +3.38 V (min = +2.98 V, max = +3.63 V)
+3.3V: +3.36 V (min = +2.98 V, max = +3.63 V)
in4: +1.71 V (min = +1.02 V, max = +1.50 V) ALARM
in5: +1.74 V (min = +1.94 V, max = +1.78 V) ALARM
in6: +1.97 V (min = +1.78 V, max = +1.91 V) ALARM
3VSB: +3.33 V (min = +2.98 V, max = +3.63 V)
Vbat: +3.15 V (min = +2.70 V, max = +3.63 V)
in9: +1.61 V (min = +1.85 V, max = +2.02 V) ALARM
fan1: 0 RPM (min = 0 RPM, div = 128)
fan2: 2518 RPM (min = 0 RPM, div =
fan3: 0 RPM (min = 10546 RPM, div = 128) ALARM
fan5: 0 RPM (min = 10546 RPM, div = 128) ALARM
temp1: +28.0°C (high = -113.0°C, hyst = -9.0°C) ALARM sensor = thermistor
temp2: +28.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
temp3: +43.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
cpu0_vid: +1.219 V
intrusion0: ALARM

Nothing's change even after reboot...
What's wrong?

jhmiller · 23. November 2016

@epicfail

Try getting the latest main script

Code

rm /usr/share/openmediavault/mkconf/sensors
wget -O /usr/share/openmediavault/mkconf/sensors https://raw.githubusercontent.com/OpenMediaVault-Plugin-Developers/openmediavault-sensors/master/usr/share/openmediavault/mkconf/sensors
chmod +x /usr/share/openmediavault/mkconf/sensors
/usr/share/openmediavault/mkconf/sensors

If you still have issues run sh -x /usr/share/openmediavault/mkconf/sensors and let me take a look at the output

@DJ-AS Are you running OMV2 or OMV3?
Try above to update the main script and if you still have problems run the debug command and let me see the output.

Jetzt mitmachen!