RobJ

I'm not an expert in this area, but wanted to comment - a fan at 1100rpm should not be making any noise. And a fan at 1100rpm *may* not be moving enough air to be worth it. It's my understanding that rpm's less than 2000 are essentially silent, unless it's a very cheap or broken fan. I'd check that fan for damage, or stuff on the blades. Or the 1100rpm number is incorrect.

You may have to do some research yourself. I found a manual online for your board, but it didn't show anything but AMD K8 in your BIOS (make sure it's enabled). So the module k8temp might help provide more sensors, but probably not fan control.

The lm-sensors site is down, has been for months, and there's no word on what the problem is, or if it's returning. So it's not possible currently to be up to date with the latest sensors-detect script. There does not appear to be any other source yet. It used to be updated fairly regularly. I don't know if the one included with System Temp is the latest available, so it's possible there's a newer one out there somewhere, that might better support your board.

So I tried cpufreq-info -d, and no output at all. Tried cpufreq-info -o, and the only output was the header line, nothing below. Then I tried modprobe powernow_k8, again no output, BUT ... the other commands then showed - And on the Dashboard, the CPU is stepping up and down! Wow! So simple! I know I used to see it stepping down before, so I'll report it as a Defect. I do hope you add the driver, but if not, I'll add it myself in go. Once the driver was in, the latency number became far more realistic, currently 109us, was 4294.55ms! cpufreq-info is reporting one more governor than you have, don't know if you want to deal with it.

Nice work! The Tips and Tweaks wiki hasn't been keeping up with the plugin! My AMD appears to be using a different governor, 'Driver' and 'Governor' are blank. Here's a few lines from my syslog, let me know what else you want. The words performance, conservative, powersave, or demand do not occur (not in related lines anyway). In the past, I thought I used to see more conventional governor lines, with those options listed. But v6 *may* have changed it for my CPU. Edit: did some research, my CPU may need powernow_k8 loaded, and it's not. It's remotely possible that I never turned Cool&Quiet on in my BIOS, but I know I used to see the CPU drop to 1000MHz, now it's stuck at 2411MHz. I checked lsmod, and acpi_cpufreq is listed! It's not in my syslog. The plot thickens... I'm sure you haven't finished, but "Max Freq. Latency" needs explanation, help. The unit is "ms", a time duration, but the word 'Freq' implies "things per time unit", not sure what "Max Freq. Latency" actually means. If it means 'maximum latency', then I assume you are selecting the highest of a number of readings? If so, then the average latency might also be useful. Another similar tweakable option you may be interested in is the "io scheduler". There's been considerable discussion of it in the past here. There have been requests before about the 'turbo write' option (which can dramatically speed writes to the array), requests for an ability to schedule it for certain times of the day. Since you've added scheduling, you might be interested in using it again for 'turbo write'? (sorry, my writing is often awkward, wish I could do better)

Have you seen the following? Any thoughts? Why only Docker containers and not dockerfiles?

Yep, the wiki was out of date, hasn't kept up with the plugin. I basically lifted your instructions and plugged them into a new v6 section at the top. Thank you for that!

I've created a wiki page to help with this -> Files on v6 boot drive (it's brand new, probably has mistakes) It includes a list of files and folders from the boot drive, and what they're for. I've added notes and warnings based on comments from this thread, so thank you all! I've now added a new section called Starting Over, designed to help users wanting to 'start over', restart their unRAID server afresh but not necessarily lose all assignments or settings. I'd really appreciate anyone willing to take the time to proofread it, tell me what's missing or needs correction, especially because there's quite a bit of detail and a large part (files and folders) must be 100% typo-free.

Nicely done. Can I propose two honorable additions? 1. '/syslinux/sylinux.cfg-' restores the "factory settings", is invoked from the GUI when Default is clicked under Syslinux Configuration. Do not edit this file manually. 2. '/config/plugins-error' this folder holds the plugins (.plg file) which failed to install on system start up. The original .plg file is moved to this folder and won't be installed upon a next system startup. Really appreciate it, thank you! I was hoping for some additions, and some proofing! I've now added these, and a new section called Starting Over, designed to help users wanting to 'start over', restart their unRAID server afresh but not necessarily lose all assignments or settings. I'd really appreciate anyone willing to take the time to proofread it, tell me what's missing or needs correction, especially because there's quite a bit of detail and a large part (files and folders) must be 100% typo-free.

