dmacias

Could you tell me what the output of "ipmi-sensors -t fan". Since you have more fans connections than I do, I'd like to know the name of the other 2 fans since the ipmi-raw command has 8 values. Here's mine. root@server:~# ipmi-sensors -t fan ID | Name | Type | Reading | Units | Event 13 | CPU_FAN1 | Fan | 1100.00 | RPM | 'OK' 14 | REAR_FAN1 | Fan | 800.00 | RPM | 'OK' 15 | FRNT_FAN1 | Fan | N/A | RPM | N/A 16 | FRNT_FAN2 | Fan | 800.00 | RPM | 'OK' 17 | REAR_FAN2 | Fan | N/A | RPM | N/A 18 | CPU_FAN2 | Fan | N/A | RPM | N/A root@server:~#

I bet that's loud. Mine only go up to 1500, l believe. I took a look at your case and it does say right on the page 5000 rpm pwm fans. I also looked at your motherboard manual and it says all fans default to Full On. But the manual didn't say what other values there are other than Full On. And didn't show any smart fan settings. Also you can check just the fans after you try the raw command like this ipmi-raw 00 3a 01 00 00 32 00 00 00 00 00 ipmi-sensors -t fan

Given your fan rpms I'd say they aren't pwm fans or controllable by your motherboard and are running at full speed. My board can only control pwm fans. It would run the 3pin case fans at full speed. I bought a few noctua pwm f-12s or p-12s

That's working fine. It just means freeipmi didn't recognize the oem command. But it shows it was sent and received. If it was the wrong netfn then you'd see "Invalid netfn value." Now to test, you'd want to adjust a value for a fan to 64 and see if the fan reads full speed then back to 00 and see if it returns to auto. Or try a lower value like 20 or 30. You don't need the --debug option. It just shows the send and receive status. Edit. Also let me know your fan names and which spot in the hex they correspond to. Mine look like this ipmi-raw 00 3a 01 00 00 00 00 00 00 00 00 ipmi-raw 00 3a 01 AA BB CC DD EE FF GG HH 00 = smartfan mode 01 - 0x64 = 1% - 100% 'CPU_FAN1' => 'AA', 'CPU_FAN2' => 'BB', 'REAR_FAN1' => 'CC', 'REAR_FAN2' => 'DD', 'FRNT_FAN1' => 'EE', 'FRNT_FAN2' => 'FF'

Thanks for helping me figure it out.

That was the reasoning behind converting the date and time to a sortable numeric format. Could you run ipmi-sel from the command line and see if you have some weird dates or times that don't fall in the format | Mar-27-2016 | 00:57:28 |. oh cool. Yes, I have several that have "PostInit" in both the date and time columns. See attached. Added a couple checks for valid date. Should be fixed now.

That was the reasoning behind converting the date and time to a sortable numeric format. Could you run ipmi-sel from the command line and see if you have some weird dates or times that don't fall in the format | Mar-27-2016 | 00:57:28 |.

I'll check it out in a bit. Thanks for looking into it. There's a problem in ipmi_helpers.php and the date format. To use archive just click the switch. Anything deleted, one or all gets appended to a log file in the plugins directory.

###2016.03.25 - fix: archived events page update on event delete - fix: archived events with same timestamp - fix: archived events tablesorter pager ###2016.03.24 - update for 6.2 to freeipmi 1.5.1 - new installs on 6.2 will work fine - 6.2 users with previous install will need to reboot or install libgcrypt-1.6.5 (temporarily) to use freipmi 1.5.1 - libgcrypt-1.6.5 is included with unRAID 6.2 and previous versions downgraded it to 1.5.5 to use freeipmi 1.4.11 - http://ftp.slackware.com/pub/slackware/slackware64-current/slackware64/n/libgcrypt-1.6.5-x86_64-1.txz - fix: bug local ipmi timeout webgui to wait for ipmi (only affected systems without local ipmi) - changed backup events to archived events - add archived event page and switch

Sorry you caught me in the middle of updating the plugin. I removed that package prematurely. The libgcrypt version included in unRAID 6.1 and 6.2 are different. It is not included anymore since I compiled freeipmi 1.5.1. So freeipmi 1.4.11 will work with 6.1 and freeipmi 1.5.1 will be for 6.2. They will use the unRAID included libgcrypt for each version. I'll finish updating in a bit.

compiled shellinabox unofficial 2.20 Notable changes/fixes: ignore VTE OSC6 and OSC7 escape sequences adjust scale on IE option to disable the peer check Added support for middle-click paste, #350. Improved iOS support, #354. New logic to enable soft keyboard icon, #119, #321, #354. Disable HTTPS fallback using the URL /plain. Consequently disables automatic upgrades from HTTP to HTTPS, #355. (CVE-2015-8400).

waited a few days, this repository appears to still be broken. Works for me. I click on the link in your post and it downloads. Why not host the packages in your github repo? Would eliminate the possibility of any broken links. No need. Oregon State University is rock solid: http://slackware.osuosl.org/slackware64-current/slackware64/l/parted-3.2-x86_64-2.txz If the package versions or build versions get updated in slackware current the link would be broken. I've seen the same package name and md5 changed later because the package was updated and not the name.

waited a few days, this repository appears to still be broken. Works for me. I click on the link in your post and it downloads. Why not host the packages in your github repo? Would eliminate the possibility of any broken links.

