Jump to content
dmacias

[Plugin] IPMI for unRAID 6.1+

1345 posts in this topic Last Reply

Recommended Posts

Hello,

 

Thanks for writing this plugin dmacius.  

 

I'm having an issue with some fans spinning at 100% no matter what (do not think this is a bad threshold issue).  For context, I'm running unraid 6.8.2,I have a CSE-846 chassis, with X9DRI-LN4F+ motherboard, and 3x iPPC Noctua 3000 fans for the "fanwall", as well as some fans for my CPU coolers.

 

The CPU fans are running consistently as they should (I will +1 the earlier suggestion of adding a temperature option of having the CPU fans be driven by max(Temp_CPU1, Temp_CPU2)).  The problem is with the 3x iPPC noctua fans in the fanwall.   When I adjust a setting regarding, say minimum fan speed, the fans go to 0, and then the threshold limitation kicks on, and they spool up to 100%.

 

What is odd here is that it doesn't matter what I set the minimum fan speed to, the fans will always go to 0 rpms, I've set minimum fan speeds of over 80%, doesn't matter, they go to 0 rpms, then I assume the threshold kicks in and spools them to 100% (but I can't be certain).

 

I have tried the fan wall fans to be plugged into FAN1/2/3 headers, and I've tried them plugged in the FANA/B header (using a 2-1 splitter on one of the connectors), but I have right now the fans connected into FANA/B connectors and the CPU connectors plugged into FAN4 (using a 2-way splitter).

 

I think the plugin is trying to set the fan speed accordingly.  Here is a segment from my /var/log/ipmifan logfile:

2020-02-21 22:42:31 fan control config file updated, reloading settings
2020-02-21 22:42:32 Fan:Temp, FAN1234(38%):CPU1 Temp(35°C), FANA(32%):HDD Temp(35°C)
2020-02-21 22:44:33 Fan:Temp, FAN1234(35%):CPU1 Temp(33°C), FANA(32%):HDD Temp(35°C)
2020-02-21 22:45:33 Fan:Temp, FAN1234(31%):CPU1 Temp(30°C), FANA(32%):HDD Temp(35°C)
2020-02-21 22:47:34 Fan:Temp, FAN1234(37%):CPU1 Temp(34°C), FANA(32%):HDD Temp(35°C)
2020-02-21 22:48:34 Fan:Temp, FAN1234(38%):CPU1 Temp(35°C), FANA(32%):HDD Temp(35°C)

If I look at my Readings page tho, you can see the results in the image. 

 

image.thumb.png.c2567c90a2f1ea66d77ffe892d29d263.png

 

Is there anything else I can check/do?

 

Thanks again.

Share this post


Link to post
Hello,
 
Thanks for writing this plugin dmacius.  
 
I'm having an issue with some fans spinning at 100% no matter what (do not think this is a bad threshold issue).  For context, I'm running unraid 6.8.2,I have a CSE-846 chassis, with X9DRI-LN4F+ motherboard, and 3x iPPC Noctua 3000 fans for the "fanwall", as well as some fans for my CPU coolers.
 
The CPU fans are running consistently as they should (I will +1 the earlier suggestion of adding a temperature option of having the CPU fans be driven by max(Temp_CPU1, Temp_CPU2)).  The problem is with the 3x iPPC noctua fans in the fanwall.   When I adjust a setting regarding, say minimum fan speed, the fans go to 0, and then the threshold limitation kicks on, and they spool up to 100%.
 
What is odd here is that it doesn't matter what I set the minimum fan speed to, the fans will always go to 0 rpms, I've set minimum fan speeds of over 80%, doesn't matter, they go to 0 rpms, then I assume the threshold kicks in and spools them to 100% (but I can't be certain).
 
I have tried the fan wall fans to be plugged into FAN1/2/3 headers, and I've tried them plugged in the FANA/B header (using a 2-1 splitter on one of the connectors), but I have right now the fans connected into FANA/B connectors and the CPU connectors plugged into FAN4 (using a 2-way splitter).
 
