dmacias

The nut driver for your ups doesn't support that. I googled other posts that show the same variables.

I added user input so I could figure the power factor. Correct me if I'm wrong but I was speaking to the Tripp Lite specifically to any UPS that reports ups.power.nominal which is in VA as opposed to the ups.realpower.nominal which is in watts. I would get the load in watts from power nominal x load%/100 x power factor. For UPS with real power nominal the power factor is included already and shown in watts. So all I need is real power nominal x load%/100. For a UPS like mine I can get the power factor with user input of 700W/1200VA. To get the load in watts 1200VA x load%/100 x 700W/1200VA which is basically my 700W capacity x load%/100. I figure ups.load 50 is 50% whether it was from VA or watts. It's what I apply that 50% to that matters. ups.power.nominal is the capacity of 1200VA for my UPS. So I could just use that and ask for user input of watt capacity. But maybe some UPS don't have that variable too.

No I haven't. Been busy with the holidays and after I swapped out my server, I swapped out all my network equipment. I will soon, before I start anything else. I'm not sure how great it will be for the X9 boards though. I can only set the fans between a few settings. The same settings that are in the bmc and just cycle through them based on temp. So basically a low, medium and high setting.

I have a Tripp Lite too. The 2018.01.03 nominal power was in volt amperes and didn't display the correct load. Our UPS don't have the ups.realpower.nominal variable. I need the watt capacity to calculate the power factor to reflect an accurate load in watts. Basically I just need the total watts multiplied by the load percentage. So change the UPS Power and Load display setting at the bottom of the page to manual and enter in your total capacity in VA and Watts. I believe your values should be 1500 for VA and 900 for Watts. Click apply.

Yeah either the nut driver or the ups doesn't present all the values especially load or time left on battery. But it may still work to shutdown the server during power outage.

Ok. I thought you meant nut server/client separation. I get what your saying as most of my other plugins are written this way. This is the way it was written and I don't see any benefit vs time spent to rewrite it. You're more than welcome to refractor the code. I'll merge it. A fall back of VA is not really useful. Nobody knows what 250VA means? User input of the output watt capacity of their ups would be a better method.

That's probably something you'll need to install all the packages yourself. It's probably more than those three also. I would go to pkgs.org and search for those three packages and get the x86-64 versions. Then copy them to your flash drive and installpkg them. Then run ufraw and see if it complains about missing libraries. If missing, then get that package and keep trying till you get all the libraries and it works. There lots of packages that aren't necessary for unRAID missing. That's the reason for trial and error.

Go to Settings/IPMI/Config Editor click on Select Config and pick Sensors. Scroll down to each Section Fan and change the 3 lower threshold values to something like 300. Do this for every Section Fan. Like this. Section 540_FAN1... ## 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 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 300.000000 ...EndSection When done editing click Save. You'll also need to set under Fan Control a Fan speed minimum to a high enough percentage to keep the fans from going below 300 RPMs. I have mine set to 28%.

Did you try using the blazer_usb driver and port "auto"?

Sorry for the late reply. Uninstalling maybe all that is needed but I think I had to reboot when I was testing the apcupsd plugin recently.

