November 2, 201411 yr Use Notepad++ and edit your sensors.conf file and swape the temp1 and temp2 labels. For example, right now you have temp1 as mb and temp2 as cpu. Make temp1 cpu and temp 2 mb, save file and reboot. That should switch them in the gui.
November 3, 201411 yr Use Notepad++ and edit your sensors.conf file and swape the temp1 and temp2 labels. For example, right now you have temp1 as mb and temp2 as cpu. Make temp1 cpu and temp 2 mb, save file and reboot. That should switch them in the gui. Yes, I have tried this but with no success. See bellow; sensors_conf chip "w83627dhg-isa-0a10" label temp1 "MB Temp" label temp2 "CPU Temp" This is "sensors" output from console; UNRAiD login: root Linux 3.9.11p-unRAID. root@UNRAiD:~# sensors coretemp-isa-0000 Adapter: ISA adapter Core 0: +33.0 C (high = +89.0 C, crit = +105.0 C) Core 2: +38.0 C (high = +89.0 C, crit = +105.0 C) w83627dhg-isa-0a10 Adapter: ISA adapter Vcore: +0.95 V (min = +0.60 V, max = +1.49 V) in1: +1.82 V (min = +1.62 V, max = +1.99 V) AVCC: +3.25 V (min = +2.98 V, max = +3.63 V) VCC: +3.25 V (min = +2.98 V, max = +3.63 V) in4: +1.53 V (min = +1.35 V, max = +1.65 V) in5: +1.26 V (min = +1.13 V, max = +1.38 V) in6: +1.44 V (min = +1.42 V, max = +1.52 V) 3VSB: +3.23 V (min = +2.98 V, max = +3.63 V) Vbat: +3.17 V (min = +2.70 V, max = +3.30 V) fan1: 0 RPM (min = 753 RPM, div = 128) ALARM fan2: 1591 RPM (min = 712 RPM, div = fan3: 1010 RPM (min = 712 RPM, div = fan4: 0 RPM (min = 753 RPM, div = 128) ALARM fan5: 1035 RPM (min = 712 RPM, div = MB Temp: +40.0 C (high = +60.0 C, hyst = +55.0 C) sensor = thermistor CPU Temp: +33.5 C (high = +95.0 C, hyst = +92.0 C) sensor = CPU diode temp3: +39.0 C (high = +75.0 C, hyst = +70.0 C) sensor = thermistor cpu0_vid: +1.513 V intrusion0: ALARM And this is how the Dynamix is displaying it (see attachment "sensors_conf"). The temperatures are switched. I have also tried with; sensors_conf chip "w83627dhg-isa-0a10" label temp1 "CPU Temp" label temp2 "MB Temp" console output is now wrong; UNRAiD login: root Linux 3.9.11p-unRAID. root@UNRAiD:~# sensors coretemp-isa-0000 Adapter: ISA adapter Core 0: +33.0 C (high = +89.0 C, crit = +105.0 C) Core 2: +37.0 C (high = +89.0 C, crit = +105.0 C) w83627dhg-isa-0a10 Adapter: ISA adapter Vcore: +0.95 V (min = +0.60 V, max = +1.49 V) in1: +1.82 V (min = +1.62 V, max = +1.99 V) AVCC: +3.25 V (min = +2.98 V, max = +3.63 V) VCC: +3.25 V (min = +2.98 V, max = +3.63 V) in4: +1.53 V (min = +1.35 V, max = +1.65 V) in5: +1.26 V (min = +1.13 V, max = +1.38 V) in6: +1.44 V (min = +1.42 V, max = +1.52 V) 3VSB: +3.23 V (min = +2.98 V, max = +3.63 V) Vbat: +3.17 V (min = +2.70 V, max = +3.30 V) fan1: 0 RPM (min = 727 RPM, div = 64) ALARM fan2: 1607 RPM (min = 712 RPM, div = fan3: 1016 RPM (min = 712 RPM, div = fan4: 0 RPM (min = 727 RPM, div = 64) ALARM fan5: 1035 RPM (min = 712 RPM, div = CPU Temp: +40.0 C (high = +60.0 C, hyst = +55.0 C) sensor = thermistor MB Temp: +32.0 C (high = +95.0 C, hyst = +92.0 C) sensor = CPU diode temp3: +39.0 C (high = +75.0 C, hyst = +70.0 C) sensor = thermistor cpu0_vid: +1.513 V intrusion0: ALARM but dynamix (see attachment "sensors_conf (wrong)")is still showing it the same (temps switched)
November 3, 201411 yr There is an issue with the CPU and MB temperatures. This line in the SystemTemps.php sorts the temperatures and the lowest one always shows first (left position) on the webpage. exec("sensors -A|awk '/^CPU Temp/ {print $3*1}; /^M\/?B Temp/ {print $3*1}'",$temp); No matter which temperature is associated with the CPU and MB, the lowest temperature will always show first on the left. In my case the MB temp is lower so it shows in the CPU temperature position. Really a minor issue, but may cause some consternation when trying to get the temperatures to show in the correct positions. I have the same problem, no matter how I label temps in sensors_conf, I always get the MB temp is Processor window and vice-versa. Tho my lowest temperature (CPU) is on the right side (see bellow)
November 3, 201411 yr Author Yeah, this is a known bug. It has been corrected for v6, but needs to be ported to v5 as well.
November 3, 201411 yr Yeah, this is a known bug. It has been corrected for v6, but needs to be ported to v5 as well. Thanks! Not a biggie, but good to know so I stop messing with it Anyway, congrats to all the work you have done
November 3, 201411 yr Any ideas here? Thanks Myk having problems getting my sensor.conf file correct - the labels are not getting changed: sensors: acpitz-virtual-0 Adapter: Virtual device temp1: +27.8 C (crit = +95.0 C) temp2: +29.8 C (crit = +95.0 C) coretemp-isa-0000 Adapter: ISA adapter Physical id 0: +24.0 C (high = +74.0 C, crit = +94.0 C) Core 0: +22.0 C (high = +74.0 C, crit = +94.0 C) Core 1: +23.0 C (high = +74.0 C, crit = +94.0 C) Core 2: +18.0 C (high = +74.0 C, crit = +94.0 C) Core 3: +21.0 C (high = +74.0 C, crit = +94.0 C) nct6776-isa-0a30 Adapter: ISA adapter Vcore: +1.00 V (min = +0.60 V, max = +1.49 V) in1: +1.87 V (min = +1.62 V, max = +1.99 V) AVCC: +3.28 V (min = +2.98 V, max = +3.63 V) +3.3V: +3.28 V (min = +2.98 V, max = +3.63 V) in4: +1.53 V (min = +1.35 V, max = +1.65 V) in5: +1.27 V (min = +1.13 V, max = +1.38 V) in6: +1.46 V (min = +1.42 V, max = +1.52 V) 3VSB: +3.34 V (min = +2.98 V, max = +3.63 V) Vbat: +3.17 V (min = +2.70 V, max = +3.63 V) fan1: 0 RPM (min = 300 RPM) ALARM fan2: 0 RPM (min = 300 RPM) ALARM fan3: 0 RPM (min = 300 RPM) ALARM fan4: 0 RPM (min = 300 RPM) ALARM fan5: 2042 RPM (min = 300 RPM) SYSTIN: +26.0 C (high = +75.0 C, hyst = +70.0 C) sensor = thermistor CPUTIN: +19.5 C (high = +80.0 C, hyst = +75.0 C) sensor = thermistor AUXTIN: +1.0 C (high = +80.0 C, hyst = +75.0 C) sensor = thermistor PECI Agent 0: +29.5 C (high = +95.0 C, hyst = +92.0 C) (crit = +100.0 C) PCH_CHIP_TEMP: +0.0 C PCH_CPU_TEMP: +0.0 C PCH_MCH_TEMP: +0.0 C intrusion0: ALARM intrusion1: OK beep_enable: enabled sensors.conf # lines starting with "#" are comments and ignored # sensor configuration chip "nct6776-isa-0a30" label SYSTIN "MB Temp" label CPUTIN "CPU Temp" can not get the labels for SYSTIN and CPUTIN to change so we page picks it up Thanks for any info Myk
November 3, 201411 yr Author Do sensors -u You get something similar like below: nct6776-isa-0290 Adapter: ISA adapter SYSTIN: temp1_input: 32.000 temp1_max: 0.000 temp1_max_hyst: 0.000 temp1_alarm: 1.000 temp1_type: 4.000 temp1_offset: 0.000 CPUTIN: temp2_input: 41.000 temp2_max: 80.000 temp2_max_hyst: 75.000 temp2_alarm: 0.000 temp2_type: 4.000 temp2_offset: 0.000 AUXTIN: temp3_input: 36.000 temp3_max: 80.000 temp3_max_hyst: 75.000 temp3_alarm: 0.000 temp3_type: 4.000 temp3_offset: 0.000 Instead of the names SYSTIN and CPUTIN use the "tempX" reference, so in my case: sensors.conf contains (also note the 'wildcard' in the chip name): chip "nct6776-isa-*" label temp1 "MB Temp" label temp2 "CPU Temp"
November 3, 201411 yr Thank you much, that did it Myk Do sensors -u You get something similar like below: nct6776-isa-0290 Adapter: ISA adapter SYSTIN: temp1_input: 32.000 temp1_max: 0.000 temp1_max_hyst: 0.000 temp1_alarm: 1.000 temp1_type: 4.000 temp1_offset: 0.000 CPUTIN: temp2_input: 41.000 temp2_max: 80.000 temp2_max_hyst: 75.000 temp2_alarm: 0.000 temp2_type: 4.000 temp2_offset: 0.000 AUXTIN: temp3_input: 36.000 temp3_max: 80.000 temp3_max_hyst: 75.000 temp3_alarm: 0.000 temp3_type: 4.000 temp3_offset: 0.000 Instead of the names SYSTIN and CPUTIN use the "tempX" reference, so in my case: sensors.conf contains (also note the 'wildcard' in the chip name): chip "nct6776-isa-*" label temp1 "MB Temp" label temp2 "CPU Temp"
December 16, 201411 yr I found a newer version of sensors-detect which found my super I/O chip correctly where the version in unRAID didn't. It might help those of you using the System Temp plugin on newer motherboards / chipsets. I just downloaded the file to my flash drive saving it as SD.sh and then ran it. You might have to set permissions to make it executable but I didn't. Here is a link to the lm-sensors page where the link can be found. http://www.lm-sensors.org/wiki/Devices. I'm going to post this in the system temp plugin thread too. Gary
December 25, 201411 yr I found a newer version of sensors-detect which found my super I/O chip correctly where the version in unRAID didn't. It might help those of you using the System Temp plugin on newer motherboards / chipsets. I just downloaded the file to my flash drive saving it as SD.sh and then ran it. You might have to set permissions to make it executable but I didn't. Here is a link to the lm-sensors page where the link can be found. http://www.lm-sensors.org/wiki/Devices. I'm going to post this in the system temp plugin thread too. Gary Thank you for that. I've updated the Setting up CPU and board temperature sensing wiki page with your info. Please feel free to edit, expand, and improve it. bonienl, I also updated the Perl info on the page (in Step 6), but I'm not positive on the Perl and Slackware versions, or the V6 support as to the whole page. When you have a chance, could you look over the page and either make any corrections and improvements, or suggest them to me?
December 26, 201411 yr Bonienl - Can you please tell us if you are planning to update the System Temp plugin to include the new versions that Gary posted? I would rather wait and just use the Update button in the gui.
December 26, 201411 yr I wondered if anyone had the system temp settings for the AsRock E3C226D2I Mini ITX Motherboard. Thanks
December 27, 201411 yr Author I found a newer version of sensors-detect which found my super I/O chip correctly where the version in unRAID didn't. It might help those of you using the System Temp plugin on newer motherboards / chipsets. I just downloaded the file to my flash drive saving it as SD.sh and then ran it. You might have to set permissions to make it executable but I didn't. Here is a link to the lm-sensors page where the link can be found. http://www.lm-sensors.org/wiki/Devices. I'm going to post this in the system temp plugin thread too. Gary Thank you for that. I've updated the Setting up CPU and board temperature sensing wiki page with your info. Please feel free to edit, expand, and improve it. bonienl, I also updated the Perl info on the page (in Step 6), but I'm not positive on the Perl and Slackware versions, or the V6 support as to the whole page. When you have a chance, could you look over the page and either make any corrections and improvements, or suggest them to me? The perl version you are referring to is the correct one for unRAIDv6. For clarity it is better to break step 6 into two paragraphs, one for unRAIDv5 and one for unRAIDv6. In case of unRAIDv5 and dynamix the plugin file can be modified (no-install -> do-install) to get perl and lm-sensors automatically installed by the plugin. In other cases a manual installation of the packages is required. In case of unRAIDv6 the perl and lm-sensors packages are already installed together with the system, but newer versions of these packages need to be installed manually. Or make a request to LT to have it included in an upcoming unRAID version. The v6 version of the temp plugin does not have an auto installer feature included, it relies on the system instead.
January 30, 201511 yr I wondered if anyone had the system temp settings for the AsRock E3C226D2I Mini ITX Motherboard. Thanks This one works for me. sensors.conf file: # sensor configuration for unRAID1 chip "coretemp-isa-0000" label temp1 "CPU Temp" chip "nct6776-isa-0290" label temp2 "MB Temp" go file entry: # Load drivers for temperature monitoring modprobe coretemp modprobe nct6775 /usr/bin/sensors -s
March 3, 201511 yr For anyone else that is as dopey as me, the latest plugin detected my sensors and was up and running within a few minutes. Great work and really easy. Unfortunately I'd spent several hours tapping away in Putty and Notepad++ trying different things, with several reboots before I realised. Unless I actually did do some good with all that messing around and didn't realise it...
August 20, 201510 yr Hope anybody still is watching this topic. I'm running unRaid v6.1-RC5 and trying to get my temps showing but without succes. I've followed everything on the wiki. Isn't there supposed to be a placeholder in the upper bar showing cpu and mb temp? At least I don't see anything. Also if I go into the Dynamix System Temp plugin and click DETECT it doesn't detect anything. The Dynamix Autofan plugin however detects the fans just fine. What am I doing wrong? If I run sensors I get: root@Tower:~# sensors k8temp-pci-00c3 Adapter: PCI adapter Core0 Temp: +45.0 C it8712-isa-0290 Adapter: ISA adapter in0: +1.39 V (min = +0.00 V, max = +4.08 V) in1: +2.61 V (min = +0.00 V, max = +4.08 V) in2: +3.28 V (min = +0.00 V, max = +4.08 V) in3: +2.22 V (min = +0.00 V, max = +4.08 V) in4: +3.02 V (min = +0.00 V, max = +4.08 V) in5: +2.43 V (min = +0.00 V, max = +4.08 V) in6: +2.90 V (min = +0.00 V, max = +4.08 V) in7: +2.51 V (min = +0.00 V, max = +4.08 V) Vbat: +2.67 V fan1: 1061 RPM (min = 0 RPM, div = fan2: 1132 RPM (min = 0 RPM, div = fan3: 1467 RPM (min = 0 RPM, div = temp1: +25.0 C (low = +127.0 C, high = +127.0 C) sensor = thermistor temp2: +36.0 C (low = +127.0 C, high = +127.0 C) sensor = thermistor temp3: +71.0 C (low = +127.0 C, high = +127.0 C) sensor = thermistor cpu0_vid: +1.400 V intrusion0: ALARM I've also created the sensors.conf in /boot/config/plugins/dynamix containing: chip "k8temp-pci-00c3" label temp1 "CPU Temp" label temp2 "MB Temp"
August 21, 201510 yr For the current v6 versions, the temps were moved to the bottom, toward the right, just to the left of "unRAID webGui c 2015 ...". They aren't in the upper bar any more.
October 18, 201510 yr I also have the same problem than X1pheR (system fans shows OK, but no temperature reading) The command "sensors" is working well in the terminal and I gel this: Linux 4.1.7-unRAID. root@Alligator:~# sensors acpitz-virtual-0 Adapter: Virtual device temp1: +27.8°C (crit = +105.0°C) temp2: +29.8°C (crit = +105.0°C) coretemp-isa-0000 Adapter: ISA adapter Physical id 0: +35.0°C (high = +80.0°C, crit = +100.0°C) Core 0: +35.0°C (high = +80.0°C, crit = +100.0°C) Core 1: +33.0°C (high = +80.0°C, crit = +100.0°C) it8728-isa-0a30 Adapter: ISA adapter in0: +1.13 V (min = +0.00 V, max = +3.06 V) in1: +2.04 V (min = +0.00 V, max = +3.06 V) in2: +2.03 V (min = +0.00 V, max = +3.06 V) in3: +2.03 V (min = +0.00 V, max = +3.06 V) in4: +0.01 V (min = +0.00 V, max = +3.06 V) in5: +1.74 V (min = +0.00 V, max = +3.06 V) in6: +1.50 V (min = +0.00 V, max = +3.06 V) 3VSB: +3.38 V (min = +0.00 V, max = +6.12 V) Vbat: +3.07 V fan1: 1004 RPM (min = 0 RPM) fan2: 0 RPM (min = 0 RPM) fan3: 0 RPM (min = 0 RPM) fan4: 0 RPM (min = 0 RPM) fan5: 0 RPM (min = 0 RPM) temp1: +34.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp2: -128.0°C (low = +127.0°C, high = +127.0°C) sensor = disabled temp3: +30.0°C (low = +127.0°C, high = +127.0°C) sensor = Intel PECI intrusion0: ALARM Here are my settings Config folder: go file: sensors.conf file Can anyone check and confirm if there is anything wrong? thanks a lot!
November 19, 201510 yr Am I blind? Where is the actual plugin itself? Or do I have to actually download sensor-detect (lmsensors.org appears down). Is there an actual plugin or do I manually have to set this up with a .conf file?
November 19, 201510 yr Am I blind? Where is the actual plugin itself? Or do I have to actually download sensor-detect (lmsensors.org appears down). Is there an actual plugin or do I manually have to set this up with a .conf file? Dynamix V6 Plugins
February 27, 201610 yr Does this plugin currently have a way to offset/correct a temp value? I know my temp is off by 30 degrees. So I just have to remember to subtract that the value shown but if its possible to have an offset that would be great. Unless I'm just one of very few that is unlucky enough to have sensors that don't report correctly.
February 28, 201610 yr I have a SuperMicro C2SEE motherboard and have followed all the steps in the wiki, but when I go to Settings > TempSettings and tap the Detect button, nothing happens. The page reloads, but there is no visible change. When logged in via SSH, running the `sensors` command accurately shows the MB and CPU temps as `temp1` and `temp2`, respectively. So as far as I can tell, everything seems to be in order. Anyone have any suggestions for how I might troubleshoot this?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.