I think the plugin is trying to set the fan speed accordingly.  Here is a segment from my /var/log/ipmifan logfile:
2020-02-21 22:42:31 fan control config file updated, reloading settings2020-02-21 22:42:32 Fan:Temp, FAN1234(38%):CPU1 Temp(35°C), FANA(32%):HDD Temp(35°C)2020-02-21 22:44:33 Fan:Temp, FAN1234(35%):CPU1 Temp(33°C), FANA(32%):HDD Temp(35°C)2020-02-21 22:45:33 Fan:Temp, FAN1234(31%):CPU1 Temp(30°C), FANA(32%):HDD Temp(35°C)2020-02-21 22:47:34 Fan:Temp, FAN1234(37%):CPU1 Temp(34°C), FANA(32%):HDD Temp(35°C)2020-02-21 22:48:34 Fan:Temp, FAN1234(38%):CPU1 Temp(35°C), FANA(32%):HDD Temp(35°C)

If I look at my Readings page tho, you can see the results in the image. 
 
image.thumb.png.c2567c90a2f1ea66d77ffe892d29d263.png
 
Is there anything else I can check/do?
 
Thanks again.

See the first post about setting Supermicro critical thresholds with the sensor config editor.

Share this post


Link to post
32 minutes ago, dmacias said:
3 hours ago, ogi said:
Hello,
 
Thanks for writing this plugin dmacius.  
 
I'm having an issue with some fans spinning at 100% no matter what (do not think this is a bad threshold issue).  For context, I'm running unraid 6.8.2,I have a CSE-846 chassis, with X9DRI-LN4F+ motherboard, and 3x iPPC Noctua 3000 fans for the "fanwall", as well as some fans for my CPU coolers.
 
The CPU fans are running consistently as they should (I will +1 the earlier suggestion of adding a temperature option of having the CPU fans be driven by max(Temp_CPU1, Temp_CPU2)).  The problem is with the 3x iPPC noctua fans in the fanwall.   When I adjust a setting regarding, say minimum fan speed, the fans go to 0, and then the threshold limitation kicks on, and they spool up to 100%.
 
What is odd here is that it doesn't matter what I set the minimum fan speed to, the fans will always go to 0 rpms, I've set minimum fan speeds of over 80%, doesn't matter, they go to 0 rpms, then I assume the threshold kicks in and spools them to 100% (but I can't be certain).
 
I have tried the fan wall fans to be plugged into FAN1/2/3 headers, and I've tried them plugged in the FANA/B header (using a 2-1 splitter on one of the connectors), but I have right now the fans connected into FANA/B connectors and the CPU connectors plugged into FAN4 (using a 2-way splitter).
 
I think the plugin is trying to set the fan speed accordingly.  Here is a segment from my /var/log/ipmifan logfile:


2020-02-21 22:42:31 fan control config file updated, reloading settings2020-02-21 22:42:32 Fan:Temp, FAN1234(38%):CPU1 Temp(35°C), FANA(32%):HDD Temp(35°C)2020-02-21 22:44:33 Fan:Temp, FAN1234(35%):CPU1 Temp(33°C), FANA(32%):HDD Temp(35°C)2020-02-21 22:45:33 Fan:Temp, FAN1234(31%):CPU1 Temp(30°C), FANA(32%):HDD Temp(35°C)2020-02-21 22:47:34 Fan:Temp, FAN1234(37%):CPU1 Temp(34°C), FANA(32%):HDD Temp(35°C)2020-02-21 22:48:34 Fan:Temp, FAN1234(38%):CPU1 Temp(35°C), FANA(32%):HDD Temp(35°C)
 

If I look at my Readings page tho, you can see the results in the image. 
 
image.thumb.png.c2567c90a2f1ea66d77ffe892d29d263.png
 
Is there anything else I can check/do?
 
Thanks again.

See the first post about setting Supermicro critical thresholds with the sensor config editor.

Screenshot above showed I modified the critical thresholds; but the original post said to put all the values between 200 and 300, which I have now done, but still have the same issue:

 