I'll have to leave it to someone else. By the way, you did install Perl first from the NerdPack? Click the Help button. Oops, just discovered that the Help doesn't mention Perl, not sure why. Perhaps it installs it in the background? You probably need bonienl's help.

This may not be the reason for your case - On my system, there's a delay in the temp display that seems proportionate, or at least related, to the Display Setting Page update frequency. If you have it set to Real-time, the temps appear almost immediately. If set to Regular, they typically appear on the next 10 second cycle. If set to Slow, it takes much longer. And if set to Disabled, they may never show up, or it will be a long time. I don't know the reason for this.

You didn't actually say what's not working. It all looks fine, from what I can see. What temps are you seeing on the Main page?

I've created a wiki page to help with this -> Files on v6 boot drive (it's brand new, *might* have mistakes) But don't use it without the comments and warnings from the thread trurl links to. I probably should add the info and warnings to the wiki.

Great feedback, just what we were looking for. As Dan said and you've emphasized, make changes slowly, one at a time, and test, verify that it helps. Sounds like the combination of settings that may help one user may not be right for another user. So users may want to test many combinations.

I haven't checked if it's commonly configurable, but I've noticed in other's syslogs that they commonly renew in half the the time they request. Do you find yours renew every 15 days? Agreed, and for the most part that's what I do. But I only have a few I can set to static, and only one with a syslog that gets littered!

I had tried that, to see if it would make a difference, no change. I just started Firefox (no reboot), pulled up the Main page, checked the log and noticed syslog entries for 'Fix Common Problems' at 4:40am. Started the plugin and for the first time it says "No errors found" and "No Warnings found", plus it says "Time of last scan: Wednesday May 25th 4:40 AM", which was the Daily scan this morning and not a scan of this instant! I had been assuming it always does a scan when I start the plugin, that's what it used to do, and it doesn't look different. But now I've just discovered there's a new Rescan button, never saw it before! So I guess it has not been re-scanning, just showing the result of the last scan. I must have missed that change. Would it be more intuitive if it didn't show the last scan, just showed the settings and a big <Scan> button, which you could click when ready, and click again after changing settings.

Did you rescan? Other than that I cannot replicate. All its doing is checking to see if dynamix thinks there's an update available Also, to downgrade it to a warning: http://lime-technology.com/forum/index.php?topic=48972.msg470697#msg470697 I had rescanned several times, but tried once more, went back to the Main page, then back to the plugin, and no change. Went back to the Main page, spun up all drives for a more complete scan, but again no change. Rebooted and this time the error was gone. So it *appeared* to be fixed after reboot. BUT ... I decided to click the 'Ignore' button for the other 2 update warnings, and they appear to work, except they don't stick, nothing changes, they aren't apparently being ignored, and the Ignore button is still there. So I'm wondering if this and the first issue are another case of client-side weirdness we occasionally have with the webGui, where setting changes don't stick. I use Firefox. I used to have that issue with slot count changes, and would have to switch to Chrome to make slot changes that would stay changed. Others have reported the opposite, wouldn't stick in Chrome, but worked in Firefox. So I just tried Chrome, and it's behaving the same way. I click an Ignore button, get the confirmation dialog box, click the OK button, click OK a second time, then it reverts to the same screen with both Ignore buttons. Noticed that 'Fix Common Problems' does a scan on boot, with syslog entries. There are no syslog entries since boot though, is that possibly an indication that the scan wasn't really running, since this last boot? It supposedly did scans on both Firefox and Chrome. And it has been reporting the adblocker.

Sorry, another false positive on my system, no idea why since it doesn't seem possible it could be connected in any way to User Shares, and others aren't reporting it. Last night, I received a notification (an 'Error') that 'Fix Common Problems' was out of date, marked as an 'Error' which seemed a little excessive. I have the update checks for it marked to be 'Ignored'. I also received a notification of "Version update 2016.05.23c" for 'Fix Common Problems', no problem with that as I was currently on 2016.05.22. So after reading the related posts this morning, I updated to the latest, 2016.05.23c and retested and it still reports the error, that I need to update. I've retried 3 times, no way to update further, and it still insists it's not up to date, see attached screens. Minor suggestion, add the version info next to the plugin title on top, perhaps in parens.

