dmacias

I'm not sure. I see what you mean but I'm not sure 1-4 = system and A = CPU. I got this from their fact. I know its from a different Motherboard but I have seen similar. Sometimes it seems like there's some conflicting info. Question We have a X9SCL-F and connected Chassis fans to FAN-1/2/3 and CPU fan to fan header "A" on this mainboard. Now we see that the fan spin up/down, or sometimes full speed. What can we do? Answer FANA is for add-on card and controlled by system temperature. FAN1~4 is controlled by CPU temperature. CPU Heatsink fan should not be connected to FAN-A. CPU Heatsink fan can be connected to FAN-1. Chassis fans can be connected to FAN-2~4 or FAN-A.

Also if anyone who tries the beta above wants to go back you can just uninstall it and install the plugin from the OP.

The FAN1234 is just a the group. The fan speed that is shown is only for the first fan available I the group. That's why hiding the other fans shows rpms. It's really just a reference and is never updated unless you refresh the page. I was thinking of just picking the highest or getting rid of it altogether. I need to double check the auto to make sure I'm using the right value. But auto right now sets a value of 01. Edit: 00 or 01 does not equal auto. 00 is auto for ASRock. You also might check your manual but I'm pretty sure FANA is for I/O but not sure what temp sensor it's based on. I believe FANS 1, 2, 3 & 4 group are based on cpu temp. There was some discussion a few pages back.

If someone with a Supermicro X10 or X11 wants to give it a try here's the latest beta I've been working on. It is fully functional. No bugs or issues that I know of yet other than I'm still working on ASRock dual cpu support and Supermicro X9 support. So fan control will not work for a X9 board yet. This is a new separate repo I split from my unRAID plugins repo and when I feel this is right I'll push an update to the main repo and point it to this one. https://raw.githubusercontent.com/dmacias72/IPMI-unRAID/master/plugin/ipmi.plg

Did you get the same delay on chmod or chown? I might of just had way more events than normal use or too many small files. You could use something like this to check permissions in the firstrun script if they've changed stat -c '%u%g' /var/cache/zoneminder/ == '033' or stat -c '%U%G' /var/cache/zoneminder/ == 'rootwww-data' stat -c '%a' /var/cache/zoneminder/events/ == 777 or 755 whatever the value is supposed to be

I also updated the plugin for 6.4 themes and moved to a separate repo of its own. I pushed an update to the old plugin repo that will point to the new. Any subsequent updates will come from the new. So even if you install the old plg link it will install from the new repo. Maybe @jonp could change the link in the OP. https://raw.githubusercontent.com/dmacias72/unRAID-NerdPack/master/plugin/NerdPack.plg

I add xinetd.

Thanks. I figured that out from the run script on your github. Yes it was taking that long, even when I ran the chmod and chown from the unRAID command line also. I purged all the events and switch to ext4. I also increased my post buffer (15sec x 20fps) a bit more to get longer/less events. May need to adjust sensitivity. Thanks for the filter suggestion. I left the purgewhenfull but have it set to 75 (in case the hard drive gets full). I created a separate filter PurgeByAge using -14 days.

I'm not sure what was wrong with the permissions. The owner was correct and the write permissions were drwxr-xr-x. The only problem I see is, if there are a ton of events it could take a while for the docker to start since the data directory is chmod and then chown. I had a ton of events and was using an xfs partition. It took more than 20 minute to start. I wiped the events and formated the drive to ext4. I don't think anything needs to be fixed. Just sharing my experience.

What are the write permissions supposed to be for the data directories? I know the owner is 0:33. I had a problem when I swapped out my data drive for a larger faster drive. I copied all the data from the old drive to the new. The permissions look the same. I checked ls -la in the container (/var/cache/zoneminder) and at /mnt/disks/zoneminder. However zoneminder can't mkdir, permission denied. It couldn't create the new 06 month directory. The top directories in /data (events, images, temp) had 777 but the monitors 01 & 02 had something different. Until I chmod 777 it wouldn't record any events.

Added it for 6.3 & 6.4

Did you try the Revert button on the Sensors Config Editor page?

Did you try clicking Revert to pull a current config from the BMC? I'll have to test what happens if I write the original config now. Edit: The ipmi-sensors.config is a static file. It is only changed if it doesn't exist or Revert is clicked. This is so threshold values can be loaded when unRAID starts for those system that don't save the settings. The config file and the web editor should matchup if reverted. Also, I tried writing my first config above with details for FAN3 but no FAN4. Write was sucessful but pulling a config resulted in the second config with the correct details for FAN4 and no FAN3. So I can't change fans values that aren't connected.