image.thumb.png.b82dcf6db56ff82b3d77171846cb9c34.png

 

Again, doesn't matter what I set the minimum fan speed percentage at, when I hit apply, the fans just go to 0 RPM.

 

Also for reference, this is the relevant section of the config file:

 

Section 2684_FANA
	## Possible values: Yes/No
	Enable_All_Event_Messages                                                   Yes
	## Possible values: Yes/No
	Enable_Scanning_On_This_Sensor                                              Yes
	## Possible values: Yes/No
	Enable_Assertion_Event_Lower_Critical_Going_Low                             Yes
	## Possible values: Yes/No
	Enable_Assertion_Event_Lower_Non_Recoverable_Going_Low                      Yes
	## Possible values: Yes/No
	Enable_Assertion_Event_Upper_Non_Critical_Going_High                        Yes
	## Possible values: Yes/No
	Enable_Assertion_Event_Upper_Critical_Going_High                            Yes
	## Possible values: Yes/No
	Enable_Assertion_Event_Upper_Non_Recoverable_Going_High                     Yes
	## Possible values: Yes/No
	Enable_Deassertion_Event_Lower_Critical_Going_Low                           Yes
	## Possible values: Yes/No
	Enable_Deassertion_Event_Lower_Non_Recoverable_Going_Low                    Yes
	## Possible values: Yes/No
	Enable_Deassertion_Event_Upper_Non_Critical_Going_High                      Yes
	## Possible values: Yes/No
	Enable_Deassertion_Event_Upper_Critical_Going_High                          Yes
	## Possible values: Yes/No
	Enable_Deassertion_Event_Upper_Non_Recoverable_Going_High                   Yes
	## Give valid input for sensor type = Fan; units = RPM
	Lower_Non_Critical_Threshold                                                225.000000
	## Give valid input for sensor type = Fan; units = RPM
	Lower_Critical_Threshold                                                    225.000000
	## Give valid input for sensor type = Fan; units = RPM
	Lower_Non_Recoverable_Threshold                                             225.000000
	## Give valid input for sensor type = Fan; units = RPM
	Upper_Non_Critical_Threshold                                                3000.000000
	## Give valid input for sensor type = Fan; units = RPM
	Upper_Critical_Threshold                                                    3000.000000
	## Give valid input for sensor type = Fan; units = RPM
	Upper_Non_Recoverable_Threshold                                             3000.000000
	## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis
	Positive_Going_Threshold_Hysteresis                                         75.000000
	## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis
	Negative_Going_Threshold_Hysteresis                                         75.000000
EndSection
Section 2751_FANB
	## Possible values: Yes/No
	Enable_All_Event_Messages                                                   Yes
	## Possible values: Yes/No
	Enable_Scanning_On_This_Sensor                                              Yes
	## Possible values: Yes/No
	Enable_Assertion_Event_Lower_Critical_Going_Low                             Yes
	## Possible values: Yes/No
	Enable_Assertion_Event_Lower_Non_Recoverable_Going_Low                      Yes
	## Possible values: Yes/No
	Enable_Assertion_Event_Upper_Non_Critical_Going_High                        Yes
	## Possible values: Yes/No
	Enable_Assertion_Event_Upper_Critical_Going_High                            Yes
	## Possible values: Yes/No
	Enable_Assertion_Event_Upper_Non_Recoverable_Going_High                     Yes
	## Possible values: Yes/No
	Enable_Deassertion_Event_Lower_Critical_Going_Low                           Yes
	## Possible values: Yes/No
	Enable_Deassertion_Event_Lower_Non_Recoverable_Going_Low                    Yes
	## Possible values: Yes/No
	Enable_Deassertion_Event_Upper_Non_Critical_Going_High                      Yes
	## Possible values: Yes/No
	Enable_Deassertion_Event_Upper_Critical_Going_High                          Yes
	## Possible values: Yes/No
	Enable_Deassertion_Event_Upper_Non_Recoverable_Going_High                   Yes
	## Give valid input for sensor type = Fan; units = RPM
	Lower_Non_Critical_Threshold                                                225.000000
	## Give valid input for sensor type = Fan; units = RPM
	Lower_Critical_Threshold                                                    225.000000
	## Give valid input for sensor type = Fan; units = RPM
	Lower_Non_Recoverable_Threshold                                             225.000000
	## Give valid input for sensor type = Fan; units = RPM
	Upper_Non_Critical_Threshold                                                3000.000000
	## Give valid input for sensor type = Fan; units = RPM
	Upper_Critical_Threshold                                                    3000.000000
	## Give valid input for sensor type = Fan; units = RPM
	Upper_Non_Recoverable_Threshold                                             3000.000000
	## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis
	Positive_Going_Threshold_Hysteresis                                         75.000000
	## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis
	Negative_Going_Threshold_Hysteresis                                         75.000000
