dmacias Posted June 9, 2017 Author Share Posted June 9, 2017 (edited) When I got my X10SLL-F board it would boot up and all the lights looked good but no video post. I couldn't connect to ipmi either. I thought the bios might be old and not compatible with my processor. So I was kinda stuck. I had to use wireshark to sniff the ip of the BMC. And found there was a manial ip set. The bios and BMC were latest versions though. It turned out the power supply was bad. But I did factory reset the BIOS and BMC. Here's what my sensors config file looks like Section 540_FAN1 ## 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 700.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 500.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 25300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 25400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 25500.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 607_FAN2 ## 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 700.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 500.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 25300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 25400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 25500.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_FAN3 ## 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 700.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 500.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 25300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 25400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 25500.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_FAN4 EndSection Section 808_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_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 700.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 500.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 25300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 25400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 25500.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 So I'm missing details on fan 4. Originally I had fans connected to FAN1,2,3 and A. I had changed my fan arrangement and moved my CPU fan to FAN4. So FAN3 is empty. So the previous config is from the original fan configuration. I clicked on the REVERT button on the Sensors Config Editor page, which pulls a new config from the BMC. This is what I got. Section 540_FAN1 ## 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 700.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 500.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 25300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 25400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 25500.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 607_FAN2 ## 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 700.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 500.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 25300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 25400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 25500.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_FAN3 EndSection Section 741_FAN4 ## 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 700.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 500.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 25300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 25400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 25500.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_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_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 700.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 500.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 25300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 25400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 25500.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 So there's no config values for missing fans and the config file may be out of sync if changes have been made. Also these are the default values. I haven't changed a thing. Edited June 9, 2017 by dmacias Quote Link to comment
JorgeB Posted June 9, 2017 Share Posted June 9, 2017 I'm not sure what the problem is, but if I do an ipmi-sensors-config --checkout to a file, there's info on all fans. Quote Link to comment
dmacias Posted June 9, 2017 Author Share Posted June 9, 2017 (edited) 23 minutes ago, johnnie.black said: I'm not sure what the problem is, but if I do an ipmi-sensors-config --checkout to a file, there's info on all fans. Did you try clicking Revert to pull a current config from the BMC? I'll have to test what happens if I write the original config now. Edit: The ipmi-sensors.config is a static file. It is only changed if it doesn't exist or Revert is clicked. This is so threshold values can be loaded when unRAID starts for those system that don't save the settings. The config file and the web editor should matchup if reverted. Also, I tried writing my first config above with details for FAN3 but no FAN4. Write was sucessful but pulling a config resulted in the second config with the correct details for FAN4 and no FAN3. So I can't change fans values that aren't connected. Edited June 9, 2017 by dmacias Quote Link to comment
JorgeB Posted June 9, 2017 Share Posted June 9, 2017 25 minutes ago, dmacias said: Did you try clicking Revert to pull a current config from the BMC? I'll have to test what happens if I write the original config now. No, I hadn't, didn't know that was what its function, but tried it now and it worked. Quote Link to comment
jang430 Posted June 10, 2017 Share Posted June 10, 2017 9 hours ago, dmacias said: Sorry, from your previous posts I wasn't sure how you were editing the thresholds. I saw you mention the editor was missing details. Are you using individual commands or the ipmi-sensors-config checkout/commit command? You wouldn't want to enable the "load on unraid start" switch because it would just load the bad/empty config file. Also can you verify that the /config/plugins/ipmi/ipmi-sensors.config file is actually missing the details also? There could be a problem with browser vs editor? I know the editor/codemirror javascript doesn't play well with mobile browsers. It displays fine but editing has problems. Also I know it might be a pain but have you thought about factory resetting the bmc? The ipmi-sensors-config checkout command pulls the info directly from the bmc. Maybe there's some sort of corruption. If the editor and actual ipmi-sensors.config file are missing details this may indicate a problem. This is the content of my ipmi-sensors.config, as checked via ssh to the machine. EndSection Section 138_FAN_1 EndSection Section 205_FAN_2 EndSection Section 272_FAN_3 EndSection Section 339_FAN_4 EndSection Section 406_FAN_A EndSection I will be trying 2 things today. 1 is to reset BMC, 2, to connect all 3 fans to FAN A, and CPU fan to FAN 1. Planning to follow this guide given to me by another person helping from another forum: Connect your CPU and fans on the motherboard side to FAN1 - FAN4 headers on the motherboard. Use a Fan splitter cable to connect all 3 fans marked in Post #4 by @marcoi to connect to FANA header on the motherboard. Reset your BMC to factory defaults. (Maintenance -> Factory Defaults -> Reset) Once the BMC comes back online define the fan thresholds manually with the commands 1 and 2 below. ipmitool sensor thresh FANA lower 200 250 300 ipmitool sensor thresh FANA upper 1300 1400 1500 This should set the thresholds for the 3 Noctuas Restart your BMC (Maintenance -> Unit Reset -> Reset) Set the fan speed to Full It's another hail Mary I'm doing to make sure I get things right. Quote Link to comment
dmacias Posted June 10, 2017 Author Share Posted June 10, 2017 3 minutes ago, jang430 said: This is the content of my ipmi-sensors.config, as checked via ssh to the machine. EndSection Section 138_FAN_1 EndSection Section 205_FAN_2 EndSection Section 272_FAN_3 EndSection Section 339_FAN_4 EndSection Section 406_FAN_A EndSection I will be trying 2 things today. 1 is to reset BMC, 2, to connect all 3 fans to FAN A, and CPU fan to FAN 1. Planning to follow this guide given to me by another person helping from another forum: Connect your CPU and fans on the motherboard side to FAN1 - FAN4 headers on the motherboard. Use a Fan splitter cable to connect all 3 fans marked in Post #4 by @marcoi to connect to FANA header on the motherboard. Reset your BMC to factory defaults. (Maintenance -> Factory Defaults -> Reset) Once the BMC comes back online define the fan thresholds manually with the commands 1 and 2 below. ipmitool sensor thresh FANA lower 200 250 300 ipmitool sensor thresh FANA upper 1300 1400 1500 This should set the thresholds for the 3 Noctuas Restart your BMC (Maintenance -> Unit Reset -> Reset) Set the fan speed to Full It's another hail Mary I'm doing to make sure I get things right. Did you try the Revert button on the Sensors Config Editor page? Quote Link to comment
jang430 Posted June 10, 2017 Share Posted June 10, 2017 @dmacias, I turned it off to be sure. I'll perform all steps above, which also includes resetting BMC. I'll report back. Fingers crossed Quote Link to comment
jang430 Posted June 10, 2017 Share Posted June 10, 2017 Just want to make everything clear :-), the following commands, what I'm doing is open ssh session to my Unraid. I go to /mnt and execute the commands below. 1) download current config to a text file ipmi-sensors-config --checkout --filename=sensordata.conf 2) use an editor like nano to change the values you want nano -w sensordata.conf ctrl+o to save, ctrl+x to exit nano 3) commit the changes ipmi-sensors-config --commit --filename=sensordata.conf I hope all these time, I'm doing it in the right place. Quote Link to comment
jang430 Posted June 10, 2017 Share Posted June 10, 2017 Found out that the fan that is too noisy is in fact another Supermicro provided fan from 1U rackmount case that I use as CPU Fan. The 3 of the other fans are the Noctua. I followed the steps detailed above. Connected CPU Fan (Supermicro) to Fan 1, and Noctua Fans to Fan A. Reset BMC, set threshold. Set fans to full. At Fans set to full, CPU Fan runs at 3300 RPM, and Noctuas run at 1275 (within limit of 1300 RPM). But the Fractal Design Node 804 is poised for TAKE OFF! :-) Despite 1275 RPM at full speed for Noctuas, the HDD temps seem to be at 40 to 41, older models go up to 45. Is this enough? Is there a way to just lower the speed for the CPU fan, and not affect Noctuas' maximum speed at 1275 RPM? Quote Link to comment
JorgeB Posted June 10, 2017 Share Posted June 10, 2017 58 minutes ago, jang430 said: Is there a way to just lower the speed for the CPU fan, and not affect Noctuas' maximum speed at 1275 RPM? If you have all 3 Notcua fans on FANA setting the profile to "Heavy IO" should keep those at or close to maximum speed while keeping the CPU fan at about 50%. Quote Link to comment
jang430 Posted June 10, 2017 Share Posted June 10, 2017 Hi johnnie.black, How are they connected? Did you use the low noise adaptor to limit fan speed? How about the CPU fan connected to Fan1? Doesn't it rev up and down at Heavy IO? Quote Link to comment
JorgeB Posted June 10, 2017 Share Posted June 10, 2017 26 minutes ago, jang430 said: Hi johnnie.black, How are they connected? Did you use the low noise adaptor to limit fan speed? How about the CPU fan connected to Fan1? Doesn't it rev up and down at Heavy IO? ¿qué? I was talking about your fans, not mine. Quote Link to comment
jang430 Posted June 10, 2017 Share Posted June 10, 2017 Sorry, misunderstood. I'm happy to finally report that with your suggestion of getting it to Heavy IO, indeed, CPU fan stayed constant at close to 50%, and Fan A (Noctuas) stayed constant at about 750 RPM. I did have Low Noise Adapters connected though, so It's supposed to run at a lower speed. On top of that, since it's in Heavy IO mode, Fan A speed was further reduced, I think. Thanks for the suggestion. Before that, I had fans set to Standard mode, and was revving up and down. I wouldn't have guessed that heavy IO will make it stable at about 50%. at 750 RPM though, it won't be enough to cool my hard drives. In the end, what cooled my hard drives are the original fans that came with the Fractal case, all 3 of them connected to the HDD side. All those fans have 3 pins, that I connected to the fan switch that came with the case, set to High. That took care of the fans blowing the HDDs. Since I have a dedicated CPU Fan, the motherboard side of the case, with Fan A (Noctuas) blowing at low speed, it doesn't really get hot. What a journey! Thanks to all of you guys! I do hope dmacias finds a way to control fans so that I can utilize my Noctuas properly. Quote Link to comment
dmacias Posted June 18, 2017 Author Share Posted June 18, 2017 If someone with a Supermicro X10 or X11 wants to give it a try here's the latest beta I've been working on. It is fully functional. No bugs or issues that I know of yet other than I'm still working on ASRock dual cpu support and Supermicro X9 support. So fan control will not work for a X9 board yet. This is a new separate repo I split from my unRAID plugins repo and when I feel this is right I'll push an update to the main repo and point it to this one. https://raw.githubusercontent.com/dmacias72/IPMI-unRAID/master/plugin/ipmi.plg 1 Quote Link to comment
wgstarks Posted June 19, 2017 Share Posted June 19, 2017 (edited) 1 hour ago, dmacias said: If someone with a Supermicro X10 or X11 wants to give it a try here's the latest beta I've been working on. It is fully functional. No bugs or issues that I know of yet other than I'm still working on ASRock dual cpu support and Supermicro X9 support. So fan control will not work for a X9 board yet. This is a new separate repo I split from my unRAID plugins repo and when I feel this is right I'll push an update to the main repo and point it to this one. https://raw.githubusercontent.com/dmacias72/IPMI-unRAID/master/plugin/ipmi.plg Decided to give it a test run. Seems ok. When i started fan control it kicked everything to max for about 2 seconds. Generated a couple of overspeed warnings. Then went back to normal. Fan 1,2 & 3 are not connected to PWM fans but fan 4 is. Why don't I get a reading. I can see the speed in the footer and adjusting the minimum speed changes the fan speed. Would also prefer to let the board control FanA (cpu fan). Is that what auto does? Edit: Had to disable (uncheck) Fans 1, 2, 3 in global settings. Now have speed display for Fan4 although the label shows FAN1234. Curious how this is going to work once I install PWM fans on 1, 2, 3. Those fans will be HDD cooling while FAN4 is my rear case fans. Different size and maybe different mfg. Edited June 19, 2017 by wgstarks Quote Link to comment
dmacias Posted June 19, 2017 Author Share Posted June 19, 2017 (edited) 5 hours ago, wgstarks said: Decided to give it a test run. Seems ok. When i started fan control it kicked everything to max for about 2 seconds. Generated a couple of overspeed warnings. Then went back to normal. Fan 1,2 & 3 are not connected to PWM fans but fan 4 is. Why don't I get a reading. I can see the speed in the footer and adjusting the minimum speed changes the fan speed. Would also prefer to let the board control FanA (cpu fan). Is that what auto does? Edit: Had to disable (uncheck) Fans 1, 2, 3 in global settings. Now have speed display for Fan4 although the label shows FAN1234. Curious how this is going to work once I install PWM fans on 1, 2, 3. Those fans will be HDD cooling while FAN4 is my rear case fans. Different size and maybe different mfg. The FAN1234 is just a the group. The fan speed that is shown is only for the first fan available I the group. That's why hiding the other fans shows rpms. It's really just a reference and is never updated unless you refresh the page. I was thinking of just picking the highest or getting rid of it altogether. I need to double check the auto to make sure I'm using the right value. But auto right now sets a value of 01. Edit: 00 or 01 does not equal auto. 00 is auto for ASRock. You also might check your manual but I'm pretty sure FANA is for I/O but not sure what temp sensor it's based on. I believe FANS 1, 2, 3 & 4 group are based on cpu temp. There was some discussion a few pages back. Edited June 19, 2017 by dmacias Quote Link to comment
dmacias Posted June 19, 2017 Author Share Posted June 19, 2017 Also if anyone who tries the beta above wants to go back you can just uninstall it and install the plugin from the OP. Quote Link to comment
wgstarks Posted June 19, 2017 Share Posted June 19, 2017 21 minutes ago, dmacias said: You also might check your manual but I'm pretty sure FANA is for I/O but not sure what temp sensor it's based on. I believe FANS 1, 2, 3 & 4 group are based on cpu temp. There was some discussion a few pages back I believe I'm interpreting this right. 1234 are system A is CPU. Quote Link to comment
dmacias Posted June 19, 2017 Author Share Posted June 19, 2017 (edited) 2 hours ago, wgstarks said: I believe I'm interpreting this right. 1234 are system A is CPU. I'm not sure. I see what you mean but I'm not sure 1-4 = system and A = CPU. I got this from their fact. I know its from a different Motherboard but I have seen similar. Sometimes it seems like there's some conflicting info. Question We have a X9SCL-F and connected Chassis fans to FAN-1/2/3 and CPU fan to fan header "A" on this mainboard. Now we see that the fan spin up/down, or sometimes full speed. What can we do? Answer FANA is for add-on card and controlled by system temperature. FAN1~4 is controlled by CPU temperature. CPU Heatsink fan should not be connected to FAN-A. CPU Heatsink fan can be connected to FAN-1. Chassis fans can be connected to FAN-2~4 or FAN-A. Edited June 19, 2017 by dmacias Quote Link to comment
JorgeB Posted June 19, 2017 Share Posted June 19, 2017 (edited) Usually FANA is for peripherals, but since there's only one of those most people use FANA for the CPU and the other 4 for peripherals, so it would be nice if the script had and option to reverse that so that FANA responded to CPU temp sensor and the other fans to disks temps. Ignore that, I see you can already select the temp you want that fan group to respond to. Edited June 19, 2017 by johnnie.black Quote Link to comment
Diggewuff Posted June 19, 2017 Share Posted June 19, 2017 (edited) Haven't tested te Beta just jet, but totally agree. 3 minutes ago, johnnie.black said: Usually FANA is for peripherals, but since there's only one of those most people use FANA for the CPU and the other 4 for peripherals, so it would be nice if the script had and option to reverse that so that FANA responded to CPU temp sensor and the other fans to disks temps. Edit: Temp sensor for Fan A is located at the lower left Edge of the Mainboard and messures ambient air temp wehre pci-e cards are located. Edited June 19, 2017 by Diggewuff Quote Link to comment
JorgeB Posted June 19, 2017 Share Posted June 19, 2017 1 minute ago, Diggewuff said: Haven't tested te Beta just jet, but totally agree. You can already do that, I edited my post, wrote before seeing how the plugin works. Quote Link to comment
Diggewuff Posted June 19, 2017 Share Posted June 19, 2017 I have examns at University this week. But will definetly test at the weekend. Quote Link to comment
wgstarks Posted June 19, 2017 Share Posted June 19, 2017 I'll have to do some more digging in the user manual for my X10 but I'm fairly sure that FANA is specified for CPU somewhere in there. It's been a few years though so I could be wrong. Regardless, it's CPU now and working from CPU TEMP. Quote Link to comment
dmacias Posted June 19, 2017 Author Share Posted June 19, 2017 I'll have to do some more digging in the user manual for my X10 but I'm fairly sure that FANA is specified for CPU somewhere in there. It's been a few years though so I could be wrong. Regardless, it's CPU now and working from CPU TEMP.I wouldn't worry about it. If it's working fine. My manual looks just like the picture you posted but says nothing else. I was just going off other manuals and the faq. I was just worried it might be running off system temp instead. Anyway I did more testing and research. Setting a value of 00 for the fan isn't Auto. The board just kicks the fan up to full speed when you set it too low. I now have to Auto setting or 00 value do nothing in the script. So it will use whatever Mode you have set in the BMC. I'm using this command to set the fan speeds "ipmi-raw 00 30 70 66 01 00 XX" XX=00-64, 64=100%, 32=50% Also when the fan script is stopped it resets the fans to the mode you selected in the BMC. If the FANA stuff wasn't confusing enough the modes are too.00 is Standard01 is Full02 is Optimal which is lower than Standard04 is between 00 & 01I'm using this command for this."ipmi-raw 00 30 45 01 XX" The one thing I am wondering though is even though the fan script is changing the the fan speeds does the BMC use the Mode to adjust those same fans at some point. 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.