September 28, 20169 yr Hi dmacias! I asked you awhile back about adding my ASRock board to the mix for fan control, but then life got in the way and I never got back to you . Can you confirm the code you need me to input so I can get you what you need to make my board's fan control work? This is for the ASRock EP2C602-4L/D16 Thanks!
September 28, 20169 yr Author Hi dmacias! I asked you awhile back about adding my ASRock board to the mix for fan control, but then life got in the way and I never got back to you . Can you confirm the code you need me to input so I can get you what you need to make my board's fan control work? This is for the ASRock EP2C602-4L/D16 Thanks! Run ipmi-sensors from the command line and post the output. You probably just need to enter the current fan names in the right order in /boot/config/plugins/ipmi/boards.json.
September 29, 20169 yr Run ipmi-sensors from the command line and post the output. You probably just need to enter the current fan names in the right order in /boot/config/plugins/ipmi/boards.json. This is what I get: ~# ipmi-sensors ID | Name | Type | Reading | Units | Event 3 | ATX+5VSB | Voltage | 5.01 | V | 'OK' 4 | +3VSB | Voltage | 3.46 | V | 'OK' 5 | Vcore1 | Voltage | 1.05 | V | 'OK' 6 | Vcore2 | Voltage | 0.86 | V | 'OK' 7 | VCCMA/B | Voltage | 1.34 | V | 'OK' 8 | VCCMC/D | Voltage | 1.35 | V | 'OK' 9 | +1.10_PCH | Voltage | 1.09 | V | 'OK' 10 | +1.50_PCH | Voltage | 1.51 | V | 'OK' 11 | VCCME/F | Voltage | 1.34 | V | 'OK' 12 | VCCMG/H | Voltage | 1.34 | V | 'OK' 13 | BAT | Voltage | 3.24 | V | 'OK' 14 | +3V | Voltage | 3.28 | V | 'OK' 15 | +5V | Voltage | 5.04 | V | 'OK' 16 | +12V | Voltage | 12.00 | V | 'OK' 17 | CPU_FAN1_1 | Fan | 3700.00 | RPM | 'OK' 18 | CPU_FAN2_1 | Fan | 3600.00 | RPM | 'OK' 19 | REAR_FAN1 | Fan | N/A | RPM | N/A 20 | REAR_FAN2 | Fan | N/A | RPM | N/A 21 | FRNT_FAN1 | Fan | N/A | RPM | N/A 22 | FRNT_FAN2 | Fan | 1900.00 | RPM | 'OK' 23 | FRNT_FAN3 | Fan | 2100.00 | RPM | 'OK' 24 | FRNT_FAN4 | Fan | 1900.00 | RPM | 'OK' 25 | CPU_FAN1_2 | Fan | N/A | RPM | N/A 26 | CPU_FAN2_2 | Fan | N/A | RPM | N/A 27 | MB Temperature | Temperature | 39.00 | C | 'OK' 28 | TR1 Temperature | Temperature | 0.00 | C | 'OK' 30 | CPU_BSP1 Temp | Temperature | 44.00 | C | 'OK' 31 | CPU_AP1 Temp | Temperature | 40.00 | C | 'OK' 32 | SATAIII_0 | Drive Slot | N/A | N/A | N/A 33 | SATAIII_1 | Drive Slot | N/A | N/A | N/A 34 | SCU_PORT_0 | Drive Slot | N/A | N/A | N/A 35 | SCU_PORT_1 | Drive Slot | N/A | N/A | N/A 36 | SCU_PORT_2 | Drive Slot | N/A | N/A | N/A 37 | SCU_PORT_3 | Drive Slot | N/A | N/A | N/A
September 29, 20169 yr Author Run ipmi-sensors from the command line and post the output. You probably just need to enter the current fan names in the right order in /boot/config/plugins/ipmi/boards.json. This is what I get: ~# ipmi-sensors ID | Name | Type | Reading | Units | Event 3 | ATX+5VSB | Voltage | 5.01 | V | 'OK' 4 | +3VSB | Voltage | 3.46 | V | 'OK' 5 | Vcore1 | Voltage | 1.05 | V | 'OK' 6 | Vcore2 | Voltage | 0.86 | V | 'OK' 7 | VCCMA/B | Voltage | 1.34 | V | 'OK' 8 | VCCMC/D | Voltage | 1.35 | V | 'OK' 9 | +1.10_PCH | Voltage | 1.09 | V | 'OK' 10 | +1.50_PCH | Voltage | 1.51 | V | 'OK' 11 | VCCME/F | Voltage | 1.34 | V | 'OK' 12 | VCCMG/H | Voltage | 1.34 | V | 'OK' 13 | BAT | Voltage | 3.24 | V | 'OK' 14 | +3V | Voltage | 3.28 | V | 'OK' 15 | +5V | Voltage | 5.04 | V | 'OK' 16 | +12V | Voltage | 12.00 | V | 'OK' 17 | CPU_FAN1_1 | Fan | 3700.00 | RPM | 'OK' 18 | CPU_FAN2_1 | Fan | 3600.00 | RPM | 'OK' 19 | REAR_FAN1 | Fan | N/A | RPM | N/A 20 | REAR_FAN2 | Fan | N/A | RPM | N/A 21 | FRNT_FAN1 | Fan | N/A | RPM | N/A 22 | FRNT_FAN2 | Fan | 1900.00 | RPM | 'OK' 23 | FRNT_FAN3 | Fan | 2100.00 | RPM | 'OK' 24 | FRNT_FAN4 | Fan | 1900.00 | RPM | 'OK' 25 | CPU_FAN1_2 | Fan | N/A | RPM | N/A 26 | CPU_FAN2_2 | Fan | N/A | RPM | N/A 27 | MB Temperature | Temperature | 39.00 | C | 'OK' 28 | TR1 Temperature | Temperature | 0.00 | C | 'OK' 30 | CPU_BSP1 Temp | Temperature | 44.00 | C | 'OK' 31 | CPU_AP1 Temp | Temperature | 40.00 | C | 'OK' 32 | SATAIII_0 | Drive Slot | N/A | N/A | N/A 33 | SATAIII_1 | Drive Slot | N/A | N/A | N/A 34 | SCU_PORT_0 | Drive Slot | N/A | N/A | N/A 35 | SCU_PORT_1 | Drive Slot | N/A | N/A | N/A 36 | SCU_PORT_2 | Drive Slot | N/A | N/A | N/A 37 | SCU_PORT_3 | Drive Slot | N/A | N/A | N/A If you want to control the CPU fans you'll have to change CPU_FAN1 and CPU_FAN2 to CPU_FAN1_1 and CPU_FAN2_1 in the boards.json in /boot/config/plugins/ipmi. I think the rest of your fans should work as long as they are 4 pin PWM fans. You can test the fans using the ipmi-raw commands I described a few posts back. http://lime-technology.com/forum/index.php?topic=39787.msg500260.msg#500260
September 29, 20169 yr Run ipmi-sensors from the command line and post the output. You probably just need to enter the current fan names in the right order in /boot/config/plugins/ipmi/boards.json. This is what I get: ~# ipmi-sensors ID | Name | Type | Reading | Units | Event 3 | ATX+5VSB | Voltage | 5.01 | V | 'OK' 4 | +3VSB | Voltage | 3.46 | V | 'OK' 5 | Vcore1 | Voltage | 1.05 | V | 'OK' 6 | Vcore2 | Voltage | 0.86 | V | 'OK' 7 | VCCMA/B | Voltage | 1.34 | V | 'OK' 8 | VCCMC/D | Voltage | 1.35 | V | 'OK' 9 | +1.10_PCH | Voltage | 1.09 | V | 'OK' 10 | +1.50_PCH | Voltage | 1.51 | V | 'OK' 11 | VCCME/F | Voltage | 1.34 | V | 'OK' 12 | VCCMG/H | Voltage | 1.34 | V | 'OK' 13 | BAT | Voltage | 3.24 | V | 'OK' 14 | +3V | Voltage | 3.28 | V | 'OK' 15 | +5V | Voltage | 5.04 | V | 'OK' 16 | +12V | Voltage | 12.00 | V | 'OK' 17 | CPU_FAN1_1 | Fan | 3700.00 | RPM | 'OK' 18 | CPU_FAN2_1 | Fan | 3600.00 | RPM | 'OK' 19 | REAR_FAN1 | Fan | N/A | RPM | N/A 20 | REAR_FAN2 | Fan | N/A | RPM | N/A 21 | FRNT_FAN1 | Fan | N/A | RPM | N/A 22 | FRNT_FAN2 | Fan | 1900.00 | RPM | 'OK' 23 | FRNT_FAN3 | Fan | 2100.00 | RPM | 'OK' 24 | FRNT_FAN4 | Fan | 1900.00 | RPM | 'OK' 25 | CPU_FAN1_2 | Fan | N/A | RPM | N/A 26 | CPU_FAN2_2 | Fan | N/A | RPM | N/A 27 | MB Temperature | Temperature | 39.00 | C | 'OK' 28 | TR1 Temperature | Temperature | 0.00 | C | 'OK' 30 | CPU_BSP1 Temp | Temperature | 44.00 | C | 'OK' 31 | CPU_AP1 Temp | Temperature | 40.00 | C | 'OK' 32 | SATAIII_0 | Drive Slot | N/A | N/A | N/A 33 | SATAIII_1 | Drive Slot | N/A | N/A | N/A 34 | SCU_PORT_0 | Drive Slot | N/A | N/A | N/A 35 | SCU_PORT_1 | Drive Slot | N/A | N/A | N/A 36 | SCU_PORT_2 | Drive Slot | N/A | N/A | N/A 37 | SCU_PORT_3 | Drive Slot | N/A | N/A | N/A If you want to control the CPU fans you'll have to change CPU_FAN1 and CPU_FAN2 to CPU_FAN1_1 and CPU_FAN2_1 in the boards.json in /boot/config/plugins/ipmi. I think the rest of your fans should work as long as they are 4 pin PWM fans. You can test the fans using the ipmi-raw commands I described a few posts back. http://lime-technology.com/forum/index.php?topic=39787.msg500260.msg#500260 Right on! I'll try that tonight . If it is set properly, will the script stop telling me my board is not supported?
September 29, 20169 yr Author Thanks for the update! Everything is working perfectly now for me! Your welcome. It should change colors too, based on temp.
September 29, 20169 yr Author Run ipmi-sensors from the command line and post the output. You probably just need to enter the current fan names in the right order in /boot/config/plugins/ipmi/boards.json. This is what I get: ~# ipmi-sensors ID | Name | Type | Reading | Units | Event 3 | ATX+5VSB | Voltage | 5.01 | V | 'OK' 4 | +3VSB | Voltage | 3.46 | V | 'OK' 5 | Vcore1 | Voltage | 1.05 | V | 'OK' 6 | Vcore2 | Voltage | 0.86 | V | 'OK' 7 | VCCMA/B | Voltage | 1.34 | V | 'OK' 8 | VCCMC/D | Voltage | 1.35 | V | 'OK' 9 | +1.10_PCH | Voltage | 1.09 | V | 'OK' 10 | +1.50_PCH | Voltage | 1.51 | V | 'OK' 11 | VCCME/F | Voltage | 1.34 | V | 'OK' 12 | VCCMG/H | Voltage | 1.34 | V | 'OK' 13 | BAT | Voltage | 3.24 | V | 'OK' 14 | +3V | Voltage | 3.28 | V | 'OK' 15 | +5V | Voltage | 5.04 | V | 'OK' 16 | +12V | Voltage | 12.00 | V | 'OK' 17 | CPU_FAN1_1 | Fan | 3700.00 | RPM | 'OK' 18 | CPU_FAN2_1 | Fan | 3600.00 | RPM | 'OK' 19 | REAR_FAN1 | Fan | N/A | RPM | N/A 20 | REAR_FAN2 | Fan | N/A | RPM | N/A 21 | FRNT_FAN1 | Fan | N/A | RPM | N/A 22 | FRNT_FAN2 | Fan | 1900.00 | RPM | 'OK' 23 | FRNT_FAN3 | Fan | 2100.00 | RPM | 'OK' 24 | FRNT_FAN4 | Fan | 1900.00 | RPM | 'OK' 25 | CPU_FAN1_2 | Fan | N/A | RPM | N/A 26 | CPU_FAN2_2 | Fan | N/A | RPM | N/A 27 | MB Temperature | Temperature | 39.00 | C | 'OK' 28 | TR1 Temperature | Temperature | 0.00 | C | 'OK' 30 | CPU_BSP1 Temp | Temperature | 44.00 | C | 'OK' 31 | CPU_AP1 Temp | Temperature | 40.00 | C | 'OK' 32 | SATAIII_0 | Drive Slot | N/A | N/A | N/A 33 | SATAIII_1 | Drive Slot | N/A | N/A | N/A 34 | SCU_PORT_0 | Drive Slot | N/A | N/A | N/A 35 | SCU_PORT_1 | Drive Slot | N/A | N/A | N/A 36 | SCU_PORT_2 | Drive Slot | N/A | N/A | N/A 37 | SCU_PORT_3 | Drive Slot | N/A | N/A | N/A If you want to control the CPU fans you'll have to change CPU_FAN1 and CPU_FAN2 to CPU_FAN1_1 and CPU_FAN2_1 in the boards.json in /boot/config/plugins/ipmi. I think the rest of your fans should work as long as they are 4 pin PWM fans. You can test the fans using the ipmi-raw commands I described a few posts back. http://lime-technology.com/forum/index.php?topic=39787.msg500260.msg#500260 Right on! I'll try that tonight . If it is set properly, will the script stop telling me my board is not supported? Post what ipmi-fru reports? Asrock, ASRockRack?
September 29, 20169 yr Author Post what ipmi-fru reports? Asrock, ASRockRack? It returned ASRockRack. Ok you should be good to go. Just edit the boards.json.
October 5, 20169 yr I'm using this plugin just to get a display of my fan speeds and cpu temps. On the dashboard display it causes a shift in the ups status part. See this post. http://lime-technology.com/forum/index.php?topic=36543.1425 When I remove the IPMI plugin the display is correct again. Kevin.
October 5, 20169 yr Author I'm using this plugin just to get a display of my fan speeds and cpu temps. On the dashboard display it causes a shift in the ups status part. See this post. http://lime-technology.com/forum/index.php?topic=36543.1425 When I remove the IPMI plugin the display is correct again. Kevin. I get the same. I'll check it out.
October 6, 20169 yr Hey dmacias, I saw you tweaked NerdPack for 6.3.0-rc1, does the IPMI work plugin for for you on that version of unRAID? IPMI isn't returning any data for me, either for the sensors or the event log. I see error on the console: sh: ipmi-fru: command not found but I'm not sure why it wouldn't be installed? I don't see anything obvious in the syslog, but I've attached my diagnostics in case anything stands out tower-diagnostics-20161005-2015.zip
October 6, 20169 yr Author Hey dmacias, I saw you tweaked NerdPack for 6.3.0-rc1, does the IPMI work plugin for for you on that version of unRAID? IPMI isn't returning any data for me, either for the sensors or the event log. I see error on the console: sh: ipmi-fru: command not found but I'm not sure why it wouldn't be installed? I don't see anything obvious in the syslog, but I've attached my diagnostics in case anything stands out The plugin file doesn't install freeipmi because the logic was for 6.2. You can manually installpkg freeipmi-1.5.1 from the plugin directory. I have a new version but I was just double checking before I released it. I added some new features for mapping the fans to the correct ipmi-raw positions and changed some underlying code. I'm looking through it now. I'll probably go ahead and release it.
October 6, 20169 yr Hey dmacias, I saw you tweaked NerdPack for 6.3.0-rc1, does the IPMI work plugin for for you on that version of unRAID? IPMI isn't returning any data for me, either for the sensors or the event log. I see error on the console: sh: ipmi-fru: command not found but I'm not sure why it wouldn't be installed? I don't see anything obvious in the syslog, but I've attached my diagnostics in case anything stands out The plugin file doesn't install freeipmi because the logic was for 6.2. You can manually installpkg freeipmi-1.5.1 from the plugin directory. I have a new version but I was just double checking before I released it. I added some new features for mapping the fans to the correct ipmi-raw positions and changed some underlying code. I'm looking through it now. I'll probably go ahead and release it. Thanks! installpkg was all it needed edit - the updated plugin works great too thanks!
October 7, 20169 yr Quick question, i am trying to identify which DIMM is giving some correctable errors, but freeipmi isn't very useful.. is there any way i can get ipmiutil/selview installed here? http://www.xkyle.com/an-ipmi-sel-viewing-shootout/ My error: Correctable memory error ; OEM Event Data2 code = 3Bh ; OEM Event Data3 code = 80h It happens relatively frequently, 10 times a month since March.. i only just noticed!
October 7, 20169 yr Author Quick question, i am trying to identify which DIMM is giving some correctable errors, but freeipmi isn't very useful.. is there any way i can get ipmiutil/selview installed here? http://www.xkyle.com/an-ipmi-sel-viewing-shootout/ My error: Correctable memory error ; OEM Event Data2 code = 3Bh ; OEM Event Data3 code = 80h It happens relatively frequently, 10 times a month since March.. i only just noticed! I don't know why Selview was included in that shootout. It's a proprietary Intel app for only a handful of Intel servers. Of course it's gonna be more accurate, it was written by them for their boards. For whatever reason there's no package or slackbuild for ipmiutil that I can find. I'll see if I can compile it from source. Did you try some of the other command line options for freeipmi? This is the command I use for the plugin. /usr/sbin/ipmi-sel --comma-separated-output --output-event-state --no-header-output --interpret-oem-data Try adding one or all of these -W assumesystemevent --output-oem-event-strings or run 'ipmi-sel --help' for more options.
October 8, 20169 yr Author Quick question, i am trying to identify which DIMM is giving some correctable errors, but freeipmi isn't very useful.. is there any way i can get ipmiutil/selview installed here? http://www.xkyle.com/an-ipmi-sel-viewing-shootout/ My error: Correctable memory error ; OEM Event Data2 code = 3Bh ; OEM Event Data3 code = 80h It happens relatively frequently, 10 times a month since March.. i only just noticed! I compiled ipmiutil 3.0.0 and added it to the OP. Give it a try. https://raw.githubusercontent.com/dmacias72/unRAID-plugins/master/source/packages/ipmiutil-3.0.0-x86_64-1.txz
October 9, 20169 yr @dmacias wow thank you that was very kind of you and YES it totally worked i now know the DIMM without having to individually test or pull my hair out! The command i used after installing the pkg was literally just ipmiutil sel and i identified my DIMM. 02ae 10/09/16 23:32:14 MIN EFI Memory #00 Correctable ECC, P1_DIMMC2 6f [a0 3b 80]
October 9, 20169 yr Hi dmacias, I'm running the 2016.10.07a version of the IPMI plugin on a 6.3.0-rc1 VM, and I get this error on the console when booting the VM: modprobe: ERROR: could not insert 'ipmi_si' : No such device Everything works fine since it uses a network connection to access IPMI, but it would be nice to suppress the console error if possible Not urgent at all I've got a current diagnostics over here if it helps: https://lime-technology.com/forum/index.php?topic=52462.msg506075#msg506075
October 10, 20169 yr Author @dmacias wow thank you that was very kind of you and YES it totally worked i now know the DIMM without having to individually test or pull my hair out! The command i used after installing the pkg was literally just ipmiutil sel and i identified my DIMM. 02ae 10/09/16 23:32:14 MIN EFI Memory #00 Correctable ECC, P1_DIMMC2 6f [a0 3b 80] Your welcome. I'm glad you figured it out.
October 10, 20169 yr Author Hi dmacias, I'm running the 2016.10.07a version of the IPMI plugin on a 6.3.0-rc1 VM, and I get this error on the console when booting the VM: modprobe: ERROR: could not insert 'ipmi_si' : No such device Everything works fine since it uses a network connection to access IPMI, but it would be nice to suppress the console error if possible Not urgent at all I've got a current diagnostics over here if it helps: https://lime-technology.com/forum/index.php?topic=52462.msg506075#msg506075 I added -q to modprobe and sent any output to null. It will still create a log entry though. I can't do anything about that.
October 10, 20169 yr Sorry, now I'm getting this: /bin/bash: line 34: [: too many arguments /bin/bash: line 34: [: missing ']' I uninstalled / rebooted / reinstalled / rebooted to confirm it was the ipmi plugin that was throwing the error.
October 10, 20169 yr Author Sorry, now I'm getting this: /bin/bash: line 34: [: too many arguments /bin/bash: line 34: [: missing ']' I uninstalled / rebooted / reinstalled / rebooted to confirm it was the ipmi plugin that was throwing the error. Thanks. I pushed the wrong plg file. Updated again.
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.