EndSection

 

Share this post


Link to post



Screenshot above showed I modified the critical thresholds; but the original post said to put all the values between 200 and 300, which I have now done, but still have the same issue:
 
image.thumb.png.b82dcf6db56ff82b3d77171846cb9c34.png
 
Again, doesn't matter what I set the minimum fan speed percentage at, when I hit apply, the fans just go to 0 RPM.
 
Also for reference, this is the relevant section of the config file:
 
Section 2684_FANA## Possible values: Yes/NoEnable_All_Event_Messages                                                   Yes## Possible values: Yes/NoEnable_Scanning_On_This_Sensor                                              Yes## Possible values: Yes/NoEnable_Assertion_Event_Lower_Critical_Going_Low                             Yes## Possible values: Yes/NoEnable_Assertion_Event_Lower_Non_Recoverable_Going_Low                      Yes## Possible values: Yes/NoEnable_Assertion_Event_Upper_Non_Critical_Going_High                        Yes## Possible values: Yes/NoEnable_Assertion_Event_Upper_Critical_Going_High                            Yes## Possible values: Yes/NoEnable_Assertion_Event_Upper_Non_Recoverable_Going_High                     Yes## Possible values: Yes/NoEnable_Deassertion_Event_Lower_Critical_Going_Low                           Yes## Possible values: Yes/NoEnable_Deassertion_Event_Lower_Non_Recoverable_Going_Low                    Yes## Possible values: Yes/NoEnable_Deassertion_Event_Upper_Non_Critical_Going_High                      Yes## Possible values: Yes/NoEnable_Deassertion_Event_Upper_Critical_Going_High                          Yes## Possible values: Yes/NoEnable_Deassertion_Event_Upper_Non_Recoverable_Going_High                   Yes## Give valid input for sensor type = Fan; units = RPMLower_Non_Critical_Threshold                                                225.000000## Give valid input for sensor type = Fan; units = RPMLower_Critical_Threshold                                                    225.000000## Give valid input for sensor type = Fan; units = RPMLower_Non_Recoverable_Threshold                                             225.000000## Give valid input for sensor type = Fan; units = RPMUpper_Non_Critical_Threshold                                                3000.000000## Give valid input for sensor type = Fan; units = RPMUpper_Critical_Threshold                                                    3000.000000## Give valid input for sensor type = Fan; units = RPMUpper_Non_Recoverable_Threshold                                             3000.000000## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresisPositive_Going_Threshold_Hysteresis                                         75.000000## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresisNegative_Going_Threshold_Hysteresis                                         75.000000EndSectionSection 2751_FANB## Possible values: Yes/NoEnable_All_Event_Messages                                                   Yes## Possible values: Yes/NoEnable_Scanning_On_This_Sensor                                              Yes## Possible values: Yes/NoEnable_Assertion_Event_Lower_Critical_Going_Low                             Yes## Possible values: Yes/NoEnable_Assertion_Event_Lower_Non_Recoverable_Going_Low                      Yes## Possible values: Yes/NoEnable_Assertion_Event_Upper_Non_Critical_Going_High                        Yes## Possible values: Yes/NoEnable_Assertion_Event_Upper_Critical_Going_High                            Yes## Possible values: Yes/NoEnable_Assertion_Event_Upper_Non_Recoverable_Going_High                     Yes## Possible values: Yes/NoEnable_Deassertion_Event_Lower_Critical_Going_Low                           Yes## Possible values: Yes/NoEnable_Deassertion_Event_Lower_Non_Recoverable_Going_Low                    Yes## Possible values: Yes/NoEnable_Deassertion_Event_Upper_Non_Critical_Going_High                      Yes## Possible values: Yes/NoEnable_Deassertion_Event_Upper_Critical_Going_High                          Yes## Possible values: Yes/NoEnable_Deassertion_Event_Upper_Non_Recoverable_Going_High                   Yes## Give valid input for sensor type = Fan; units = RPMLower_Non_Critical_Threshold                                                225.000000## Give valid input for sensor type = Fan; units = RPMLower_Critical_Threshold                                                    225.000000## Give valid input for sensor type = Fan; units = RPMLower_Non_Recoverable_Threshold                                             225.000000## Give valid input for sensor type = Fan; units = RPMUpper_Non_Critical_Threshold                                                3000.000000## Give valid input for sensor type = Fan; units = RPMUpper_Critical_Threshold                                                    3000.000000## Give valid input for sensor type = Fan; units = RPMUpper_Non_Recoverable_Threshold                                             3000.000000## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresisPositive_Going_Threshold_Hysteresis                                         75.000000## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresisNegative_Going_Threshold_Hysteresis                                         75.000000EndSection

 