Running at Full is raging loud, too loud for me. Is there an easy way to tweak the bios settings to different fan levels to see the speed change? Or do I need to set the level, save and reboot to see the change? Yes in the the smart fan control in the bios you can tweak the curve for the temps/power ratio. My noctuas are running at 800 rpms and low 30s. You may be able to bump them up to just 600 and that may be enough. The way I have them set allows for parity sync/checks to stay in the high 30s to low 40s. So they are probably set too high for the majority of time but high enough to cover stressful times. Also if your system/cpu are too cool then smart fan won't spin the fans fast enough for high drive temps. My board is fanless.

No trouble, it literally took a few seconds. So should I put 4.6.5 back. It looks like there were a number of fixes since 4.6.1

Ok I switched to the 4.6.1 package.

Sorry I couldn't reproduce that error. The closest I got was a bind (...) permission denied when I changed .screen to root user. What version unRAID are you on?

I'd say it's permissions on your home or .screen directory. Just delete /mnt/user/steve/.screen/ and try again. I just created a home directory for a user under /mnt/cache/home, logged in as user and screen worked fine.

Even though it says it updated perl, perl continues to show an update available. Which version of unRAID? Any other plugins or installations with perl. While I plan to try and make it smarter right now it's not. So if you were on 6.1 and had the python 2.7.9 installed but another plugin or you installed 2.7.11 then NerdPack would show update ready. This was on 6.2b18. I haven't even had my backup server turned on since 6.2beta was released and may just leave that one on 6.1.9 for now. I'm pretty sure the only reason I had perl turned on was for sensors detection. I am not using any plugins for anything that has a docker. I am fine without perl and will probably turn it off. Just thought I would mention what I was seeing. I did notice Nerdpack showing a different version of python when you updated speedtest before updating NerdPack but that is all good now. Just perl showing update available after it said it updated it. Thanks for pointing that out. The perl for 6.2 has the same version but a different build number. I'll have to fix that. I updated speedtest and vm wake on lan plugins first which use python from NerdPack. It shouldn't be a problem now that I split the repos. As long as all the plugins are up to date.

Even though it says it updated perl, perl continues to show an update available. Which version of unRAID? Any other plugins or installations with perl. While I plan to try and make it smarter right now it's not. So if you were on 6.1 and had the python 2.7.9 installed but another plugin or you installed 2.7.11 then NerdPack would show update ready.

I updated the plugin to work with 6.1 & 6.2+. I created separate repos for each and updated the packages for 6.2. If blank, you will have to hit F5 or click Check for Updates the first time visiting the settings page. If coming from 6.1 to 6.2 just click apply to upgrade all packages.

Yes they are different. The command options are ipmi-raw [<lun> <netfn> COMMAND-HEX-BYTES] lun is usually 0 and COMMAND is usually 01 but the 3a netnf is proprietary. And the Hex may be different. I seem to remember that the supermicro boards may have separate commands for each fan.

I only have raw values for my ASRock board that have been tested to work with c2750d4i, c2550d4i, E3C224D4I-14S, and one other. I'm not sure if it will work with your ASRock board but it should. If you test, let me know your fan names and id's and if the are the same. I don't have any raw commands for any other board manufacturer. So if others want to try and find out the raw commands and test that's the only way I can add support for that board. When I was figuring out raw commands for test events I started working on the fan script again using freeipmi now. This is the command if you want to test. The debug is just to see the send and receive response. ipmi-raw 00 3a 01 00 00 00 00 00 00 00 00 --debug This would set all fans to smart mode And here's a key for the fan values ipmi-raw 00 3a 01 AA BB CC DD EE FF GG HH 00 = smartfan mode 01 - 64 = 1% - 100% ID 13 'CPU_FAN1' => 'AA', ID 18 'CPU_FAN2' => 'BB', ID 14 'REAR_FAN1' => 'CC', ID 17 'REAR_FAN2' => 'DD', ID 15 'FRNT_FAN1' => 'EE', ID 16 'FRNT_FAN2' => 'FF', ? => 'GG', ? => 'HH' So for testing I would run a command like this to set CPU_FAN1 to full speed and check the fan jumps to full rpms ipmi-raw 00 3a 01 64 00 00 00 00 00 00 00 --debug set CPU_FAN1 to 1/2 speed ipmi-raw 00 3a 01 32 00 00 00 00 00 00 00 --debug Set all fans full speed ipmi-raw 00 3a 01 64 64 64 64 64 64 64 64 --debug

I know it's a little ambiguous. Maybe I could label the switch Backup on Clear or Save on Clear and the lable the 'dellete all' 'clear all' With backup on it sets the ipmi-sel option to --post-clear instead of just --clear. This clears the SEL after displaying all the SEL records. The output is then stored in a gzip like this ipmi_event_log-2016-03-12-214431.gz in /boot/config/plugins/ipmi/logs. I'm thinking we don't even need a switch, just have it backup automatically when you press delete all? What sort of format is the backup in? Is it something the plugin can use somehow or is it something else? It's the same output as if you typed ipmi-sel from the command line. I think I know where your going. I could make an Archived Events tab. ipmi_event_log-2016-03-12-214431.gz

Fixed bug with freeipmi creating an init.d directory on install. I guess it's more a bug with libvirt or virsh but virtual machines won't autostart if there is an /etc/init.d directory. And I already got a talking to cause the tv's in the house wouldn't work because I didn't notice that my Mythbuntu VM wasn't started.