When I got my X10SLL-F board it would boot up and all the lights looked good but no video post. I couldn't connect to ipmi either. I thought the bios might be old and not compatible with my processor. So I was kinda stuck. I had to use wireshark to sniff the ip of the BMC. And found there was a manial ip set. The bios and BMC were latest versions though. It turned out the power supply was bad. But I did factory reset the BIOS and BMC. Here's what my sensors config file looks like Section 540_FAN1 ## Possible values: Yes/No Enable_All_Event_Messages Yes ## Possible values: Yes/No Enable_Scanning_On_This_Sensor Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Non_Recoverable_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Non_Recoverable_Going_High Yes ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Critical_Threshold 700.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 500.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 25300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 25400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 25500.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 607_FAN2 ## Possible values: Yes/No Enable_All_Event_Messages Yes ## Possible values: Yes/No Enable_Scanning_On_This_Sensor Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Non_Recoverable_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Non_Recoverable_Going_High Yes ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Critical_Threshold 700.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 500.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 25300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 25400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 25500.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 674_FAN3 ## Possible values: Yes/No Enable_All_Event_Messages Yes ## Possible values: Yes/No Enable_Scanning_On_This_Sensor Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Non_Recoverable_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Non_Recoverable_Going_High Yes ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Critical_Threshold 700.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 500.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 25300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 25400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 25500.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 741_FAN4 EndSection Section 808_FANA ## Possible values: Yes/No Enable_All_Event_Messages Yes ## Possible values: Yes/No Enable_Scanning_On_This_Sensor Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Non_Recoverable_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Non_Recoverable_Going_High Yes ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Critical_Threshold 700.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 500.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 25300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 25400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 25500.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection So I'm missing details on fan 4. Originally I had fans connected to FAN1,2,3 and A. I had changed my fan arrangement and moved my CPU fan to FAN4. So FAN3 is empty. So the previous config is from the original fan configuration. I clicked on the REVERT button on the Sensors Config Editor page, which pulls a new config from the BMC. This is what I got. Section 540_FAN1 ## Possible values: Yes/No Enable_All_Event_Messages Yes ## Possible values: Yes/No Enable_Scanning_On_This_Sensor Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Non_Recoverable_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Non_Recoverable_Going_High Yes ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Critical_Threshold 700.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 500.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 25300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 25400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 25500.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 607_FAN2 ## Possible values: Yes/No Enable_All_Event_Messages Yes ## Possible values: Yes/No Enable_Scanning_On_This_Sensor Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Non_Recoverable_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Non_Recoverable_Going_High Yes ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Critical_Threshold 700.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 500.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 25300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 25400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 25500.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 674_FAN3 EndSection Section 741_FAN4 ## Possible values: Yes/No Enable_All_Event_Messages Yes ## Possible values: Yes/No Enable_Scanning_On_This_Sensor Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Non_Recoverable_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Non_Recoverable_Going_High Yes ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Critical_Threshold 700.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 500.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 25300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 25400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 25500.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 808_FANA ## Possible values: Yes/No Enable_All_Event_Messages Yes ## Possible values: Yes/No Enable_Scanning_On_This_Sensor Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Non_Recoverable_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Non_Recoverable_Going_High Yes ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Critical_Threshold 700.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 500.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 25300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 25400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 25500.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection So there's no config values for missing fans and the config file may be out of sync if changes have been made. Also these are the default values. I haven't changed a thing.

Sorry, from your previous posts I wasn't sure how you were editing the thresholds. I saw you mention the editor was missing details. Are you using individual commands or the ipmi-sensors-config checkout/commit command? You wouldn't want to enable the "load on unraid start" switch because it would just load the bad/empty config file. Also can you verify that the /config/plugins/ipmi/ipmi-sensors.config file is actually missing the details also? There could be a problem with browser vs editor? I know the editor/codemirror javascript doesn't play well with mobile browsers. It displays fine but editing has problems. Also I know it might be a pain but have you thought about factory resetting the bmc? The ipmi-sensors-config checkout command pulls the info directly from the bmc. Maybe there's some sort of corruption. If the editor and actual ipmi-sensors.config file are missing details this may indicate a problem.

I will add X9 support too. I haven't tried those commands on my X10 to see if they work also. Just the X10/X11 commands.

Are you using the Sensor Config Editor to change the thresholds or are you using the command line? The Editor just uses the ipmi-sensors-config checkout command to save the the config to the flash drive in the plugin folder and then loads that in the in-browser editor. Then when done editing it saves the config and loads it with the commit command. Some boards save these changes between reboots some don't. The switch is for those that don't. So your sensor config loads when unRAID starts up.

They work as well on my X10SLL-F. Once I get working on it, it should get done fairly quick. Since all we're dealing with is basically two fans, FANA and FAN1234. I should be able to use what I've already coded for the Asrock boards.

Nothing yet. Other than I tested the ipmi raw commands. I was waiting on a power supply for my main server, so I could put the old one in the backup (SM X10) server. I should have time this weekend now that the X10 server is up.

There are firmware updates for the Marvell controllers on the Asrockrack website.

I thought a drop below any threshold on these boards would ramp up the fans until the bmc realized the temp was fine. Then it would drop the rpm and begin the cycle again of lowering and raising the rpms.

I was installing a new corsair sfx 600 power supply and thought I'd try and get a shot of the "skirt". It's the opaque plastic piece between the motherboard and backplane.

What board do you have? I've been meaning to change the bmc reset button to cold reset instead of warm.

I just added it[emoji1]

Findutils is already included with unRAID. I added slocate which has an updated locate (slocate) and updatedb. You can point it to save the database on your flash drive so it will be persistent through reboots.