I would try 200 or 300 thresholds instead of 225. I've had trouble with the bmc accepting numbers other than whole hundreds.

Share this post


Link to post
4 hours ago, dmacias said:


 

 


I would try 200 or 300 thresholds instead of 225. I've had trouble with the bmc accepting numbers other than whole hundreds.

 

Thanks for the reply, for some reason my sensor seems to want multiples of 75, so 200 would not work:

 

image.thumb.png.7535a162b4223ab5d3d541d5b3296679.png

 

When I set to 300, I still get the same behavior described earlier.  Here is the ipmi log, the log indicates the plugin is trying to do things correctly, but for some reason the fan is just going to 0, then the fan spools up again to 100%

 


2020-02-22 07:29:07 Starting Fan Control
2020-02-22 07:29:07 Setting fans to full speed
2020-02-22 07:29:17 Fan:Temp, FAN1234(32%):CPU1 Temp(31°C), FANA(36%):HDD Temp(0°C)
2020-02-22 07:30:17 Fan:Temp, FAN1234(31%):CPU1 Temp(24°C), FANA(36%):HDD Temp(0°C)
2020-02-22 07:30:40 Stopping Fan Control
2020-02-22 07:30:40 Setting fans to auto
2020-02-22 07:31:56 Starting Fan Control
2020-02-22 07:31:56 Setting fans to full speed
2020-02-22 07:32:06 Fan:Temp, FAN1234(31%):CPU1 Temp(24°C), FANA(36%):HDD Temp(25°C)
2020-02-22 07:32:16 fan control config file updated, reloading settings
2020-02-22 07:32:17 Fan:Temp, FAN1234(31%):CPU1 Temp(25°C), FANA(36%):HDD Temp(25°C)
2020-02-22 07:33:57 fan control config file updated, reloading settings
2020-02-22 07:33:57 Fan:Temp, FAN1234(31%):CPU1 Temp(25°C), FANA(40%):HDD Temp(25°C)
2020-02-22 07:35:58 Fan:Temp, FAN1234(35%):CPU1 Temp(33°C), FANA(40%):HDD Temp(27°C)
2020-02-22 07:36:59 Fan:Temp, FAN1234(31%):CPU1 Temp(30°C), FANA(40%):HDD Temp(27°C)
2020-02-22 07:38:09 fan control config file updated, reloading settings
2020-02-22 07:38:09 Fan:Temp, FAN1234(31%):CPU1 Temp(28°C), FANA(50%):HDD Temp(27°C)

 

Share this post


Link to post

