[[Plugin] IPMI for unRAID 6.1+]

oh well...

great ..but don't work for me.

 

great work..

[CPU freq not stepping down]

In KVM mode, there might be a cpu scaling driver issue with certain hardware combinations.  One of those drivers is called Intel-Pstate.  This is the chosen driver if your Intel cpu is Sandy Bridge (2011) or newer.  On my Haswell-class cpu (i7-4771) the Intel-Pstate driver is too sensitive and seems to keep the cpu frequency near the max frequency even when idle but occasionally it does scale the frequency down.

 

You can disable the Intel-Pstate driver by editing your /boot/syslinux/syslinux.cfg and adding a intel_pstate=disable parameter to the append line below:

 

...

label unRAID OS

  menu default

  kernel /bzimage

  append intel_pstate=disable initrd=/bzroot

...

 

 

Save the file, stop the array and reboot unRAID.  Doing this on my Haswell machine caused it to use the acpi-cpufreq scaling driver instead of the intel_pstate one.  It scales the frequency down like a rockstar now!  Usually keeps it around 800MHz - 1000MHz during idle now.

 

On the flip side, my other test machine, a year older Intel cpu (i5-3470) was able to scale down to 1600MHz (minimum) pretty consistently when using the intel_pstate driver... but when I disabled intel_pstate then there wasn't a scaling driver available.  For some reason the acpi-cpufreq driver wasn't compatible with this cpu.  Your mileage may very.

 

Give this a try and let me know if it helps you.  Either way, if it helped or not, let me know which cpu you tried with this command:

grep -m 1 'model name' < /proc/cpuinfo

 

Hi eschultz,

Is working for me  ...

 

 

CPU on the server is.. ((Intel® Xeon® CPU E3-1270 v3 @ 3.50GHz))

 

The cpu was always around  (3500  3700MHz all the time)

now with this,

is all the way down to 800MHz and the load is 50-54 watts

Is all good!! 8)

 

Mmm  let see what happens when the server is busy?

 

Thanks you, eschultz

                 

/hellboy

[unraid-tunables-tester.sh - A New Utility to Optimize unRAID md_* Tunables]

Hey Hellboy,

 

I'm not sure, but probably it is safe.

 

Primarily the tester is just running a parity check from the command line, so that should be safe regardless of what version is running.

 

The memory parameters that are being adjusted between runs simply affect how much memory is allocated to the process, and should be okay to tweak unless Tom has made changes to these tunables.  In fact, with v6 being 64 bit, you may be able to push these numbers much higher than ever before.  Worst case, you're still just running a non-correcting parity check, so if something happens your data shouldn't be modified. 

 

All that said, let me be clear, I am still on v5.  I only have my one production box, and I don't run beta software on it.  I have not tested this tool on v6.anything, though I think other users in here have done so.

 

And since you are asking if this is safe to run on 6b10a, my gut is telling me you are running beta on a production box with data you actually care about, something I don't advise, and in that case I really wouldn't advise running this tool either.

 

If you end up running it, be sure to share your results!

 

-Paul

 

Ok...

This what i got......

TunablesReport1.txt

[unraid-tunables-tester.sh - A New Utility to Optimize unRAID md_* Tunables]

Hey Hellboy,

 

I'm not sure, but probably it is safe.

 

Primarily the tester is just running a parity check from the command line, so that should be safe regardless of what version is running.

 

The memory parameters that are being adjusted between runs simply affect how much memory is allocated to the process, and should be okay to tweak unless Tom has made changes to these tunables.  In fact, with v6 being 64 bit, you may be able to push these numbers much higher than ever before.  Worst case, you're still just running a non-correcting parity check, so if something happens your data shouldn't be modified. 

 

All that said, let me be clear, I am still on v5.  I only have my one production box, and I don't run beta software on it.  I have not tested this tool on v6.anything, though I think other users in here have done so.

 

And since you are asking if this is safe to run on 6b10a, my gut is telling me you are running beta on a production box with data you actually care about, something I don't advise, and in that case I really wouldn't advise running this tool either.

 

If you end up running it, be sure to share your results!

 

-Paul

 

I will let you know

 

Thanks..//

[unraid-tunables-tester.sh - A New Utility to Optimize unRAID md_* Tunables]

Hi  Pauven,

 

let me get in here and ask.... 

 

It is safe to run this script on unRAIDServer-6.0-beta10a-x86_64..?

 

Thanks//

[Show me your builds!]

ok here we go..