Lev

Have your tried changing md_* tunables in the disk settings? That made a huge improvement for me, as I too was stuck at 40MB/sec regardless of what cards I used until I increased those settings. Here's the thread with more details.

I'd pick the -e board with the Xeon for your use case. In fact for 99% of use cases I can think of the Xeon is the better pick, go with that and don't lose and sleep on it 😀

The root cause was smart-one.cfg and for some reason it had the following two lines that must of been leftover artifacts from the past. smType=" " smPort1="10" Mystery solved. 😀

I'll post details as soon as I find how I resolved this. There was something in my /boot/config/ and after I deleted the file(s) have resolved the warning message and it no longer appears.

Helpful tips @hawihoney, thank you! I would have likely run into some of the same situations you have already, much appreciate the advice.

Typo. I edited the post so as not to cause more confusion. Thank you @trurl

New test conducted. I boot my server using a new installation of UnRAID 6.7.0rc5 on a new USB drive using a trial key. The warning messages do not appear. Knowing that, and knowing that rolling back to 6.6.6 also do not have the warning messages lead me to believe there must be something existing defined in my /boot/config/* files that 6.7.0rc doesn't like and creates that warning message. I'm thinking of doing a diff compare of each of my /boot/config/* files against the clean install but what should I be looking for? What is an example of a 'illegal string offset type' that I can use for reference?

I'll test again with a fresh installation and report back.

I noticed my Dashboard stopped reporting CPU, memory and network usage and it had just been working previously. I found disabling/enabling SMB in the settings was the trigger.

@hawihoney I think I'm going to try this too. how's your setup running these days? any additional advice you'd add?

Cool, thanks for confirming. Closed.

Dynamix color theme is Black. The shadow box windows and confirmation windows do not appear to adhere to the style guide and remain white, some examples are PluginUpdate.png and UpdateConfirmation.png On the other hand, some window boxes seem to have a light shade of gray, see SystemInfo.png I wasn't sure the right place to report this one @bonienl. If this is a feature request, feel free to move it.

I guess I did do it right, just it didn't resolve suppressing the warning messages. Just confirmed by testing rc5 @bonienl. If you submit anymore pull requests, I'll give it another test.

I copied the changes, but not sure how to reload emhttp. I tried the command "/etc/rc.d/rc.nginx restart" which I think is correct but the warning messages still persist. Did I do it right?

@bonienl If I copy your changes in pull request #463 is that the correction you made? I have some time today so thought I could give it a test and give you some quick feedback.