okay, things are weird, I decided to open up the chassis to see what's going on, turns out while the reading reports 0 RPMs, the fans are still actually spinning....so I suppose this is a problem of an incorrect fan speed reading....

Share this post


Link to post

muahahahaha I finally got it I think.  What was missing was that I was missing a few sensors from the "Display Settings/Global Available Sensors".  Things started to work when I enabled the two HDD Status snesors (both read N/A) and PCH Temp; I added all those at the same time, so I'm not sure which one specifically did the trick.

 

 

EDIT: thanks you dmacias for making this plugin and providing assistance in these threads! 

 

EDIT2:  Rebooted the machine, still having the same problem, when I enable fan control, fans report 0 RPM, and then go full bore.... but when reporting 0 rpm, fans are actually spinning under power....

 

EDIT3: on another reboot, fans are spinning at 225rpm ....and not in the critical zone, so yay?

Edited by ogi

Share this post


Link to post

Just following up earlier posts, things are going well a day later; .... i think one of the issues I was fighting, and what originally caused this whole thing to begin with was that I removed some fans....which on its own I think is fine, but doing IPMI fan control on a section that is 'missing' fans probably won't work, so until the IPMI interface knows to not even bother looking for them, ....probably shouldn't worry about fans spooling up to 100%....

 

That said I'd like to reboot the server a bunch more to make sure things come back up as expected; it's undergoing too much use for now.

Share this post


Link to post



Just following up earlier posts, things are going well a day later; .... i think one of the issues I was fighting, and what originally caused this whole thing to begin with was that I removed some fans....which on its own I think is fine, but doing IPMI fan control on a section that is 'missing' fans probably won't work, so until the IPMI interface knows to not even bother looking for them, ....probably shouldn't worry about fans spooling up to 100%....
 
That said I'd like to reboot the server a bunch more to make sure things come back up as expected; it's undergoing too much use for now.


Thanks for following up. The fans will be at full speed before and after the fan control script is run. By design I reset the fans to full in case something happens and your fans are stuck at 200 rpms burning up your cpu or hard drives. So at start and shutdown they will be at full. And sometimes at start it can take s little longer depending on your poll settings. Also removing fans should have no affect. The script just checks temps and blindly sends the fan speed commands based on the settings. It wouldn't work to check fan rpms since they aren't always accurate and differ between fans.

Share this post


Link to post
3 hours ago, dmacias said:

Thanks for following up. The fans will be at full speed before and after the fan control script is run. By design I reset the fans to full in case something happens and your fans are stuck at 200 rpms burning up your cpu or hard drives. So at start and shutdown they will be at full. And sometimes at start it can take s little longer depending on your poll settings. Also removing fans should have no affect. The script just checks temps and blindly sends the fan speed commands based on the settings. It wouldn't work to check fan rpms since they aren't always accurate and differ between fans.

 

Huh, is there any other log I can lookup to see what's was happening (or in my case, was not happening)?  The contents of /var/log/ipmifan appear correct....

Share this post


Link to post

Follow up part 2; so after having the system run stable for a few days as expected, I decided to yank out the fans connected to the FAN5 and FAN6 headers (was planning on doing this anyway as they do not provide much cooling at this point).  Unfortunately this has resulted in the same behavior as before, where regardless of what i set the minimum fan speed percentage to be, the fans go to effectively 0 RPM, and the critical threshold kicks in, bringing the fans connected to FAN1, FAN2 and FAN3 connectors to 100%. 

 

I'm starting to be suspicious that this may be a motherboard specific issue...

Share this post


Link to post
Follow up part 2; so after having the system run stable for a few days as expected, I decided to yank out the fans connected to the FAN5 and FAN6 headers (was planning on doing this anyway as they do not provide much cooling at this point).  Unfortunately this has resulted in the same behavior as before, where regardless of what i set the minimum fan speed percentage to be, the fans go to effectively 0 RPM, and the critical threshold kicks in, bringing the fans connected to FAN1, FAN2 and FAN3 connectors to 100%. 
 
