EdgarWallace Posted August 19, 2016 Share Posted August 19, 2016 I still have occurrences when the temperature is high and the log is reporting 100% fan speed but in reality fans are running at 500rpm: 2016-08-19 06:02:06 Starting Fan Control 2016-08-19 06:02:08 FRNT_FAN1(100%):M/B Temperature(46°C) MB is now at 66°C and the hottest disc at 45° [EDIT]Maybe fixed, I decreased the thresholds in the motherboards smart fan settings. Seems to be important with the settings that I am using. Can anyone confirm that this is a correct understanding? Quote Link to comment
dmacias Posted August 29, 2016 Author Share Posted August 29, 2016 I still have occurrences when the temperature is high and the log is reporting 100% fan speed but in reality fans are running at 500rpm: 2016-08-19 06:02:06 Starting Fan Control 2016-08-19 06:02:08 FRNT_FAN1(100%):M/B Temperature(46°C) MB is now at 66°C and the hottest disc at 45° [EDIT]Maybe fixed, I decreased the thresholds in the motherboards smart fan settings. Seems to be important with the settings that I am using. Can anyone confirm that this is a correct understanding? It will be linear between 20C - 45C. Below 20C fan will be off. 45C and above fan will be full speed. 32.5C would be 50%. Quote Link to comment
mattbr Posted August 30, 2016 Share Posted August 30, 2016 Hey, I'm having this weird annoying issue with a Supermicro X10 xeon-d board, which had the SM "cycling" thing going at default... Switched a few things around in the IPMI settings, and the board will now boot with fans at a reasonable speed, which'll ramp up to full-on after a minute or so, so I'd suspect only once Unraid loads... I mean, it's not throwing errors or anything, it's mostly that it probably makes the box noiser than it could or should be... (I've tried putting the upper thresholds to proper variants of the manufacturer's max speeds, didn't change a thing, and also tried adding the Dynamix temp/autofan plugins on top, no luck with that, can't detect the PWM controller or any other temp sensor than the CPU's coretemp) Any clue as to what I'm doing wrong ? Section 607_FAN1 ## this is the silent wings case fan ## 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_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_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 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 1600.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 1700.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 1800.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 674_FAN2 ## this is a noctua 92mm ## 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_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_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 400.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 2100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 2400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 22000.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 741_FAN3 ## this is a noctua F12 ## 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_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_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 400.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 2100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 2400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 22000.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 808_FAN4 EndSection Section 875_FANA ## this is a noctua 92mm ## 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_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_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 400.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 2100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 2400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 22000.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Quote Link to comment
dmacias Posted August 30, 2016 Author Share Posted August 30, 2016 Hey, I'm having this weird annoying issue with a Supermicro X10 xeon-d board, which had the SM "cycling" thing going at default... Switched a few things around in the IPMI settings, and the board will now boot with fans at a reasonable speed, which'll ramp up to full-on after a minute or so, so I'd suspect only once Unraid loads... I mean, it's not throwing errors or anything, it's mostly that it probably makes the box noiser than it could or should be... (I've tried putting the upper thresholds to proper variants of the manufacturer's max speeds, didn't change a thing, and also tried adding the Dynamix temp/autofan plugins on top, no luck with that, can't detect the PWM controller or any other temp sensor than the CPU's coretemp) Any clue as to what I'm doing wrong ? Section 607_FAN1 ## this is the silent wings case fan ## 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_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_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 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 1600.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 1700.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 1800.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 674_FAN2 ## this is a noctua 92mm ## 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_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_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 400.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 2100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 2400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 22000.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 741_FAN3 ## this is a noctua F12 ## 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_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_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 400.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 2100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 2400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 22000.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 808_FAN4 EndSection Section 875_FANA ## this is a noctua 92mm ## 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_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_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 400.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 2100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 2400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 22000.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection I don't think you're doing anything wrong. That seems to be the way the Supermicro boards work. There's only a low, medium and high speed. If you look earlier in the thread there are some ipmi-raw commands. But if you set it to medium you might have overhating issues. The ipmi settings and thresholds only affect warnings mainly. Changing them won't change how the fans operate. It‘s useful to eliminate any low rpm warnings. Quote Link to comment
saarg Posted August 30, 2016 Share Posted August 30, 2016 Hey, I'm having this weird annoying issue with a Supermicro X10 xeon-d board, which had the SM "cycling" thing going at default... Switched a few things around in the IPMI settings, and the board will now boot with fans at a reasonable speed, which'll ramp up to full-on after a minute or so, so I'd suspect only once Unraid loads... I mean, it's not throwing errors or anything, it's mostly that it probably makes the box noiser than it could or should be... (I've tried putting the upper thresholds to proper variants of the manufacturer's max speeds, didn't change a thing, and also tried adding the Dynamix temp/autofan plugins on top, no luck with that, can't detect the PWM controller or any other temp sensor than the CPU's coretemp) Any clue as to what I'm doing wrong ? Section 607_FAN1 ## this is the silent wings case fan ## 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_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_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 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 1600.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 1700.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 1800.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 674_FAN2 ## this is a noctua 92mm ## 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_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_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 400.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 2100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 2400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 22000.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 741_FAN3 ## this is a noctua F12 ## 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_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_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 400.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 2100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 2400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 22000.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 808_FAN4 EndSection Section 875_FANA ## this is a noctua 92mm ## 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_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_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 400.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 2100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 2400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 22000.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection You need to go into the IPMI webgui and change you fan setting to optimal. By default it set at full. You could also download the ipmiview app from SuperMicro and set it there. I'm not sure if the x8/9 raw commands work for x10. On X10 it should be possible to set fans to a specific duty cycle. There should be some info on the SuperMicro fan about it. Quote Link to comment
mattbr Posted August 30, 2016 Share Posted August 30, 2016 I don't think you're doing anything wrong. That seems to be the way the Supermicro boards work. There's only a low, medium and high speed. If you look earlier in the thread there are some ipmi-raw commands. But if you set it to medium you might have overhating issues. The ipmi settings and thresholds only affect warnings mainly. Changing them won't change how the fans operate. It‘s useful to eliminate any low rpm warnings. And useful to stop the SM boards from the annoying cycling thing, too I'd tried the raw commands, they seemed to go through but don't seem to have any effect. You need to go into the IPMI webgui and change you fan setting to optimal. By default it set at full. You could also download the ipmiview app from SuperMicro and set it there. I'm not sure if the x8/9 raw commands work for x10. On X10 it should be possible to set fans to a specific duty cycle. There should be some info on the SuperMicro fan about it. Thanks for the pointer - forgot to mention I'd already set the IPMI to optimal. Best I can see is an error during boot with ipmifan saying the motherboard isn't supported yet... Quote Link to comment
saarg Posted August 30, 2016 Share Posted August 30, 2016 I don't think you're doing anything wrong. That seems to be the way the Supermicro boards work. There's only a low, medium and high speed. If you look earlier in the thread there are some ipmi-raw commands. But if you set it to medium you might have overhating issues. The ipmi settings and thresholds only affect warnings mainly. Changing them won't change how the fans operate. It‘s useful to eliminate any low rpm warnings. And useful to stop the SM boards from the annoying cycling thing, too I'd tried the raw commands, they seemed to go through but don't seem to have any effect. You need to go into the IPMI webgui and change you fan setting to optimal. By default it set at full. You could also download the ipmiview app from SuperMicro and set it there. I'm not sure if the x8/9 raw commands work for x10. On X10 it should be possible to set fans to a specific duty cycle. There should be some info on the SuperMicro fan about it. Thanks for the pointer - forgot to mention I'd already set the IPMI to optimal. Best I can see is an error during boot with ipmifan saying the motherboard isn't supported yet... Just remembered what the problem is. You didn't set the lower threshold for the fans low enough, and therefore the fans starts running at full speed. Don't know if you can edit the comfig file using this plugin or if you have to use the ipmi raw command to change it. The raw commands might be somewhere in this thread or the cheap Xeon 2670 thread.... The plugin says motherboard not supported as dmacias is too lazy to support any other boards than a few asrock boards Quote Link to comment
mattbr Posted August 30, 2016 Share Posted August 30, 2016 Just remembered what the problem is. You didn't set the lower threshold for the fans low enough, and therefore the fans starts running at full speed. Don't know if you can edit the comfig file using this plugin or if you have to use the ipmi raw command to change it. The raw commands might be somewhere in this thread or the cheap Xeon 2670 thread.... The plugin says motherboard not supported as dmacias is too lazy to support any other boards than a few asrock boards Also, there's this cute little kink with the SM BMC where you need to physically unplug the device to make it reset and actually apply the cooling profile... lowering the thresholds fixed the rest of it, thanks a lot for the hint !!! (while I'm at it - I'd also corrected the temp thresholds for the M.2, since they're significantly higher than what you'd have for those spinny 60's things we still have to live with for the time being... not sure it had any effect other than no more blinky gifs, which is something) Quote Link to comment
ljm42 Posted September 20, 2016 Share Posted September 20, 2016 Hey dmacias, I have the 2016.09.16 version of IPMI support on unRAID 6.2 final. When I boot my system I get these error messages in the console: ipmifan[4092]: Your motherboard is not supported yet ipmifan[4099]: Your motherboard is not supported yet Is there any way to disable these error messages on the console? Since I have fan control disabled I don't really care that it isn't supported. BTW, the web interface to fan control sure makes it look like my board is supported. It enumerates my fans and provides settings for all of them, and it looks like I could enable Fan Control if I wanted to. I have an ASRock E3C226D2I I posted a recent diagnostics here if you need one: https://lime-technology.com/forum/index.php?topic=52052.msg499727#msg499727 Quote Link to comment
dmacias Posted September 20, 2016 Author Share Posted September 20, 2016 Hey dmacias, I have the 2016.09.16 version of IPMI support on unRAID 6.2 final. When I boot my system I get these error messages in the console: ipmifan[4092]: Your motherboard is not supported yet ipmifan[4099]: Your motherboard is not supported yet Is there any way to disable these error messages on the console? Since I have fan control disabled I don't really care that it isn't supported. BTW, the web interface to fan control sure makes it look like my board is supported. It enumerates my fans and provides settings for all of them, and it looks like I could enable Fan Control if I wanted to. I have an ASRock E3C226D2I I posted a recent diagnostics here if you need one: https://lime-technology.com/forum/index.php?topic=52052.msg499727#msg499727 It just shows that because your fan cfg was missing the board variable. I fixed it. It'll just show that fan control is disabled once in the log now. Your board should be supported. Quote Link to comment
ljm42 Posted September 21, 2016 Share Posted September 21, 2016 It just shows that because your fan cfg was missing the board variable. I fixed it. It'll just show that fan control is disabled once in the log now. Your board should be supported. Thanks dmacias! No more error messages on bootup Quote Link to comment
vandammages Posted September 21, 2016 Share Posted September 21, 2016 This is a great plugin.. thanks so much. how do i get IPMI sensor to pass trough from ESXI6.0u2 to unraid 6.2 as guest VM MOBO = Supermicro Motherboard MBD-X9SCM-F-O suggestions or links Regards. Quote Link to comment
dmacias Posted September 21, 2016 Author Share Posted September 21, 2016 This is a great plugin.. thanks so much. how do i get IPMI sensor to pass trough from ESXI6.0u2 to unraid 6.2 as guest VM MOBO = Supermicro Motherboard MBD-X9SCM-F-O suggestions or links Regards. Just use the network option and point it to the ip of your ipmi. Quote Link to comment
mavermc Posted September 21, 2016 Share Posted September 21, 2016 I'm a bit confused, I've been trying to do this myself for the past few days but it's getting frustrating. I have asrock rack E3C224D4I-14S with a E3-1241 v3 When I turn on the fan controller, I can tell its working because my fans spin slower. that being said no matter what I set the min speed to, what temps I set it too. It doesn't react. It just holds the rpms it falls down too when it's enabled. So I think there's a underlying control problem. When I try to use ipmi-raw to trigger full and auto, This always comes back. rcvd: 01 C7 I have no idea what that means and searching the forum and I found one other person with a "OEM -Unknown Response" error, which didn't seem to be the issue, the issue was he had 3pin fans. I know I have 4 pin PWM fans (I installed them myself) and they react and work as they should through the bios. Going through and trying to change the speeds on them seems to do nothing at all. So I'm lost, is my mobo just not compatible? I imagine it's the same ipmi as the rest of the asrockrack. And the ipmi-fru kicks back ASRockRack like it's properly detected. I just can't seem to get them to do anything once I enable the controller. Edit: turns out I needed to add more spots to my commands, I was using ipmi-raw 00 3a 01 64 64 64 64 64 64 --debug using this worked ipmi-raw 00 3a 01 64 64 64 64 64 64 64 64 --debug going to do some more testing and see auto is working as it's supposed too. Edit 2: so while I can now at least manually choose the speed of the fans (which is nice to not have to boot into the bios) the auto setting doesn't seem to work for HDD, I set my low and high in the gui to 30 - 50, Yet the HDD are reading at 47C and my 5000rpm fans are only doing 1500. For now I manually set them to half speed, so my hard drives don't burn up, but I'm guessing there is something amiss with the auto, I know it uses ipmi as the fan controller, In the bios I have them all set to smart fan with the default temp > fanspeed setup. Is there something else I should do in the bios? thanks! Quote Link to comment
dmacias Posted September 21, 2016 Author Share Posted September 21, 2016 I'm a bit confused, I've been trying to do this myself for the past few days but it's getting frustrating. I have asrock rack E3C224D4I-14S with a E3-1241 v3 When I turn on the fan controller, I can tell its working because my fans spin slower. that being said no matter what I set the min speed to, what temps I set it too. It doesn't react. It just holds the rpms it falls down too when it's enabled. So I think there's a underlying control problem. When I try to use ipmi-raw to trigger full and auto, This always comes back. rcvd: 01 C7 I have no idea what that means and searching the forum and I found one other person with a "OEM -Unknown Response" error, which didn't seem to be the issue, the issue was he had 3pin fans. I know I have 4 pin PWM fans (I installed them myself) and they react and work as they should through the bios. Going through and trying to change the speeds on them seems to do nothing at all. So I'm lost, is my mobo just not compatible? I imagine it's the same ipmi as the rest of the asrockrack. And the ipmi-fru kicks back ASRockRack like it's properly detected. I just can't seem to get them to do anything once I enable the controller. Edit: turns out I needed to add more spots to my commands, I was using ipmi-raw 00 3a 01 64 64 64 64 64 64 --debug using this worked ipmi-raw 00 3a 01 64 64 64 64 64 64 64 64 --debug going to do some more testing and see auto is working as it's supposed too. What are your fan names? The script is dependent on the fan names and how they correspond to the raw command. Also what are your low and high temp setting for the fans. rcvd: 01 C7 means the command was received ok. I get the same. And yes there needs to be 8 spots in the raw command. If your testing let me know what the fan names are and what spot they are in. Quote Link to comment
mavermc Posted September 21, 2016 Share Posted September 21, 2016 Edit 2: so while I can now at least manually choose the speed of the fans (which is nice to not have to boot into the bios) the auto setting doesn't seem to work for HDD, I set my low and high in the gui to 30 - 50, Yet the HDD are reading at 47C and my 5000rpm fans are only doing 1500. For now I manually set them to half speed, so my hard drives don't burn up, but I'm guessing there is something amiss with the auto, I know it uses ipmi as the fan controller, In the bios I have them all set to smart fan with the default temp > fanspeed setup. Is there something else I should do in the bios? thanks! I see this in the log: 2016-09-21 04:08:38 Starting Fan Control 2016-09-21 04:08:40 CPU_FAN1(48%):CPU Temperature(54°C), FRNT_FAN1(85%):HDD Temperature(47°C), FRNT_FAN2(85%):HDD Temperature(47°C) 2016-09-21 04:09:42 CPU_FAN1(22%):CPU Temperature(41°C), FRNT_FAN1(85%):HDD Temperature(47°C), FRNT_FAN2(85%):HDD Temperature(47°C) 2016-09-21 04:11:57 CPU_FAN1(36%):CPU Temperature(48°C), FRNT_FAN1(90%):HDD Temperature(48°C), FRNT_FAN2(90%):HDD Temperature(48°C) 2016-09-21 04:13:00 CPU_FAN1(20%):CPU Temperature(40°C), FRNT_FAN1(90%):HDD Temperature(48°C), FRNT_FAN2(90%):HDD Temperature(48°C) 2016-09-21 04:15:04 CPU_FAN1(16%):CPU Temperature(38°C), FRNT_FAN1(95%):HDD Temperature(49°C), FRNT_FAN2(95%):HDD Temperature(49°C) 2016-09-21 04:19:13 CPU_FAN1(18%):CPU Temperature(39°C), FRNT_FAN1(100%):HDD Temperature(50°C), FRNT_FAN2(100%):HDD Temperature(50°C) but my fan speed is stuck at 1500 Fan.cfg FANCONTROL="enable" FANPOLL="1" FANIP="" IPMIBOARD="" BOARD="ASRockRack" FAN_CPU_FAN1="13" TEMP_CPU_FAN1="21" TEMPLO_CPU_FAN1="30" TEMPHI_CPU_FAN1="80" FANMIN_CPU_FAN1="1" FAN_FRNT_FAN1="14" TEMP_FRNT_FAN1="99" TEMPLO_FRNT_FAN1="30" TEMPHI_FRNT_FAN1="50" FANMIN_FRNT_FAN1="1" FAN_FRNT_FAN2="15" TEMP_FRNT_FAN2="99" TEMPLO_FRNT_FAN2="30" TEMPHI_FRNT_FAN2="50" FANMIN_FRNT_FAN2="1" FAN_FRNT_FAN3="16" TEMP_FRNT_FAN3="0" FAN_FRNT_FAN4="17" TEMP_FRNT_FAN4="0" FAN_FRNT_FAN5="18" TEMP_FRNT_FAN5="0" boards.json { "ASRockRack": { "raw": "00 3a 01", "auto":"00 00 00 00 00 00 00 00", "full":"64 64 64 64 64 64 64 64", "fans": { "CPU_FAN1": "00", "CPU_FAN2": "00", "REAR_FAN1": "00", "REAR_FAN2": "00", "FRNT_FAN1": "00", "FRNT_FAN2": "00", "FRNT_FAN3": "00", "FRNT_FAN4": "00" } }, "ASRock": { "raw":"00 3a 01", "auto":"00 00 00 00 00 00 00 00", "full":"64 64 64 64 64 64 64 64", "fans": { "CPU_FAN1": "00", "CPU_FAN2": "00", "REAR_FAN1": "00", "REAR_FAN2": "00", "FRNT_FAN1": "00", "FRNT_FAN2": "00", "FRNT_FAN3": "00", "FRNT_FAN4": "00" } } } I'm only using Fan1 and 2, And they properly report the RPMs (I can hear them go up and down when I manually trigger it) Quote Link to comment
dmacias Posted September 21, 2016 Author Share Posted September 21, 2016 Edit 2: so while I can now at least manually choose the speed of the fans (which is nice to not have to boot into the bios) the auto setting doesn't seem to work for HDD, I set my low and high in the gui to 30 - 50, Yet the HDD are reading at 47C and my 5000rpm fans are only doing 1500. For now I manually set them to half speed, so my hard drives don't burn up, but I'm guessing there is something amiss with the auto, I know it uses ipmi as the fan controller, In the bios I have them all set to smart fan with the default temp > fanspeed setup. Is there something else I should do in the bios? thanks! I see this in the log: 2016-09-21 04:08:38 Starting Fan Control 2016-09-21 04:08:40 CPU_FAN1(48%):CPU Temperature(54°C), FRNT_FAN1(85%):HDD Temperature(47°C), FRNT_FAN2(85%):HDD Temperature(47°C) 2016-09-21 04:09:42 CPU_FAN1(22%):CPU Temperature(41°C), FRNT_FAN1(85%):HDD Temperature(47°C), FRNT_FAN2(85%):HDD Temperature(47°C) 2016-09-21 04:11:57 CPU_FAN1(36%):CPU Temperature(48°C), FRNT_FAN1(90%):HDD Temperature(48°C), FRNT_FAN2(90%):HDD Temperature(48°C) 2016-09-21 04:13:00 CPU_FAN1(20%):CPU Temperature(40°C), FRNT_FAN1(90%):HDD Temperature(48°C), FRNT_FAN2(90%):HDD Temperature(48°C) 2016-09-21 04:15:04 CPU_FAN1(16%):CPU Temperature(38°C), FRNT_FAN1(95%):HDD Temperature(49°C), FRNT_FAN2(95%):HDD Temperature(49°C) 2016-09-21 04:19:13 CPU_FAN1(18%):CPU Temperature(39°C), FRNT_FAN1(100%):HDD Temperature(50°C), FRNT_FAN2(100%):HDD Temperature(50°C) but my fan speed is stuck at 1500 Fan.cfg FANCONTROL="enable" FANPOLL="1" FANIP="" IPMIBOARD="" BOARD="ASRockRack" FAN_CPU_FAN1="13" TEMP_CPU_FAN1="21" TEMPLO_CPU_FAN1="30" TEMPHI_CPU_FAN1="80" FANMIN_CPU_FAN1="1" FAN_FRNT_FAN1="14" TEMP_FRNT_FAN1="99" TEMPLO_FRNT_FAN1="30" TEMPHI_FRNT_FAN1="50" FANMIN_FRNT_FAN1="1" FAN_FRNT_FAN2="15" TEMP_FRNT_FAN2="99" TEMPLO_FRNT_FAN2="30" TEMPHI_FRNT_FAN2="50" FANMIN_FRNT_FAN2="1" FAN_FRNT_FAN3="16" TEMP_FRNT_FAN3="0" FAN_FRNT_FAN4="17" TEMP_FRNT_FAN4="0" FAN_FRNT_FAN5="18" TEMP_FRNT_FAN5="0" boards.json { "ASRockRack": { "raw": "00 3a 01", "auto":"00 00 00 00 00 00 00 00", "full":"64 64 64 64 64 64 64 64", "fans": { "CPU_FAN1": "00", "CPU_FAN2": "00", "REAR_FAN1": "00", "REAR_FAN2": "00", "FRNT_FAN1": "00", "FRNT_FAN2": "00", "FRNT_FAN3": "00", "FRNT_FAN4": "00" } }, "ASRock": { "raw":"00 3a 01", "auto":"00 00 00 00 00 00 00 00", "full":"64 64 64 64 64 64 64 64", "fans": { "CPU_FAN1": "00", "CPU_FAN2": "00", "REAR_FAN1": "00", "REAR_FAN2": "00", "FRNT_FAN1": "00", "FRNT_FAN2": "00", "FRNT_FAN3": "00", "FRNT_FAN4": "00" } } } I'm only using Fan1 and 2, And they properly report the RPMs (I can hear them go up and down when I manually trigger it) Check that spot 5 & 6 correspond to front fan 1 & 2. I don't think they do since your fans are labeled 1 - 5. You'll need to change the names in the boards.json to match (just for ASRockRack) and make sure the order is right too. You can test with the raw command by running ipmi-sensors first (to get get fan names and rpms first) then change just one 64 to 32. You can skip the first since it's probably the cpu. Then run ipmi-sensors to see which fan changed. I'm working on a script that should automate this and write the boards.json with the correct values. Quote Link to comment
mavermc Posted September 21, 2016 Share Posted September 21, 2016 seemed like everything is properly named, the right headers correspond to the right fan labeling. After a reboot it seems the fan are spinning up and down like they should, I'm guessing it was a combination of setting the fans to auto smart in the bios and setting got it to work. Thanks for the help! -Edit: Actually it could be an issue with having to restart to get the settings to work. I saw it working last night (it bounce around from 1500 to 3800 while the drivers were doing things) but this morning I tried changing the high and low temps for the fans and now it just sits at 2800 even though the log says this 2016-09-21 01:42:47 CPU_FAN1(100%):CPU Temperature(49°C), FRNT_FAN1(75%):HDD Temperature(45°C), FRNT_FAN2(75%):HDD Temperature(45°C) 2016-09-21 01:48:04 CPU_FAN1(100%):CPU Temperature(49°C), FRNT_FAN1(80%):HDD Temperature(46°C), FRNT_FAN2(80%):HDD Temperature(46°C) 2016-09-21 01:51:13 CPU_FAN1(100%):CPU Temperature(49°C), FRNT_FAN1(85%):HDD Temperature(47°C), FRNT_FAN2(85%):HDD Temperature(47°C) 2016-09-21 01:53:50 fan control config file updated, reloading settings. 2016-09-21 01:53:54 CPU_FAN1(100%):CPU Temperature(50°C), FRNT_FAN1(100%):HDD Temperature(47°C), FRNT_FAN2(100%):HDD Temperature(47°C) 2016-09-21 02:14:47 fan control config file updated, reloading settings. 2016-09-21 02:15:19 fan control config file updated, reloading settings. 2016-09-21 02:15:22 CPU_FAN1(100%):CPU Temperature(49°C), FRNT_FAN1(96%):HDD Temperature(49°C), FRNT_FAN2(96%):HDD Temperature(49°C) And sometimes it bounces down to 1500 even though the log says 100% So I went ahead an did a ipmi-raw 00 3a 01 64 64 64 64 64 64 64 64 Just to keep the drives from burning up (they were getting back up to 50C) and I'll try setting it up auto the way I think it should work and reboot and see if it then the fans will act normal again. Edit 2: Just noticed that mins after I set it to full speed, the fans went back down to 1500, I set it to full again and they went back up, I'm confused as what could be kicking the fans back down, could it be ipmi and the bios? or is the ipmi plugin going back to auto even after I did a ipmi raw command? Quote Link to comment
dmacias Posted September 21, 2016 Author Share Posted September 21, 2016 seemed like everything is properly named, the right headers correspond to the right fan labeling. After a reboot it seems the fan are spinning up and down like they should, I'm guessing it was a combination of setting the fans to auto smart in the bios and setting got it to work. Thanks for the help! -Edit: Actually it could be an issue with having to restart to get the settings to work. I saw it working last night (it bounce around from 1500 to 3800 while the drivers were doing things) but this morning I tried changing the high and low temps for the fans and now it just sits at 2800 even though the log says this 2016-09-21 01:42:47 CPU_FAN1(100%):CPU Temperature(49°C), FRNT_FAN1(75%):HDD Temperature(45°C), FRNT_FAN2(75%):HDD Temperature(45°C) 2016-09-21 01:48:04 CPU_FAN1(100%):CPU Temperature(49°C), FRNT_FAN1(80%):HDD Temperature(46°C), FRNT_FAN2(80%):HDD Temperature(46°C) 2016-09-21 01:51:13 CPU_FAN1(100%):CPU Temperature(49°C), FRNT_FAN1(85%):HDD Temperature(47°C), FRNT_FAN2(85%):HDD Temperature(47°C) 2016-09-21 01:53:50 fan control config file updated, reloading settings. 2016-09-21 01:53:54 CPU_FAN1(100%):CPU Temperature(50°C), FRNT_FAN1(100%):HDD Temperature(47°C), FRNT_FAN2(100%):HDD Temperature(47°C) 2016-09-21 02:14:47 fan control config file updated, reloading settings. 2016-09-21 02:15:19 fan control config file updated, reloading settings. 2016-09-21 02:15:22 CPU_FAN1(100%):CPU Temperature(49°C), FRNT_FAN1(96%):HDD Temperature(49°C), FRNT_FAN2(96%):HDD Temperature(49°C) And sometimes it bounces down to 1500 even though the log says 100% So I went ahead an did a ipmi-raw 00 3a 01 64 64 64 64 64 64 64 64 Just to keep the drives from burning up (they were getting back up to 50C) and I'll try setting it up auto the way I think it should work and reboot and see if it then the fans will act normal again. Edit 2: Just noticed that mins after I set it to full speed, the fans went back down to 1500, I set it to full again and they went back up, I'm confused as what could be kicking the fans back down, could it be ipmi and the bios? or is the ipmi plugin going back to auto even after I did a ipmi raw command? If you run the raw command it will stay till you reboot. If the fan control is run or running it will change it. You still need to figure out the sequence of your fans and change the names in the boards.json to match. Run something like this ipmi-sensors ipmi-raw 00 3a 01 64 32 64 64 64 64 64 64 ipmi-sensors ipmi-raw 00 3a 01 64 64 32 64 64 64 64 64 ipmi-sensors ipmi-raw 00 3a 01 64 64 64 32 64 64 64 64 ipmi-sensors ... And so on. Taking note of the fan name and the spot whose rpm lowered in half. Then change the boards.json to something like this { "ASRockRack": { "raw": "00 3a 01", "auto":"00 00 00 00 00 00 00 00", "full":"64 64 64 64 64 64 64 64", "fans": { "CPU_FAN1": "00", "FRNT_FAN1": "00", "FRNT_FAN2": "00", "FRNT_FAN3": "00", "FRNT_FAN4": "00", "FRNT_FAN5": "00", "FRNT_FAN6": "00", "FRNT_FAN7": "00" } }, "ASRock": { "raw":"00 3a 01", "auto":"00 00 00 00 00 00 00 00", "full":"64 64 64 64 64 64 64 64", "fans": { "CPU_FAN1": "00", "CPU_FAN2": "00", "REAR_FAN1": "00", "REAR_FAN2": "00", "FRNT_FAN1": "00", "FRNT_FAN2": "00", "FRNT_FAN3": "00", "FRNT_FAN4": "00" } } } Also this will set the fans back to auto/smart fan ipmi-raw 00 3a 01 00 00 00 00 00 00 00 00 Quote Link to comment
mavermc Posted September 21, 2016 Share Posted September 21, 2016 I got all the fans working properly, they all respond to the right headers and have the right names, it's all labeled properly and working properly. That being said I can't explain why when I run a full 64 64 type command, sometimes they spin back down to slow after a little while. Or the auto won't bring them up to full speed when the hdd temps are reaching the top temp in the auto fan settings. I'll try a reboot after this transfer and see if that clears any of this up. Quote Link to comment
vandammages Posted September 21, 2016 Share Posted September 21, 2016 This is a great plugin.. thanks so much. how do i get IPMI sensor to pass trough from ESXI6.0u2 to unraid 6.2 as guest VM MOBO = Supermicro Motherboard MBD-X9SCM-F-O perfect that worked. suggestions or links Regards. Just use the network option and point it to the ip of your ipmi. Quote Link to comment
mavermc Posted September 22, 2016 Share Posted September 22, 2016 I feel like an idiot, I realized when I thought auto fan was working, it was actually off, and the only reason the fans spun up and down was due to the MB temps going up and down. So I guess I'm back where I started. When auto fan is on the log looks like this: 2016-09-21 06:11:14 fan control config file updated, reloading settings. 2016-09-21 06:11:16 CPU_FAN1(100%):CPU Temperature(41°C), FRNT_FAN1(88%):HDD Temperature(47°C), FRNT_FAN2(88%):HDD Temperature(47°C) and the fans sit at 1500 Then my HDD started to overheat again 50C so Then I ipmi-raw 00 3a 01 64 64 64 64 64 64 64 64 Which worked for a total of 30 seconds till they spun back down on their own to 1500rpm. So I did the command again, after 30 seconds they went back down to 1500rpm I figure at this point something is overriding the ipmi plugin, so I turn off ipmi fan control in your plugin. And the fans have stayed at full speed since then. Is it possible the ipmi plugin is overridding it's self? You said that if I did a command like 64 that it should be set that way until I set them back to 00 (auto), but this isn't the case, something is overridding my ipmi raw commands, and when I turn off fan control then my ipmi-raw commands stick until I change them. Quote Link to comment
dmacias Posted September 22, 2016 Author Share Posted September 22, 2016 I feel like an idiot, I realized when I thought auto fan was working, it was actually off, and the only reason the fans spun up and down was due to the MB temps going up and down. So I guess I'm back where I started. When auto fan is on the log looks like this: 2016-09-21 06:11:14 fan control config file updated, reloading settings. 2016-09-21 06:11:16 CPU_FAN1(100%):CPU Temperature(41°C), FRNT_FAN1(88%):HDD Temperature(47°C), FRNT_FAN2(88%):HDD Temperature(47°C) and the fans sit at 1500 Then my HDD started to overheat again 50C so Then I ipmi-raw 00 3a 01 64 64 64 64 64 64 64 64 Which worked for a total of 30 seconds till they spun back down on their own to 1500rpm. So I did the command again, after 30 seconds they went back down to 1500rpm I figure at this point something is overriding the ipmi plugin, so I turn off ipmi fan control in your plugin. And the fans have stayed at full speed since then. Is it possible the ipmi plugin is overridding it's self? You said that if I did a command like 64 that it should be set that way until I set them back to 00 (auto), but this isn't the case, something is overridding my ipmi raw commands, and when I turn off fan control then my ipmi-raw commands stick until I change them. When the ipmifan script runs it sets all other fans to 00 which is auto. With the default boards.json and the way your fans are named the command that is executed looks like this ipmi-raw 00 3a 01 00 00 00 00 XX XX 00 00 where XX (a number between 1 and 64 based on temp and hi/low threshold) is the spot in the raw command that corresponds to FRNT_FAN1 and FRNT_FAN2 in the original boards.json. But even if you changed the boards.json like my previous example, the position of FRNT_FAN1 and FRNT_FAN2 may not correspond to the correct position in the raw command so ipmi-raw 00 3a 01 00 XX XX 00 00 00 00 00 may not be the spots that control FRNT_FAN1 and FRNT_FAN2. That's why you need to figure out which spot controls which fan by running ipmi-sensors followed by a raw command with 32 only in one spot and 64 in the rest of the spots then ipmi-sensors again to see which fan changed rpms. I hope that all makes sense. Quote Link to comment
mavermc Posted September 22, 2016 Share Posted September 22, 2016 I think I'm starting to grasp it, thanks for staying with me. Yes when I do ipmi-raw 00 3a 01 00 64 64 64 64 64 64 64 The CPU fan goes auto, and works properly (no problems there) when I do ipmi-raw 00 3a 01 00 35 64 64 64 64 64 64 Fan1 drops from 4200 rpm to 2100 rpm and when I do ipmi-raw 00 3a 01 00 64 35 64 64 64 64 64 Fan2 drops from 4200 rpm to 2100 rpm So those are the correct spots as far as I can tell. and according to ipmi-sensors that's the name of those spots 13 | CPU_FAN1 | Fan | 1900.00 | RPM | 'OK' 14 | FRNT_FAN1 | Fan | 3100.00 | RPM | 'OK' 15 | FRNT_FAN2 | Fan | 3100.00 | RPM | 'OK' 16 | FRNT_FAN3 | Fan | N/A | RPM | N/A 17 | FRNT_FAN4 | Fan | N/A | RPM | N/A 18 | FRNT_FAN5 | Fan | N/A | RPM | N/A So all that seems to line up and work properly, could it be that FRNT_FAN1 is not the same one as FRNT_FAN1 (4200 RPM): in the ipmi fan controller page? Just to try that theory I set all the Fans (expect CPU) to HDD with 50 being high, but again when I set to auto the HDD are at 50C but the fans spin at 1500. Specifcly the started at 3100 for 30 seconds, then went to 2200 for 30 seconds, then finally went to 1500 and haven't budge even though the HDD are very hot. Yet the log seems to see that and have all the fans set to high. 2016-09-21 11:38:26 CPU_FAN1(100%):CPU Temperature(65°C), FRNT_FAN1(96%):HDD Temperature(49°C), FRNT_FAN2(96%):HDD Temperature(49°C), FRNT_FAN3(96%):HDD Temperature(49°C), FRNT_FAN4(96%):HDD Temperature(49°C) so what does that mean? Quote Link to comment
dmacias Posted September 22, 2016 Author Share Posted September 22, 2016 I think I'm starting to grasp it, thanks for staying with me. Yes when I do ipmi-raw 00 3a 01 00 64 64 64 64 64 64 64 The CPU fan goes auto, and works properly (no problems there) when I do ipmi-raw 00 3a 01 00 35 64 64 64 64 64 64 Fan1 drops from 4200 rpm to 2100 rpm and when I do ipmi-raw 00 3a 01 00 64 35 64 64 64 64 64 Fan2 drops from 4200 rpm to 2100 rpm So those are the correct spots as far as I can tell. and according to ipmi-sensors that's the name of those spots 13 | CPU_FAN1 | Fan | 1900.00 | RPM | 'OK' 14 | FRNT_FAN1 | Fan | 3100.00 | RPM | 'OK' 15 | FRNT_FAN2 | Fan | 3100.00 | RPM | 'OK' 16 | FRNT_FAN3 | Fan | N/A | RPM | N/A 17 | FRNT_FAN4 | Fan | N/A | RPM | N/A 18 | FRNT_FAN5 | Fan | N/A | RPM | N/A So all that seems to line up and work properly, could it be that FRNT_FAN1 is not the same one as FRNT_FAN1 (4200 RPM): in the ipmi fan controller page? Just to try that theory I set all the Fans (expect CPU) to HDD with 50 being high, but again when I set to auto the HDD are at 50C but the fans spin at 1500. Specifcly the started at 3100 for 30 seconds, then went to 2200 for 30 seconds, then finally went to 1500 and haven't budge even though the HDD are very hot. Yet the log seems to see that and have all the fans set to high. 2016-09-21 11:38:26 CPU_FAN1(100%):CPU Temperature(65°C), FRNT_FAN1(96%):HDD Temperature(49°C), FRNT_FAN2(96%):HDD Temperature(49°C), FRNT_FAN3(96%):HDD Temperature(49°C), FRNT_FAN4(96%):HDD Temperature(49°C) so what does that mean? You just need to edit the boards.json on your flash drive @ /boot/config/plugins/ipmi and restart the fan control service. { "ASRockRack": { "raw": "00 3a 01", "auto":"00 00 00 00 00 00 00 00", "full":"64 64 64 64 64 64 64 64", "fans": { "CPU_FAN1": "00", "FRNT_FAN1": "00", "FRNT_FAN2": "00", "FRNT_FAN3": "00", "FRNT_FAN4": "00", "FRNT_FAN5": "00", "FRNT_FAN6": "00", "FRNT_FAN7": "00" } }, "ASRock": { "raw":"00 3a 01", "auto":"00 00 00 00 00 00 00 00", "full":"64 64 64 64 64 64 64 64", "fans": { "CPU_FAN1": "00", "FRNT_FAN1": "00", "FRNT_FAN2": "00", "FRNT_FAN3": "00", "FRNT_FAN4": "00", "FRNT_FAN5": "00", "FRNT_FAN6": "00", "FRNT_FAN7": "00" } } } The ipmifan script relies on the fans being properly named and in the correct order so it can create the raw command. Fan3 and fan4 don't exist in the default boards.json and fan1 and fan2 are in spots 5 and 6 so the script won't work. I'm working on a solution to automate the creation of the boards.json Quote Link to comment
Recommended Posts
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.