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.
Upgraded yesterday from 6.7.0-rc2 to rc3, went smoothly.
I captured a diagnostics before and after and did a diff compare. No surprises, everything looks as it should so I won't bother attaching.
That's why it's important we report 'what IS working' so that the rc process can move forward.
If the majority of issues are very minor, 'annoyance' presentation layer issues, which @bonienl has been very responsive too, then that's a great sign of forward progress.
Maybe the next rc resolves them all, maybe we get some new ones to discover. That's the fun of the rc process, embrace it 😁
I'm curious too! I'm still impressed you spotted the drive count as the outlier.
I did a test where I removed one unassigned drive, but it had no effect on reducing the number of messages. Maybe I'll get time this weekend and try removing an assigned disk and see what happens 😁
To help further try to isolate this issue, I did the following...
1. Rolled back to 6.6.6 thru the GUI, that worked smoothly. The warning message is not present. I captured a diagnostics file, attached filename ending in ...2022.zip
2. I upgraded to 6.7.0-rc2, that worked smoothly. The warning message has returned. I captured a diagnostics file, attached filename ending in ...2028.zip
Anything jump out in the diff comparison that's of help?
tower-diagnostics-20190129-2022.zip
tower-diagnostics-20190129-2028.zip
I checked the code where those warning messages reference and yeah it looks disk count related @trurl
@bonienl the Dynamix Stats plugin is also showing the error on the Disk Stats page.
Edits: Found in 6.7.0-rc1, rc2, rc3, rc4, rc5
After upgrade I was greeted with this warning message in the GUI.
I removed all plug-ins and it still persisted. I cleared all browser cache and cookies, it still persisted.
Starting array and everything else seems to work fine. Just a visual warning.
Any ideas what else to check?
tower-diagnostics-20190124-1754.zip
tower-diagnostics-20190124-2245.zip
@bonienl I couldn't find this previously reported... Dynamix System Stats very small cosmetic nit I noticed over the years, it's more noticeable now that you've done such a great job polishing the rest of the UI. The vertical align of the Dynamix Stats plug-in.
Thanks! this makes me want to give it another try someday with the usb cable and see if I get results like yours. I've only had luck using NET with the optional remote access add on card Cyberpower offers.
@jonathanm I was able to finally get mine working a year ago using the network snmp after many hours wasted on trying the direct connect usb cable. Is that the same method you're describing?
Ever try the usb cable? Did it work for you?
Great decision to add a UPS!
I also think cyberpower products and their customer support are excellent!
However the apc library in linux and thus included in unraid doesn't marry well to the point of your question. I'd advise you stick to tried and proceed compatibility recommendations from others.