Been different all my life, why change! Anyway, it works fine now, on my differentexceptional system.

Troubleshooting and tweaking tools Here are a few tools to help you, when something isn't working correctly on your unRAID server. We assume you are already aware of the Diagnostics collection and download tool! (Tools -> Diagnostics) Fix Common Problems is a plugin with a suite of tests and detections, to make sure your unRAID server is configured correctly. It checks for common mistakes and defects. And more checks keep being added. You may be surprised by the things it finds. The Fix Common Problems plugin has a Troubleshooting mode, for those times the system is crashing or locking up at random times, with no way to save the diagnostics. It periodically runs diagnostics and other tests, and maintains a live tail of the syslog to the flash drive, until crash or reboot. PLEASE use this if your system is crashing unexpectedly! Then grab the saved diagnostics and syslog.txt (from the live tail) and post them. The Tips and Tweaks wiki page is a collection of the various troubleshooting and performance tips, tweaks, and fixes scattered in multiple places around the forum. It's new, may change often as new tips are found and old ones are no longer needed or are incorporated into new unRAID releases. Please check it, especially if you are having issues with your system, and provide feedback here about what works for you, and what doesn't. We're hoping the results and your feedback may help LimeTech. Plus, we hope to add many more tips and tricks to the page, as users suggest them. The Tips and Tweaks plugin is a companion tool for interactively implementing some of the tips and tweaks from the Tips and Tweaks wiki page, and a few that haven't made it to the wiki yet. Should make it easier to try some of them out. Again, we want feedback on what helps and what doesn't.

In part, I do the same, but I *also* (where possible) set them as static on the item itself. In the router, I set a range of known addresses from my list for everything I know of, and let anything else (like SMART phones of relatives) get addresses above those. That takes care of all IP reservations. But then on primary machines like my desktop and unRAID server, I set them to not use DHCP, and I assign them the IP from that same list. Why? Mostly because it seems wasteful to keep asking for the same thing, and I hate waste. It's fixing what isn't broken. I know it's safely reserved on the router, and there's no wasted requests for what it knows it's going to use anyway. But for unRAID, I have a couple of other reasons. The first is not major, but a nuisance when examining syslogs. Every renewal puts a bunch of stuff in the syslog, more if there's bridging, even more if there's Dockers. And if the users' router has a short lease time, then the syslog is full of this stuff, making more to look through, annoying since it seems so unnecessary. In some cases, I've seen lease times of 2 hours, and since most are configured to renew in half the lease time, they had a bunch of IP renewal lines every single hour. I'm not sure why we can't at least recommend monthly IP lease renewals, or every 2 months so it happens monthly only. The other reason is because I found a problem recently in a users syslog that appeared tied to the first renewal (see this, the DHCP comments). And I believe I saw another user with similar. It looks to me as if something isn't renewing correctly when there's bridging and/or Dockers involved, or some other special circumstance (jumbo frames maybe, not getting set correctly on the renewal?). I fully accept that I may have the wrong diagnosis there, and may be 'jumping the gun' too quickly. If anyone else sees something different, please feel free to say so. But it's clear in that syslog, the issues start with the first renewal, and disappear when the user changed to non-renewing, static assignment. I think Frank's idea of using a high range for 'static' assignments is a good one, a good recommendation. Ensures no conflicts. This troubles me, it's hard for me to believe that decent routers would allow that. That would be an obvious bug. I don't know for sure, but I suspect that the router did not know about the static, so gave .12 to a device, then later the other device turned on and began using .12. There's nothing a router could do about that except log it, as it knows this is coming from the wrong MAC address. But routers can't scream or shout or raise red flags. All it can do is log it, and who reads those! As you said, static assignments should be set in a safe range, unreachable. As to using DHCP because of router replacements, that seems a special circumstance, where users really ought to *know* that a new router may not use the same default subnet. Even if it doesn't occur to them after they install a new router, the first time you turn on your unRAID server and can't find it on the network, the reason for the issue should slap you right then, and you'd slap yourself and get to work fixing it. It seems such an obvious possibility when you set the router up, that you may have to tweak the static assignments. I don't know how we can help if they can't figure that out. Add a FAQ - "I got a new router, didn't touch my unRAID server, why can't I see it on the network any more?" It's almost embarrassing.

