I am having the reboot issue again.
Temperature CPU?
-
- OMV 1.0
- joq3
-
-
I suspect it is something to do with your modprobe command, double check it is loaded after a reboot. The old reboot issue was fixed and is working (for my setup atleast)
-
You were right. It works just fine again now. Thanks for the hint. ☺
-
-
Well, we knew this from the testing previously, but for the record completeness, all is good in my system (w83627thf), after the upgrade to the latest version 1.0.22.
-
-
-
-
Your sensor (it8712-isa-0290) as far as I can tell was never added to the supported sensors list so I don't know why you said it was working in an earlier version. I will double check this to see if I accidently removed it.
That is not a true plugin, it is a script you run to make the files needed for graphs to be shown. From what I can tell you need to tell it your sensors where as this plugin tries to detect your sensors.
I will add this sensor in the next version.
-
Hello
And I think it's the reason why, in my case, the graph in your plugin show cpu's temp even if my sensor is not recognized
When I try to run plugin's 1.0.5 version , script is already running
Thank for your reply and for all you do (great job !!)
-
I have also been having trouble with seeing Motherboard Temp, CPU Fan speed, SYS fan speed in my OMV installation. However, this is likely because not many people have tried this on an HP Proliant server before.
I've attached output from sensors, omv-sensors-detect, mkconf as well as what the HP Health cli is able to tell me at first brush.
I'd love some expert assistance to point me in the right direction.
Thanks!
-
-
It looks like the only sensors it will use is the coretemp's.
It does not find any other modules for the other sensors. You could try searching you server model along with lm-sensors to see if there is a work around.I know some sensors needs to load the modules before running sensors-detect.
-
@jhmiller is it possible to reset the fan-graphs?
I solved a problem where the reported RPM-values were way too high.
As a result, the graph's y-axis scaling is also over the top and the current (correct) values don't even show up.
Would be nice if there was a solution to this, now the week/month/year graphs have no use at all.Also, the CPU temps could stay as they are (but I don't mind resetting them too).
I guess something like this does the trick?
followed byCoderm /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
-
Hello,
I try to setup the plugin sensor 1.0.22 on my OMV 2.1.23 (Stone burner)
but no graphs until now
I already try to finf in the forum but no ideas
I try to reboot with no effectsany help will be appreciated
thanks a lot in advance,
Vincent
--lm-sensor package seems to be ok
sensors-detect output:
Code
Alles anzeigen# sensors-detect revision 6031 (2012-03-07 17:14:01 +0100) # System: ACER Aspire E500 # Board: ACER ERC410M▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ 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): 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... No 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): Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... Yes Found `ITE IT8712F Super IO Sensors' Success! (address 0xa10, driver `it87') 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): # DMI data unavailable, please consider installing dmidecode 2.7 # or later for better results. 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): 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): Using driver `i2c-ali15x3' for device 0000:00:1e.1: Acer Labs 1533/1543 Using driver `i2c-ali1535' for device 0000:00:1e.1: Acer Labs 1535 Module i2c-dev loaded successfully. Next adapter: Radeon i2c bit bus DVI_DDC (i2c-0) Do you want to scan it? (yes/NO/selectively): Next adapter: Radeon i2c bit bus VGA_DDC (i2c-1) Do you want to scan it? (yes/NO/selectively): Next adapter: Radeon i2c bit bus MONID (i2c-2) Do you want to scan it? (yes/NO/selectively): Next adapter: Radeon i2c bit bus GPIOPAD_MASK (i2c-3) Do you want to scan it? (yes/NO/selectively): Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `it87': * ISA bus, address 0xa10 Chip `ITE IT8712F Super IO Sensors' (confidence: 9) To load everything that is needed, add this to /etc/modules: #----cut here---- # Chip drivers it87 #----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) Unloading i2c-dev... OK Unloading cpuid... OK
sensors output:
Code
Alles anzeigenit8712-isa-0a10 Adapter: ISA adapter in0: +1.33 V (min = +0.00 V, max = +4.08 V) in1: +1.22 V (min = +0.00 V, max = +4.08 V) in2: +3.26 V (min = +0.00 V, max = +4.08 V) +5V: +2.98 V (min = +0.00 V, max = +4.08 V) in4: +2.93 V (min = +0.00 V, max = +4.08 V) in5: +1.74 V (min = +0.00 V, max = +4.08 V) in6: +1.62 V (min = +0.00 V, max = +4.08 V) 5VSB: +2.96 V (min = +0.00 V, max = +4.08 V) Vbat: +4.08 V fan1: 1180 RPM (min = 0 RPM, div = 8) fan2: 1095 RPM (min = 0 RPM, div = 8) fan3: 0 RPM (min = 0 RPM, div = 8) temp1: +35.0°C (low = -1.0°C, high = +127.0°C) sensor = thermistor temp2: +45.0°C (low = -1.0°C, high = +127.0°C) sensor = thermal diode temp3: -128.0°C (low = -1.0°C, high = +127.0°C) sensor = disabled cpu0_vid: +1.050 V intrusion0: ALARM
ls /var/lib/rrdcached/db/localhost
-
-
-
<a href="http://forums.openmediavault.org/index.php/User/2137-sinedv/">@sinedv</a>
Add the line <code class="inlineCode">it87</code> to the file <code class="inlineCode">/etc/modules</code> reboot and run <code class="inlineCode">sensors-detect</code> again. Then run <code class="inlineCode">ls /var/lib/rrdcached/db/localhost</code> to see if it has the correct folder, it should have something like sensors-it87XXXXXXXThanks for your fast reply:
"it87" already include into /etc/modules
reboot ok
sensors-detect doneCode
Alles anzeigenls -al /var/lib/rrdcached/db/localhost/ total 56 drwxr-xr-x 14 root root 4096 janv. 2 19:04 . drwxr-xr-x 3 root root 4096 mai 23 2014 .. drwxr-xr-x 2 root root 4096 juil. 12 20:15 cpu-0 drwxr-xr-x 2 root root 4096 mai 23 2014 df drwxr-xr-x 2 root root 4096 mai 23 2014 df-media-91035952-3c55-4883-9be2-e82a23de1bbe drwxr-xr-x 2 root root 4096 juil. 12 20:15 df-media-9891aa96-1d00-41c3-9903-fe73913600bf drwxr-xr-x 2 root root 4096 mai 23 2014 df-root drwxr-xr-x 2 root root 4096 mai 23 2014 interface drwxr-xr-x 2 root root 4096 juil. 12 20:15 interface-eth0 drwxr-xr-x 2 root root 4096 mai 23 2014 interface-eth1 drwxr-xr-x 2 root root 4096 sept. 18 17:17 interface-lo drwxr-xr-x 2 root root 4096 juil. 12 20:15 load drwxr-xr-x 2 root root 4096 juil. 12 20:15 memory drwxr-xr-x 2 root root 4096 juil. 12 20:16 rrdcached
still no sensors rrd data
-
modprobe it87
Run that then sensors-detect then check the folder again.
-
-
modeprobe done
still nothing for sensors in the folder /var/lib/rrdcached/db/localhost/
any other idea?
do I have to uninstall the package en reinstall it?
-
You could try that but I doubt that it will make any difference.
This plugin relies on lm-sensors working correctly, if it does not then the plugin will not work.
You could try asking the developers of lm-sensors if they have any ideas. -
I have an it87 sensor, but it seems to be working, i.e. giving me output when I run "sensors" (please ignore CPU fan RPM, I'm not sitting here wearing earplugs, it's just beeing stupid and it was also doing that when this PC had windows on it ?() :
root@STURE:~# sensors
it8728-isa-0228
Adapter: ISA adapter
in0: +1.39 V (min = +0.00 V, max = +3.06 V)
in1: +1.49 V (min = +0.00 V, max = +3.06 V)
in2: +1.99 V (min = +0.00 V, max = +3.06 V)
in3: +2.05 V (min = +0.00 V, max = +3.06 V)
in4: +2.32 V (min = +0.00 V, max = +3.06 V)
in5: +2.22 V (min = +0.00 V, max = +3.06 V)
in6: +2.23 V (min = +0.00 V, max = +3.06 V)
3VSB: +3.34 V (min = +0.00 V, max = +6.12 V)
Vbat: +3.14 V
fan1: 135000 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 1261 RPM (min = 0 RPM)
fan4: 1229 RPM (min = 0 RPM)
fan5: 0 RPM (min = 0 RPM)
temp1: +28.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
temp2: -8.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
temp3: +53.0°C (low = +127.0°C, high = +127.0°C) sensor = disabled
intrusion0: ALARMtemp1=MB
temp3=CPU
fan1=CPU
Edit: fan3 and fan4= System fans, and I have one leftover connector so I guess fan2 will also be sysfan, but not sure why fan5 is there...However, I do not get any graphs, just the grey smileyfaces. It seems I have the neccesary files?
root@STURE:~# ls /var/lib/rrdcached/db/localhost/sensors*/
fanspeed-fan1.rrd fanspeed-fan5.rrd voltage-in0.rrd voltage-in4.rrd voltage-in8.rrd
fanspeed-fan2.rrd temperature-temp1.rrd voltage-in1.rrd voltage-in5.rrd
fanspeed-fan3.rrd temperature-temp2.rrd voltage-in2.rrd voltage-in6.rrd
fanspeed-fan4.rrd temperature-temp3.rrd voltage-in3.rrd voltage-in7.rrd(Folder containing these files is /var/lib/rrdcached/db/localhost/sensors-it8728-isa-0228/)
I noticed my sensor is named it8728 but the mkconf only have it8718 as closest match, can this be an explanation?:
http://pastebin.com/mpsDQqPB -
-
I am currently converting some plugins to OMV 3. If I get the chance (and remember) I will try to add your sensor so that it picks up the correct data.
-
Added it8728 to the latest version.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!