I'm starting to be suspicious that this may be a motherboard specific issue...
Are your bmc and bios firmware up to date?

Share this post


Link to post

I managed to restore the functionality I had previously.  First, I disabled "load config @ unraid start", then I restored the BMC to factory settings.  I then booted up and copied fan.cfg, ipmi.cfg into the directory and copy/pasted the contents of ipmi-sensors.config into the editor.  The changes took.

 

For now I'll leave the system as is, unless there is some debug information you would be interested in having dmacias.

 

Thanks again for this plugin, if it wasn't for your work, my wife would give me the death glare at every opportunity :D

Share this post


Link to post

Hi,

 

I hope it is ok to ask for help here. I have found out I can use ipmitool (on ubuntu) to get the current power draw. I use this command: 

ipmitool -H HOST-NAME-OF-SYSTEM -U USER-NAME -P PASSWORD dcmi power reading

But I am no wizard in programming. So my question is this: Is it possible to add either the command or the functionality to the plugin version if IPMItool?

 

/Alphahelix

Share this post


Link to post



Hi,
 
I hope it is ok to ask for help here. I have found out I can use ipmitool (on ubuntu) to get the current power draw. I use this command: 
ipmitool -H HOST-NAME-OF-SYSTEM -U USER-NAME -P PASSWORD dcmi power reading

But I am no wizard in programming. So my question is this: Is it possible to add either the command or the functionality to the plugin version if IPMItool?
 
/Alphahelix



This plugin doesn't use ipmitool. It uses freeipmi. There's an ipmi-dcmi that's part of freeipmi. You might try that

Share this post


Link to post
39 minutes ago, dmacias said:

This plugin doesn't use ipmitool. It uses freeipmi. There's an ipmi-dcmi that's part of freeipmi. You might try that

 

 

Hi again.

 

First thanks for your correction, Its logical that it won't work if I use the wrong program. ;) 

Now I did manage to find the command for ipmi-dcmi

ipmi-dcmi --hostname=HOST-NAME-OF-SYSTEM --username=USER-NAME --password=PASSWORD --get-system-power-statistics | grep "Current Power"

Can anyone help me with a guide to have the plugin include this command when collection the other IPMI data? I would very much like to see the power draw now the feature is there. 

 

Thanks in advance

 

/Alphahelix

Share this post


Link to post
 
Hi again.
 
First thanks for your correction, Its logical that it won't work if I use the wrong program.  
Now I did manage to find the command for ipmi-dcmi
ipmi-dcmi --hostname=HOST-NAME-OF-SYSTEM --username=USER-NAME --password=PASSWORD --get-system-power-statistics | grep "Current Power"

Can anyone help me with a guide to have the plugin include this command when collection the other IPMI data? I would very much like to see the power draw now the feature is there. 
 
Thanks in advance
 
/Alphahelix

You'd need to provide the command you used and the output.

Share this post


Link to post
On 5/7/2015 at 5:08 PM, dmacias said:

To set the thresholds for to the config editor tab. Then select sensors config and scroll down to each fan and change the thresholds. I set all three thresholds for FANA to 200. The fans on this header are for my hard drives. I set all the other fans to 300. These are my case and CPU fans. Just click save after you're done. You may have to click load config @ unraid start if the settings aren't persistent after a reboot.

Hi

 

Thanks for a wonderful plugin.  Absolutely great.

 

Could you help me with lowering the fan speed threshold on the motherboard BMC, please?  I have an X10 board.

 

The config tab is blank so I'm unable to scroll down to the fans as you suggest above.  Am I doing something wrong or is there a command to type in?

 

So many thanks

 

 

 

D

Share this post


Link to post
Posted (edited)

I just got my system up and running with my Supermicro X11SCH-F, E-2278G, and Supermicro CSE-836BE16-R920B. Everything is looking good but I've noticed that my CPU fan is stuck at 400 RPM and just isn't responding to any increases in percentage.

 

I think it has a lot to do with how I currently have things laid out:

 

FAN1: FAN-0074L4 (on fan wall)

FAN2: FAN-0074L4 (on fan wall)

