dmacias

I set in my asus/merlin router in the dnsmasq.conf.add on the jffs partition (/jffs/configs/dnsmasq.conf.add). Or you can add it to your router's dnsmasq.conf with your domain name and the local ip formatted like this # add local addressaddress=/yourserver.example.com/xxx.xxx.xxx.xxx

I couldn't find sqlite, glib2 and kernel headers to match. So the ones included are slightly different. The glib2 is only an incremental release and sqlite is newer. The kernel headers are older. I need to find the newer source. They will show as update in the table.

Give this a try if you want. I couldn't find a couple packages to match the built-in packages though, sqlite, glib2 and the kernel-headers. So those are slightly different versions. unRAID DevPack

unRAID 6 DevPack - Dev tools Assorted tools for unRAID development, mostly for compiling packages. For 6.3 and 6.4+ https://raw.githubusercontent.com/dmacias72/unRAID-DevPack/master/plugin/DevPack.plg Everything is set to install when toggled On and applied. Toggling Off and Apply will just toggle off and delete the package from the flash drive. There's no uninstall since some of these are default packages built in to unRAID. To remove: Toggle Off, Apply and reboot. Anything set to On will be installed at unRAID boot also. Change Log ###2018.10.23 - fix only include headers for inherent unRAID packages - add autov to css and js - remove support link from readme ###2017.10.12 - plugin version still 2017.10.01b - fix libunistring package, include symlink for libunistring.so.0 - added full glibc package - removed everything but headers for all preinstalled unRAID packages ###2017.10.01b - fix stickyheaders for new themes - update tablesorter to 2.29.0 - add status for installed and not installed packages ###2017.07.02 - fork Nerdpack to create DevPack - add all dev packages and descriptions - rename all variables and file names to reflect fork - remove all non relevant code ###2017.06.17 - combine delete and uninstall switch - add cleanup of old packages - add support for azure and gray themes - change to separate repo - update tablesorter ###2017.02.06 - fix support link - add perl toggle for vim ###2017.01.31 - move local tablesorter to cdn - add support link to readme ###2016.10.20 - fix: php7 compatibility ###2016.10.09 - fix: not creating package directory ###2016.10.08 - fix: false positive of installed packages - fix: packagemanager bug if cookies are missing ###2016.09.18 - fix: packagemanager array errors ###2016.09.16 - fix: empty package list on new install or upgrade - update tablesorter to 2.27.6 ###2016.09.10 - add: popup for unRAID version change or empty downloads folder - add: always compare package checksums - fix: remove corrupted packages - fix: remove failed downloads - fix: add package desc and json to scandir filter ###2016.03.15 - enable apply button if update ready - fix: remove old package settings from config after package update - create separate package repos for 6.1 and 6.2 - update plugin for unRAID 6.2 compatibility - update packages for 6.2 ###2016.02.23 - fix: search for a partial match of packages used in other plugins ###2016.02.17 - remove curl progress bar - separate plugin depends by comma - only show update status of selected packages when processing ###2016.02.15 - update tablesorter - fix spacing of processing messages - remove array start event package install - move initial package install to plugin install ###2016.02.08 - fix permissions on event script ###2016.02.02 - add check for other plugin dependencies on uninstall ###2016.01.25 - Merge eschultz pull request - tweaks to tablesorter to restore saved filters - minor optimizations ###2016.01.24 - Merged eschultz's package repo and following fixes - Fixed first time running warnings about missing packages.json / desc files - Fixed bug preventing Select All from being toggle-able - Fixed bug in Select All and dependent package checkboxes / race condition - Eliminated vertical space gap between page header and table ###2016.01.16a - add metric parser to sort units ###2016.01.16 - minor diplay changes - add tablesorter as a separate package ###2016.01.15 - fix filter save - add filter reset button ###2016.01.10a-c - fix name of package description file ###2016.01.10 - added dynamic package description tootips - updated tablesorter to v2.25.0 - add tablesorter widgets (filter, saveSort, stickyHeaders, hover-highlight) - added cli options to packagemanager script ###2015.12.30 - create packages directory on install ###2015.12.15a - remove command output ###2015.12.15 - minor fixes ###2015.12.14 - add update functions - add delete package function - fix some minor bugs ###2015.12.13 - initial commit of wrapper plugin for packages in repo

There was some discussion about this before. I think those would be better in a separate Dev Pack. I could just clone this repo and change all the names and variables. Then add the packages you wanted and the others that I use. What version you need it for? 6.3 or 6.4? I have versions for both to match.

Thanks. I just went ahead and added the screen terminal info to the screen 4.6 package. Other packages like tmux have their own terminal info included.

Thanks. I was wondering if you could help me with a problem. I thought I needed the updated version ncurses-6.0-x86_64-3.txz for unRAID 6.4 for the problem with the Screen package and backspace not working. But I tracked it down to the /usr/share/terminfo/v/vt100. When I installed the full ncurses-6.0-x86_64-3.txz package the vt100 term info was installed and backspace worked. So the problem is, I compiled and installed the same screen-4.6.0-x86_64-1.txz on unRAID 6.3.5 and 6.4 but the backspace doesn't work on 6.4 unless I add the vt100 terminal info. It works fine on 6.3.5. So why is /usr/share/terminfo/v/vt100 required for 6.4. I could just add the vt100 term info to the screen package.

