t33j4y

trurl, thanks. I guess I am gonna bite the bullet and get going. Have started the extended smart tests now :-)

jonathanm, thank you for your suggestion. You mention that parity can be rebuilt in a few hours - am I missing something or is the parity rebuild not equal in duration to a parity check? If so, that's like 16 hours for me so the process you outline will take a long time with three parity checks across the seven steps.

I am about to shrink my array as I want to phase out an older drive and have plenty of space as is. The drive contents have already been relocated using unBalance. However, I am a bit uncertain about the process as I have seen a couple of different approaches. Can someone who has followed this procedure: https://lime-technology.com/wiki/Shrink_array#The_.22Clear_Drive_Then_Remove_Drive.22_Method verify that this will in fact allow me to remove the drive without breaking parity? If it matters, I am running dual parity. Thanks in advance for any input and advice! BR, Thomas

Lothar, thanks for the input. Good link! I did pick up on the thresholds needing change, but picked up on it in this post by dmacias earlier in the thread. So I changed it through the interface :-)

Thanks - have now done that :-)

I stand corrected and humbly apologize :-(

Ermm. Ok - I certainly did not mean to offend anyone, but based on what I read in the 6.4.1 release thread, he seemed to be in control of the plugin. Thank you for the input - will try to reinstall from CA as you suggest.

I just lost my SABnzbd docker install due to still having Squid's "Advanced Buttons" plugin installed while updating the docker :-( If at all, I would like to avoid having to configure everything over again when re-installing. I have a recent copy of the of the appdata folder. Any suggestions on how I minimize the effort involved in getting this back on its feet? Thanks in advance for any help!

So, I had this happen to me as well. Due to an update of cache pool drive, I actually have very recent backup version od the cache drive version with the docker (SabNzbd) that disappeared after updating. Can I somehow roll that back?

Alright, makes a lot of sense :-) Does the HDD temp sensor work off of the highest reading across the disk pool or the average of the pool?

You may have to factory reset the bmc. Also remove the .config files from the ipmi plugin directory on the flash drive. And make sure that the load config toggle switch is off on the sensor editor. Found this and toggled the switch to "OFF", after restarting the server. So far it seems to be holding the config without going full blast. Can see on the Readings tab that RPM is actually adjusting. *fingers crossed* Still wondering why the CPU fan - a Noctua NH-L9x65 rated at RPM 600 - 2500 ± 10% seems to never go under 1000RPM, even though the fan speed minimum is 31. So compensating for the ± 10%, 31% gives a range of 775-852 for lowest RPM, as long as temp is below 40 degrees. But even when temp is below 40 degrees, it still hovers at around 1000.

You asked about the error messages - here's an example: So, some progress now. Setting to Full Speed seems to have helped - pulsing is gone and the plugin seems to have regained control over rpm. I have edited the three Lower Critical values for the case fans to be at 300/300/300 and the cpu fan at 500/500/500. Case fan thresholds for temp are 35/40 and for rpm 40/100 CPU fan thresholds for temp are 40/60 and for rpm 31/100 I'm gonna fiddle around with it now to find final and sensible settings :-) Thank you so much for putting me back on track! Edit: Spoke to soon :-( After changing the RPM settings, it is now back to full blast... Did the following to recover: 1. Uninstalled IPMI plugin 2. Removed IPMI folder in /config/plugins/ 3. Shutdown server 4. Reset BMC to factory (from within BMC) 5. Changed fan speed to Full Speed 6. Started unRaid 7. Installed IPMI plugin 8. Changed Lower Critical Values: case fans to be at 300/300/300 and the cpu fan at 500/500/500 and set settings to reload on unRaid start 9. Set IPMI plugin to - Case fan thresholds for temp are 35/40 and for rpm 40/100 - CPU fan thresholds for temp are 40/60 and for rpm 31/100 10. Enabled Fan Control Still, full blast :-/ I should have just kept my fingers off of it, instead of trying to adjust more. 11. Repeat the above, plus full power down and mains lead removed. And now, it worked. But only for 2 mins after which it stepped RPM up to full again on fans 1-4. Even if the temp thresholds weren't reached :-( CPU fan is at 1000 which does not correspond to the threshold temp of 40 as it is at 35.

Thanks! I will try out what you advise as soon as I return from work. I can definitely run the commands manually if you want. What are they, please? :-)

So, I am at my wits end here :-( Trying to get this plugin working on 6.4.1 with 4x Noctua PWM case fans (2x 1200RPM and 2x 1500RPM) + 1x Noctua PWM CPU cooler (max 2200RPM) on a SuperMicro X11SSM with support for PWM. I set the SuperMicro fan control at "Standard" in BMC and install the plugin. Configure case fans to react to HDD temp and CPU cooler to react to CPU temp. Configure fan control for case fans to min/max temp of 30/40 on HDD and fan speed to 40%/100% Configure fan control for CPU fan to min/max temp of 30/60 on CPU and fan speed to 40%/100% If I leave it like this, the fans pulse up and down endlessly, throwing hundreds and hundreds of warnings in the event log. I then tried adjusting the lower thresholds as advised earlier in the thread to 300/300/300, the idea being that if the plugin is set for lowest fan speed above this, it will never trigger bios to try and adjust (causing the pulsing) and everything is good. Unfortunately, what happens is that all fans immediately go to full blast. This change seems irreversible, at least through "conventional" ways. Tried disabling plugin, adjusting lower thresholds back to default, uninstalling the plugin, cycling through the modes in the SM IPMI interface. The only thing that reverts it is resetting BMC to factory default. Any advice on what to do would be much appreciated. Thanks in advance!

That sounds quite straightforward - will do that! Thanks :-)