dmacias

Sorry I'm not sure. You'll have to look up your specific UPS model and nut compatibility

Yes I could add an option to disable system logging.

Thanks for the link I'll check that link out more when I get a chance. Maybe I can use that instead.

I'm not sure. Maybe something else is claiming it first.

You might need this package too kmod-usb-hid and maybe more. I'm not sure as I've only played with openwrt a bit.

The plugin can't update the bmc. You have to go to Supermicro website and get the bmc file for your board then update through the board's ipmi webpage. The bios has to be done with a dos boot disk or pay SM like $20 for a license to do it through the ipmi webpage. The configure button is only for ASRock boards. It's for determining which fan header corresponds to which place in the command for those boards. Single core ASRock boards have just a single command and dual socket boards have 2 commands. But each command is able to set several fans to different levels separately.

Before you do this make sure you have the threshold for FANA set properly. Here's the raw commands you can test. Just stop the fancontrol service first. Run this first to get the readings ipmisensors -t fan Then run this to change the fan setting for FANA to full speed ipmi-raw 00 30 70 66 01 01 64 Run this to get the reading maybe even a couple times to check ipmisensors -t fan Then change the fan speed like this and check the reading again with ipmisensors ipmi-raw 00 30 70 66 01 01 34 Let me know what you find out. You can also use this to check FAN1234 ipmi-raw 00 30 70 66 01 00 64 If none of this works, double check bios and bmc are up to date. Try switching fan headers. Not that it matters but all Supermicro boards I have had say to put CPU on fan1 and FANA is for peripherals. So I always have CPU on fan header 1 and case fans on 2, 3, 4 then 2 fans with a splitter (pwm only goes to one fan) on FANA for my hard drives.

If this error is on your router, it's probably a permissions problem. You could be missing necessary directories too. Just google Nut Can't claim USB device No such file or directory

In the latest version I do set the fan profile to full for Supermicro boards before running the script. This was to avoid any bmc interruption which can happen with the other fan modes.

Yes that's how you stop the service. Also what's the recent fan log say when you ran debug. You might also need to use the sensor config editor and set the thresholds for your fans. I need to make a guide how to do that but there's some info earlier in the thread. FANA worked in the previous release?

Which fan connector is it on 1 2 3 or 4? You can also stop the fancontrol service and run ipmifan --debug from the console. It will log more info in the fan log and display lots of info in the terminal. Also is the bios and bmc updated.

Try applying all settings again and stopping and starting the fancontrol service. I had a similar experience but I gave it a minute and the fan returned to normal control

That is probably out of the scope of this plugin. It would probably require a few more packages also. There is another plugin called devpack that has a lot of the development packages. I just run a virtual machine of unRAID and compile on it.

I'll look at it more tomorrow. It's late and I'm a bit tired to do math ?. I think I see what you want to do. Rescale it and I was just applying the min till it went above. Makes sense. Do you have a github account? You could do a pull request. Replace that line and remove the 2 if statements imposing the limits just below it.

You're welcome. And yes thanks for confirming it's working and thanks to gmk2.

Ok. Done.

I'll look into it more. The decimal places should have no effect as the underlying values for the selections were still 1-64 or 1-255

That's good to hear. What was your interval? If it was 3 or 5 min it might have taken that long to adjust.

You'll have to give me a little more info. I have the exact board and it's working for me. What are your fan settings? What does the ipmifan log say? Clear the log and start and stop the fan control. You can also stop fan control and run ipmifan - - debug and post the ipmifan log.

I have a list of a bunch of Supermicro and ASRock commands. I knew I had those commands but didn't realize the range was 0 - 255 (00-ff). I updated the plugin with changes for X9 boards. If you have any trouble you can run ipmifan --debug from the command line. It will show all the variables on the console and log the command string to the fanlog.

Thank you for this. I had no idea the X9 had this available. Would be nice if others could confirm it works for their X9 boards also. You are correct that the gui %'s are based on 64. So 100% = 64. It may be as simple as converting the resulting PWM value to hexadecimal and setting a upper limit to 255. I can determine the board model automatically. I'll see what I can do.

Sounds like fun. Thanks

Looking at the github for the mosh slackbuild it looks like the mosh 1.3.2 build 6 was a "Massive rebuilt against openssl 1.1.0h" I downgraded mosh to 1.2.4 because all the previous 1.3.2 builds are gone. I'll try and build it myself against openssl 1.01 when I get a chance.

How are you logging into it? Either the unRAID mosh package was built against openssl 1.1 or your client is. If it's unRAID, I can revert to an earlier version or try to compile it myself.

I added protobuf and mosh. You will also need to install perl and utempter.