FAN3: N/A (hopefully will be 3rd 0074L4 that's currently on FANB once I get a extension cable)

FAN4: 2 x FAN-0104L4's (on back of case) that are bound together with a cable splitter

FANA: Noctua NH-9DL with NF-A9 (already lowered the thresholds to 300rpm)

FANB: FAN-0074L4 (on fan wall)

 

Right now, FAN1234 are tied to HDD Temps and FANA is tied to CPU Temp.

 

I'm sure I have the CPU fan plugged into the wrong fan slot but I'm open to suggestions on how to configure this.

Edited by ramblinreck47

Share this post


Link to post

Hi,

Thanks so much for writing this IPMI plugin.  I'm in the midst of building out my Unraid server on a Supermicro X11SCA-F motherboard and Xeon E-2278G CPU.  The plugin seems to be missing blue-on.png in the readings tab.  See screen capture below.

 

image.thumb.png.0fce5dc6e5398db7601c809d9c5b6173.png

Share this post


Link to post
Posted (edited)
56 minutes ago, bwnautilus said:

Hi,

Thanks so much for writing this IPMI plugin.  I'm in the midst of building out my Unraid server on a Supermicro X11SCA-F motherboard and Xeon E-2278G CPU.  The plugin seems to be missing blue-on.png in the readings tab.  See screen capture below.

 

 

Hi...  Great Question!!!  I have the same board, only with an i7-8700K.  I've noticed that DIMM slot sensors will only read certain sticks.  Currently I have slots A1 and B1 populated with 2x 16GB Crucial 32GB DDR4 2666 which do not show temp sensor readings.  But I also tested these CORSAIR (2 x 16GB) 288-Pin DDR4 SDRAM DDR4 2666 on the board and IPMI sensor readings do show.  I believe the unRAID plugin will only read the sensors from the board itself so you should see the same reading(s) when selecting the "Server Health" tab from your IPMI web-client.

 

 

Edited by cpthook

Share this post


Link to post
1 hour ago, cpthook said:

Hi...  Great Question!!!  I have the same board, only with an i7-8700K.  I've noticed that DIMM slot sensors will only read certain sticks.  Currently I have slots A1 and B1 populated with 2x 16GB Crucial 32GB DDR4 2666 which do not show temp sensor readings.  But I also tested these CORSAIR (2 x 16GB) 288-Pin DDR4 SDRAM DDR4 2666 on the board and IPMI sensor readings do show.  I believe the unRAID plugin will only read the sensors from the board itself so you should see the same reading(s) when selecting the "Server Health" tab from your IPMI web-client.

 

 

Sorry if I wasn't clear.  The issue I'm having with the plugin is that the sensors tab is supposed to be showing a blue dot for those readings that are not present.  It's showing a broken icon symbol in the status column.  If you look at the page source it's referencing blue-on.png for any N/A reading.  The file blue-on.png is not in the /usr/local/emhttp/plugins/dynamix/images/ directory.

 

FYI I'm using 2 sticks of 32GB ram from NEMIX and their temperature is being read correctly in the picture I uploaded.

Share this post


Link to post
1 hour ago, bwnautilus said:

Sorry if I wasn't clear.  The issue I'm having with the plugin is that the sensors tab is supposed to be showing a blue dot for those readings that are not present.  It's showing a broken icon symbol in the status column.  If you look at the page source it's referencing blue-on.png for any N/A reading.  The file blue-on.png is not in the /usr/local/emhttp/plugins/dynamix/images/ directory.

 

FYI I'm using 2 sticks of 32GB ram from NEMIX and their temperature is being read correctly in the picture I uploaded.

Ahhhh  Got it!  I have the same broken icons as well for N/A sensors that are not active.  Never really paid attention until you pointed it out.  Thanks!

Share this post


Link to post

I installed the plugin.  All the values are either green or blue, except for this one which is yellow:

MB Temp 107°C

 

That temperature seems really high to me.  Is it accurate?  Should I be concerned and is there anyway to fix it?  Thanks.

Share this post


Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.