dmacias

What brand of fans do you have? You need 4 pin PWM. IPMITOOL is not included with this plugin. I use freeipmi. If you type ipmi the hit TAB TAB it will show youa list of commands.

Maybe there's too much power draw with the bluetooth.

What driver are you using now? Did you try what I posted before with the custom driver?

When I get a chance I'll test 6.1 and 6.2 in a vm. But they are both pretty old now and a lot has changed. 6.3.5 works.

I added cdrtools which includes mkisofs.

I pull the drives from the unRAID variable ini files. I plugged in a usb drive and I see now the dev.ini for non array drives doesn't get updated unless the array is stopped or started. I'll see what I can do.

Should be fixed to work with System Temp plugin. Not sure on the non display. Works fine on all pages for me.Try refreshing your browser cache.

I added the ability to show any sensor.

It's probably overwriting the ipmi footer with a blank footer. I used his System Temp plugin to model my that portion of this plugin. While all the variables and page are renamed it writes to same location of the webgui. I'll look at it again and see if I can make them work together. There could be a small use case where someone might want or need both installed.

You need to adjust the upper temp thresholds. What you have set would be valid for a CPU but your fans won't reach run 100% till your hard drives are 80°C. [emoji33] Something between 40 and 50 would be appropriate. Below is what mine looks like currently. FANA connects to 2 fans on the hard drive and FAN1234 are CPU, intake and exhaust fans. Also the minimum of 28 keeps my FANA at or above 300rpms. Will differ between systems. I have edited my Sensors config for each fan section like this. 200 for FANA and 300 for FAN1234. Not setting this will make your fans run at full speed if they drop below the OEM values which I believe were 700-500. Check you event log for threshold warnings. ## Give valid input for sensor type = Fan; units = RPMLower_Non_Critical_Threshold 200.000000## Give valid input for sensor type = Fan; units = RPMLower_Critical_Threshold 200.000000## Give valid input for sensor type = Fan; units = RPMLower_Non_Recoverable_Threshold 200.000000

What version of unRAID? What sensors do you have set to show? Do you have the dynamix temp plugin installed?

Minimum of 31 is 31%. So 2400 rpms seems reasonable. What are the other values set to? They are what is going to determine fan speed above that.

You mentioned earlier you were manually editing the config file. If you have a bad config or the settings are wrong it could lag the webgui. There would be a timeout for every ipmi command run. I would delete the ipmi plugin directory on the flash drive and start from scratch. You could try running ipmisensors from the command line and see if there's an error.

Could you give me a readout of ipmi-sensors?

I would just use ipmi-sensors in your script to get the data you need. What board do you have? Maybe someone else can shed some light on your temp sensors.

I'm not sure what you're trying to do. Could you elaborate a bit more. On what values you're trying to get and for what. The numbers are the sensor id's and the names are all from your system. This all comes from running ipmi-sensors.

I bet the built-in ups was running or you had a hung nut usb driver. Did you try running it with the custom diver (nutdrv_qx) and not in manual mode?

Did you disable the built in apcupsd? I would run /etc/rc.d/rc.nut stop. Then check for any ups processes running. ps aux | grep ups

Use manual mode. ups.conf should look like this [ups] driver = "nutdrv_qx" port = "auto" vendorid = "0665" productid = "5161" product = "USB to Serial" vendor = "INNO TECH" bus = "002" upsmon.conf should look like this MONITOR [email protected] 1 monuser monpass master SHUTDOWNCMD "/sbin/poweroff" POWERDOWNFLAG /etc/nut/no_killpower NOTIFYFLAG ONBATT SYSLOG+EXEC NOTIFYFLAG ONLINE SYSLOG+EXEC NOTIFYCMD "/usr/sbin/nut-notify" Run /etc/rc.d/rc.nut start and post the output.

Try using custom driver and type in nutdrv_qx. If that didn't work, edit the ups.conf and add the info from the scanner so it looks like this. driver = "nutdrv_qx" port = "auto" vendorid = "0665" productid = "5161" product = "USB to Serial" vendor = "INNO TECH" bus = "002"

I may add support to the Nut Details page (e.g a drop down based on the ups.conf) for monitoring other defined ups but that's about it. You could use the manual mode and add all the info to the conf files. The ups' would have to distinguishable from each other. From the manual: some combination of the "vendor", "product", "serial", "vendorid", and "productid" options. For instance: e.g. [mge]driver = usbhid-upsport = autovendorid = 0463[tripplite]driver = usbhid-upsport = autovendorid = 09ae

Just wanted to put your mind at ease. It was my mistake. Thanks for all the feedback as always.

I wouldn't call it a workaround. Most of the rc.scripts would do this if you called the wrong option. It would be the same as calling rc.libvirtd start instead of stop. That's what the -q did. It tried to start it in quiet mode. The main purpose of ipmifan is to start a loop. The errors don't add to the problem as it would still be in a loop. As long as ipmifan --quit is called it's benign and will exit after checking for pid or trying to kill any ipmifan processes. I call all three services in shutdown to stop ipmiseld, ipmitail and ipmifan. I will double check that you couldn't somehow start the script from the webgui without the proper variables set. I believe that is already the case.

It's fixed in the latest. If you have already rebooted with the latest, it should work. The shutdown only gets written on plugin install but I didn't add anything to change the -q to --quit, maybe I should have. Just check /etc/rc.d/rc.local_shutdown for the ipmifan line. It should be at the button. Make sure it has --quit or remove it completely. As far as settings disappearing, it may be that the cfg files were open during the hang and were zero'd out when shutdown was forced.

Thanks I still wasn't sure why my system never hung but that explains it. The ipmi plugin Slackware package's do install script adds 3 lines to rc.local_shutdown to shut down the services. The ipmifan line had a -q instead of --quit. So that error was the fan script trying to run but not configured. Hence the line 322 error. Since I use fan control I wouldn't see that error.