dmacias

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.

I updated some of the screenshots in the original post. They were outdated. The current fan control does include a fan speed minimum and the ability to link a fan to a specific temperature sensor. The temperature regulation is based on a scale between the upper and lower temperature thresholds and the reading of the chosen sensor.

I think the x9 would only allow fan control with all fans low, med, high. Yes this plugin can change the thresholds from the Readings/Sensors Config page. Just edit and save.

Thanks I'll let you know when I have something. I already have scripts written in php that work with Asrock (ipmifan and ipmi2json). I just need to modify them for SM raw commands.

Yes and it should work on the board I have. I had seen those commands before, they are in my SM notes. I have that thread in my favorites although it's quite a bit longer now. I just wasn't sure which boards they work on. When I get my server up I'll get started on it.

You can use the included ipmi-raw or ipmiraw (adds the network, ip , user and pass from ipmi settings) ipmi-raw 00 30 70 66 01 00 64 00 - Get value 01 - Set value 00 - FAN 1/2/3/4 01 - FAN A (possibly different groupings on some models) 00 to 64 - Speed (64 is max). 00 or 01 may set to auto if I remember

I'll have to give it a try on my x10.

I just recently built a Supermicro x10 backup server. Just waiting on a new power supply. So I'll have a machine to test on. However I'm not sure fan control support will help. Supermicro only allows changing a group of fans with low, med, high.

All credit for the "skirt" goes to danioj. He's the skirt master[emoji1]. You can use a thin piece of cardboard, plastic or some other pliable material. I used plastic for durability and longevity. I just cut a piece that was as long as the drive cage and a little wider than the distance from the drive cage to the side intake fans. Then I just wedged it into the case. It fits in between the motherboard and two side intake fans perpendicular to both and rests against the bottom of the drive cage. Depending on your settings for fans this may not be enough. This isn't a fault of the case but if you have your fans set with a smart fan value too low they may not spin up fast enough to cool the hard drives or the motherboard and other components. This is due to the fact that the smart fan is usually cpu dependent. So if your cpu never gets hot enough everything else may cook under load. You could try raising the smart fan thresholds, set them to a fixed value or I fixed this problem with an ipmi plugin I created. The ipmi plugin's fancontrol is only useful for Asrock boards right now. Although I just set up a backup supermicro server. So soon I'll add support for supermicro. It allows you to control individual fans based on separate temperatures. So you could control the front two fans based on hard drive temps and control the rear fan based on motherboard temps, also even the cpu fan.

Thanks. Update went fine. Everything is working great.