dmacias

Thanks, it shows up properly in the sensor report now, but still shows N/A in the dashboard.. Updated. Should work for dash and footer. Thanks! It shows up properly in all places now.. Just a small request for your next update, can you remove the ' from the display.. Right now it shows as 'Low' everywhere instead of Low Thanks again! Can you run this command for me and post the output? /usr/sbin/ipmi-sensors --output-sensor-thresholds --comma-separated-output --output-sensor-state --no-header-output --interpret-oem-data

Thanks, it shows up properly in the sensor report now, but still shows N/A in the dashboard.. Updated. Should work for dash and footer. Thanks! It shows up properly in all places now.. Just a small request for your next update, can you remove the ' from the display.. Right now it shows as 'Low' everywhere instead of Low Thanks again! Ok. I'll look into that.

Thanks, it shows up properly in the sensor report now, but still shows N/A in the dashboard.. Updated. Should work for dash and footer.

Thanks, it shows up properly in the sensor report now, but still shows N/A in the dashboard.. Thanks, I forgot about the dashboard. I'll make the same changes to it.

Updated. It should show events as readings for OEM Reserved. The footer will take a bit more work.

Oh ok. So does it show low in the sensor readings page or did you want it for the footer? I already have --interpret-oem-data in the command string so it should show up in readings.

I can do that and included it in the footer too. Can you run ipmi-sensors from the command line and post the output? Do you know what the exact text is? low/medium/high? root@Tower:~# ipmi-sensors ID | Name | Type | Reading | Units | Event 4 | CPU Temp | OEM Reserved | N/A | N/A | 'OEM Event = 0000h' 5 | Sys Temp | Temperature | 34.00 | C | 'OK' 6 | CPU Vcore | Voltage | 1.16 | V | 'OK' 7 | DIMM Volt | Voltage | 1.82 | V | 'OK' 8 | 3.3V | Voltage | 3.30 | V | 'OK' 9 | 5V | Voltage | 4.82 | V | 'OK' 10 | 12V | Voltage | 11.81 | V | 'OK' 11 | -12V | Voltage | -12.10 | V | 'OK' 12 | 5VSB | Voltage | 4.85 | V | 'OK' 13 | VBAT | Voltage | 3.22 | V | 'OK' 14 | Fan1 | Fan | 3000.00 | RPM | 'OK' 15 | Fan2 | Fan | 1000.00 | RPM | 'OK' 16 | Fan3 | Fan | 1000.00 | RPM | 'OK' 17 | Fan4 | Fan | 900.00 | RPM | 'OK' 18 | Fan5 | Fan | 3000.00 | RPM | 'OK' 19 | Fan6/CPU | Fan | 1400.00 | RPM | 'OK' 20 | Intrusion | Physical Security | N/A | N/A | 'OK' 21 | Power Supply | Power Supply | N/A | N/A | 'OK' 22 | Thermal Trip | Module/Board | N/A | N/A | 'OK' 23 | BIOS | System Firmware Progress | N/A | N/A | N/A And yes, it's Low, Medium and High - It was in Low when I got the output above.. cheers! Could you try again with ipmi-sensors --interpret-oem-data And if that didn't work try ipmi-sensors --interpret-oem-data --record-ids=4 Also what board?

I can do that and included it in the footer too. Can you run ipmi-sensors from the command line and post the output? Do you know what the exact text is? low/medium/high?

I get the same results. Like the info in the forms is not getting transferred to the underlying code. Can't change settings. Edit: although it does show the ip when trying to connect manually.

Done. Not the latest without someone compiling it. But added 4.1 to unRAID 6.2 and 3.7 to 6.1

Any other drives in your system besides start drives? The ipmifan script and the sensor page are two separate things. I reuse the dynamix readings for the hard drive temps and take the greatest value. The fan script checks the hard drive temps based on the frequency selected in the settings, using smartctl to get the temps, then uses the highest value also.

You can monitor SuperMicro motherboards and receive alerts through the unRAID notification system but I just haven't had time to implement a solution for fan control. The fan control for SM boards would also be limited to low, medium and high. They don't have the ipmi fan control that Asrock has. However you could possibly use the dynamix plugin to control your fans.

Edit. Ok let me know.

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

I have the same experience using Android ControlIR 2.02 with spinning icon. Cleared cache and data but same spinning icon when trying to connect. The + works fine for me and responds to touch.

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.

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

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.

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.

Just use the network option and point it to the ip of your ipmi.

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.

I added stunnel 5.35.

Thanks, it's a bug in the package manager.

I update sshfs for 6.2

Thanks I'll figure it out. Until then if you turn delete on then deselect screen and utempter and click Apply it will delete them. Then just reselect and apply. Or just delete the utempter package from the flash drive the deselect/select then apply.