I didn't add the 2.7.5pre package to the plugin because of the issues I described before. I have since suspected that my flash drive may have become faulty (it would give an error in windows and drop off) and have swapped to a new one. I have been running 2.7.5pre for a couple days and have rebooted a dozen times without issue. I also turned on issues as that wasn't part of the original nut plugin repo. I added the plg file I'm using below. It includes 2.7.5pre and gets plugin version 2018.01.03 which is before your pull request. You will be notified of the 2018.01.06 update though when unRAID checks for updates. nut.plg Thanks for the suggestion. I agree an array key lookup is faster and more functional than using switch but I didn't see a real reason to rewrite that bit of code (it's from the original nut plugin which borrowed it from the included apcupsd plugin). I don't really plan on adding more columns and it wouldn't be that much faster with this array size. Could you explain more what you want from front and back end separation.

There's 2 different things going on here. I never got disconnects with my Cyberpower but the ASRock board I was using didn't have usb 3.0. The new Supermicro board does have usb 3.0. My new Tripp Lite does get disconnects. This is without nut installed. So it's either a Tripp Lite problem or kernel problem. I have read of similar problems on the freenas board. However if I disable usb 3.0 I still get sequential disconnects but as soon as I connect it to the nut usb driver it stops and nut works. This is with nut 2.7.4. Also it stops if I add the UPS to a vm. The other problem is every time I've compiled the latest nut It causes the flash drive to reset. This happen on both boards and both UPS's. There's a nut-2.7.5pre package in my NUT-unRAID repo if you want to try it but be warned and make a backup first. It's messed up the mbr a couple times and I've have to format and recreate the unRaid flash drive. I think the problem may be in their conversion of nut to libusb1.0. but I'm not sure.

That's a repo for a standalone version I created for someone. The plugin is still in my unRAID plugins repo. That repo is mostly dead and I've been creating separate repos for each plugin. So I'll create an unRAID-speedtest repo. But to answer your question I could create an unRAID notification, a toggle for notifications on or off in settings. Then a notification would be sent for each speedtest. It would use the unRAID notification system to relay the results. In the future I could also add different thresholds for warnings.

I just compiled the latest from GitHub. But it does the same thing as the last time. When the server is restarted and the nut driver loads, other usb devices get reset. This is very bad for unRAID as it resets the flash drive and the boot process stops. Unless powered down properly from the command line it can cause corruption of the flash drive too.

I don't know if you figured it out but I just swapped my Cyberpower 1350 for a Tripp Lite 1200 rack mountable UPS. I got the same constant usb disconnects and increasing device number. disabling both of these solved it for me. Advanced/Chipset Configuration/PCH-IO Configuration/XHCI Hand-off Advanced/Chipset Configuration/PCH-IO Configuration/XHCI Mode Essentially disabling usb 3.0. Edit: I still get usb disconnects but when I start nut, they stop.

I would make sure your cpu fan1 is spinning first. Maybe try a different header. I would start with the Noctua. Try it on REAR_FAN1

# ASRock Dual Socket # ipmi-raw 00 3a 01 CPU_1_OVERRIDE CPU_1 REAR_1 FRONT_1 FRONT_2 FRONT_3 # ipmi-raw 00 3a 11 CPU_2_OVERRIDE CPU_2 REAR_2 FRONT_4 # ipmi-raw 00 3a 01 01 AA BB CC DD EE # ipmi-raw 00 3a 11 01 AA BB CC # AA-EE values can be 01-64 # 00 is smartfan ipmi-sensors -t fan ipmi-raw 00 3a 01 01 64 64 64 64 64 # wait a few seconds ipmi-sensors -t fan ipmi-raw 00 3a 01 01 32 32 32 32 32 # wait a few seconds ipmi-sensors -t fan ipmi-raw 00 3a 01 01 00 00 00 00 00 Try the above commands and see if there's a change in rpm. These are for CPU_1 REAR_1 FRONT_1 FRONT_2 FRONT_3. You can also just target one fan by leaving the other fans 00 and just changing the one fan location. Use ipmi-raw 00 3a 11 01 AA BB CC for CPU_2 REAR_2 FRONT_4.

You're welcome. Glad we figured it out. Only other advice would be to add a fan minimum to keep the fans above the lower threshold or turn off the low threshold alerts in the Config Editor/Sensors config for each fan you want to shut off. With the Asrock boards you can actually have the fans turn off.

Try running the Config button from the Fancontrol page in the webgui

I figured your board was Asrock by the model# I would definitely update the bmc. Yours is almost original and 4 years old. Latest is 00.28.00. You just download the latest firmware and update it through the Asrock ipmi page. You probably need to update the bios if you haven't also. Latest is 3.30. Then run that last set of commands. You don't have to wait to long just a few seconds between commands.

Thanks happy holiday to you too. I didn't mention earlier but you need to wait a couple seconds between the ipmi-raw commands and the ipmi-sensors to give the fans a chance to spin up. Try these also ipmi-sensors -t fan ipmi-raw 00 3a 01 64 64 64 64 64 64 64 64 Wait a couple seconds ipmi-sensors -t fan ipmi-ra3 00 3a 01 32 32 32 32 32 32 32 32 Wait a couple seconds ipmi-sensor -t fan ipmi-raw 00 3a 01 00 00 00 00 00 00 00 00

try these commands and post the output ipmi-sensors -t fan ipmi-raw 00 3a 01 01 64 64 64 64 64 ipmi-sensors -t fan ipmi-raw 00 3a 01 01 32 32 32 32 32 ipmi-sensors -t fan ipmi-raw 00 3a 01 01 00 00 00 00 00

I'm not sure either. Maybe udev rules. I just disabled nut and setup the built in apcupsd. Apcupsd wouldn't work till I rebooted. However I could stop it and install nut which worked. I was gonna suggest to try a custom driver apcsmart or apcsmart-old.

What does it say when you run rc.nut start?

You can't fix that error because ipmifan will not run without a proper config. I'll give you some commands to try. I suspect your board may use similar commands to the e2c board but only has a single socket.