What version of the plugin are you using? latest is 2017.06.17. I moved everything to its own repo.

I recompiled tmux. Should work now.

I'll have to update tmux

Basically yes but it's a little more complicated than that. The script is written in php with a main while loop and a couple nested loops. One for the fans/commands. One for the polling time which is a variable loop based on polling time but fixed at 10 sec to check the fan config for changes while waiting. E.g. It sleeps for 10 sec then loops 6 times to create a minute. I would need to carry a global true/false hdd poll and sensor poll and maybe a couple counters to count the time through the main and nested loops. So when time is reached, poll is true. It becomes more complicated if someone were to set the hdd poll less than the sensor poll. I could limit it in the settings or deal with that in the script. I'm not sure of the impact from reading ipmi sensors and setting the ipmi fans every 10 secs. I have seen it choke on too frequent commands. This could lead to the unRAID webgui becoming unresponsive waiting on ipmi commands to render the Settings and Readings pages or the whole webgui waiting to display the footer. It could also error out and not display anything. There could be problems writing config files with the editor. All that said, I'll see what I can come up with but there may be some side effects on shorter intervals.

I not sure what you mean. For hard drives, smartctl can impede drive performance if run too often. CPU and fan speeds both use freeipmi to get and send to the BMC. Which can lock up and not respond.

Im using a Powerful Intel Xeon E3-1245v6 CPU with a TDP of 78W and I can confirm fast temperature spikes. That's a good use case. We've had some discussion in here about this but I believe FANA, FANB.. are for peripherals including hard drives. And when set to auto are controlled based on system temp. FAN1234 are based on CPU temp. I was going to ask what the temps are when set to auto and which mode (high I/O, standard, optimal). But if your CPU is on FANA then that wouldn't work. It mentions the same thing in the link. Thanks for that. I hadn't read that one. It has a good idea about setting the mode first to keep the BMC from changing the fan speeds. Very thorough write up. I may be able to just add a hdd polling time and then add back the 10 sec intervals below 1 min. But still need to be careful about too many ipmi commands.

That temp is the highest hdd temp pulled from from unRAID webgui. It may differ depending on when it was polled and when the webgui actually pulled it from the hard drive.

That could lead to a similar problem by hammering the ipmi. It could freeze up the IPMI Settings/Readings pages and possibly the entire webgui if you have temps and fans in the footer. I have had this happen before when an ipmi command hung. My question to you would be what use case would you need such fine control over the CPU fan? Is there a situation where the temp is going to rise that dramatically in less than a minute. The fan should already be spinning and cooling to some degree. It might have a small spike in temp but should even out. The way the fan control its written right now it would be difficult to add this. The highest hard drive temp is injected as a sensor when I get ipmi sensor readings. So it shows up like an ipmi sensor. I wrote the fan control script with the mindset to minimize executions. It won't execute if the pwm is the same when polling. I also have it round the (% value x 16) then x 4 to get the pwm instead of just rounding x 64. Partly so it won't execute when a value changes just 1 point and goes from say 30 to 31 then back to 30. It needs to go to 32 or drop to 28. This then creates a +/- 4 in accuracy. So if you were to run it at a smaller interval, it may not even change anything. I would say run it a little longer and watch the fan log.

That's what I thought. Thank you for clarifying that. I run both tunable and fan control at 3 min intervals.

There's a beta version in the OP. I'm moving it to its own repo. So when I was ready I was going to update the CA version to point to the new repo (IPMI-unRAID). Maybe you could shed some light on the issue in the post above. The plugin webgui uses unRAID vars to get the hdd temps but the fan control script uses hdparm to check standby and then smartctl to get highest temp. Could intervals of 10, 20 or 30 seconds cause problems.

I pulled the update. There should be a new update reverting the changes. I need to investigate more the impact of running the fan control script in intervals less than a minute. The script uses smartctl to get the highest drive temp. I was starting and stopping the script a lot, testing some settings and apparently one of my parity drives got a sata error. I didn't notice this till this morning after the mover caused parity errors on that parity drive. I'm not sure if they are related but I decided to pull the update till I can look through the logs. Also check why I wasn't notified till the parity errors. I would like anyone using the beta to update just in case.

Unless you lower the thresholds of the fans on the Supermicro, they will spin up to full if they fall below the threshold. I changed Temperature Polling Times to seconds and added 10 sec intervals below a minute. Everyone will need to change settings, save and restart fan control otherwise the polling will be 6 times less. So 1 min = 10 sec. I added fan max speed. Didn't see the edit about the network connection change and fan control. I'll fix that on next update.

Forgot to remove the tablesorter package. It uses a cdn link now. It's fixed now.

Thanks I fixed the link.

It's for the beta. I won't update the old repo except to update the plugin file to point to the beta/new repo. 2017.06.21 The update was to fix the auto setting and to return the fans to the previous mode set in the BMC.

Do you have a manual host set or is it auto?

Yes that's the way the fan control has always been. The original point of the plugin's fan control was to control the side fans of my case based on hdd temps especially during parity checks/rebuilds.

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 Standard 01 is Full 02 is Optimal which is lower than Standard 04 is between 00 & 01 I'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.