Just installed it, and had my first look, great job! I think it's well done, I especially like all the help. A few initial nits and suggestions - * There's a "can can" in the second paragraph * In all unRAID documentation, we're trying to be consistent with the word 'unRAID', and always capitalize it that way, not Unraid, UnRaid, unRaid, etc; it's Tom's wish * Suggestion: in the help, change "Some Recommendations:" to "Some General Recommendations:", just to differentiate it better from the specific help entries below it * Suggestion: add a link to the Tips and Tweaks wiki page, for possibly more info * Suggestion: add a link with comments to the Tips and Tweaks feedback page. We would really like to hear back on what works, what works great, and what doesn't seem to help, or even hurts * Suggestion: In the ring buffer help (TX and RX), it says "The default value is recommended". If they make a change, and come back a month later, they may not know what the default is. Suggest changing it to "The default value of 256 is recommended". Items for discussion - * "Don't use Jumbo Frames" - I'm uncomfortable with such a blanket statement (even knowing it's based on what I wrote!). We don't yet know if it's everyone using jumbo frames or not, or if the issue is only with certain NIC's/switches/etc. I think I would prefer something like "For now, avoid Jumbo Frames". I've adjusted the notes with that tip. * Static IP - I'll respond when I can about it, to the valid points others have made, and why I've begun favoring static IP over DHCP (a problem I saw). I do realize I may be going too far with it. * dirty cache settings - I think you have a good start to the Help needed for write caching, and a pointer to the guide (good idea!). I think much more help would still be useful though. I'd like it to be clear that raising the numbers may not help them in some situations, lowering them may be better! In particular, decreasing them to single digits may be best for situations with streaming issues, like stuttering and pauses. Users forget that these numbers were devised in the 32 bit days, and only applied to available RAM within lowmem, the first gigabyte ONLY! That could be only 300MB to 500MB! And it all ran fine in our v4 and v5 days! When we changed to 64 bit in v6, available RAM exploded from 300MB to 7GB, 15GB, and 31GB! So that 10% ratio might go from 30MB to 3GB, an ENORMOUS increase. Which is why I've seen one recommendation to change the numbers to vm.dirty_background_ratio=2 and vm.dirty_ratio=3. A low vm.dirty_background_ratio means it starts dumping the write cache sooner, and therefore less likely to fill it up and cause pauses. * num_stripes=8192 - this is my only disappointment! I was especially wanting this for the beta thread, because it's probably the single most important workaround just now, for users with VM's and systems hanging when they try large transfers. Eric seems fairly confident that this fixes it. Would it be possible to put the highest priority on adding this tweak? I've added the plugin to the Tips and Tweaks wiki page, let me know if there's anything else you would want it to say (or change it yourself).

Decided to try the latest, looks good, one issue though - reports "Error: Array is not started" but it IS started. Want my diagnostics? It also popped up with a notice about an adblocker detected, so I checked and yes, uBlock Origin was running. However I've never had any display problems, and when I checked uBlock Origin, it indicated nothing blocked on the page, and I never changed any settings. So I guess not every adblocker is a problem. I'll leave it as is, until there IS a problem. (I'm not reporting it as an issue, just a behavioral variation)

That first 5 step procedure is obsolete, only for unRAID v4 and earlier. The latter procedure is correct for unRAID v6.

I see good things happening here! Are we ready to go live? I'd like to add the plugin to the wiki page, when you feel it's ready. In order to do that though, you'll need to set up a plugin support thread for it, that I can link to. Then I'd like to go live with this, promote it in the beta thread and possibly elsewhere. I'd like to introduce these as a set of new Troubleshooting tools, "Fix Common Problems" plugin (with the new Troubleshooting mode), "Tips and Tweaks" wiki page, and "Tips and Tweaks" plugin, and strongly recommend everyone try them out, but especially anyone having problems with recent versions. Anyone see a reason why it's too early? I'd hoped for more critiquing of the page. And I'd hoped to add something about write caching, but I'd like more knowledgeable opinions on it. I'm not comfortable yet with how to present the 'dirty' options.