Mat W

@FlamongOle - I can verify that my dashboard (and Disk Location settings tab) now work when disks are spun down!! Thank you for all your hard work. As promised, beer money sent.

It's a known issue at this point. If any of the drives are spun down, the dashboard and Disk Location device page will both be blank. If you spin up all drives, they should re-appear. At least that's how it is for myself and 1 or 2 others on this thread.

I should add that my Disk Location settings page goes blank when the dashboard is blank, similar to @SShadow.

Forgot to mention leaving the dashboard up for 5 minutes. I have the dashboard open in a tab at all times in Firefox. I haven't observed any issues with performance.

I am seeing the following in the php log when I brought up the dashboard prior to spinning up all drives. It's the same stack trace every time with nothing else in the log. [08-Jul-2023 07:34:26 America/Denver] PHP Fatal error: Uncaught TypeError: round(): Argument #1 ($num) must be of type int|float, string given in /usr/local/emhttp/plugins/disklocation/pages/devices.php:305 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/devices.php(305): round('*') #1 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(706) : eval()'d code(25): require_once('/usr/local/emht...') #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(706): eval() #3 /usr/local/emhttp/plugins/dynamix/template.php(82): require_once('/usr/local/emht...') #4 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/devices.php on line 305 I have no issue with supplying a diagnostic file if it will help?

I pulled down the C version just in case it worked. No change. I haven't come across any other pages or plugins having issues throughout this process. Again, really appreciate all the effort. Will definitely be "buying you some beer" when this is done!

@FlamongOle - Updated and still nothing on the Dashboard. I repeated the same testing steps as I did before, with the same results. Once the drives are spun up, the dashboard re-appears.

Awesome job on getting this out! Just did the update and, sadly, did not resolve the issue for me. I did the following steps to test... Logged out and back in Verified drives were spun down (all data and parity in fact) Tested in a private window to rule out browser plugins and cookies/cache Lastly, spun up the drives to see if dashboard appears... it did. Let me know what info you need from me to assist further.

I have discovered the offending plugin after combing through most of the plugin threads. There is an issue with the Disk Location plugin that caused the Dashboard to go blank BUT only when 1 or more drives is spun down. Spinning up all drives resolves the issue. This explains why everything would being working and then a drive would spin down and poof! I was going crazy, well, more so than usual.

You have no idea how happy I am to come across your comment!! I have been playing wack-a-mole with plugins for a couple of days now trying to figure out which one was causing the issue. <spins up all drive> Poof! The dashboard reappears. Let me know if you need any info from another system having the issue.

I'll 2nd that!!! Only wish there was a way to disable individual plugins rather than removing them, but I'll take preventing reboots.

Well, the Dashboard disappeared again. Is there a way to "disable" individual plugins to help troubleshoot which one is causing the issue?

So, I decided to put on my big boy pants and try the upgrade again. I did remove the Docker Patch plugin prior to the upgrade this time but otherwise it was the same process. Oh, and I did run the Upgrade Assistant beforehand which showed no conflicts. The upgrade went smoothly, just like last time and so far no issues with a blank dashboard. I guess I'll wait and see what happens.

I went to 6.12.2 from 6.11.5. I did, recently, locate the list of known plugins to cause issues with 6.12.x (6.12.0 release notes) and while I have 3 of the ones on the list, they were all already updates as suggested. I think I'm just going to have to dedicate more time to re-do the upgrade and poke around more and attempt to better troubleshoot the root cause. Was just frustrated that I had resolved the issue yesterday, only to find the dashboard missing again this morning.

Disclaimer: Not truly looking for support, only venting but didn't know where else to put this (beyond reddit). Anyone else having too many issues with 6.12.2 breaking too much to be usable? I hit a "critical mass" point of removing plugin after plugin trying to get the dashboard to reappear that I have to revert back to 6.11.5. I was losing too much functionality to make having a more customizable dashboard worth it. Not to mention than have to fight to get some Docker containers working again after reverting but that's not the point. As someone who has been in playing with tech since the late 90s, I get that community driven applications have their quirks and struggles. But this? This is too much. I could be understanding if I was chasing the latest RC but this is a stable release that has been coming for a while. I fully acknowledge that Limetech doesn't make most/all of the plugins so it's the responsibility of those that created the plugins but too experience and read about so many issues, it kinda falls back on the OS (webUI) changes at some point. Don't get me wrong, I love unRAID and have helped multiple friends setup unRAID servers. I'm not walking away anytime soon, I'm just voicing my disappointment.

I too, use and love this plugin. It makes my docker tab usable honestly. I've got nearly 30 docker containers so without it can be a struggle to quickly find the container I need to work on for whatever reason. If I knew more about webUI coding I'd definitely roll up my shelves and give it ago but alas.... The best I do is offer a case or bottle of someone's favorite beverage as a thank you.

Yup. Mine is showing "not available", as well as my Prometheus. I am very reluctantly going to try changing the DNS server unRAID uses as a test.

The changes look good. Can't reboot my server to verify at the moment but I expect it will resolve the issue. I've done enough "grep" foo to know that escaping "/"s can cause issues. Done it too many times myself when switching between regex syntax and bash syntax.

Thanks for the info. Sorry for the "double" posting. Genuinely, thought I might have been in the wrong place on discord.

I've seen some older posts about this but couldn't see any specific solutions. I'm running a pi-hole and can see that unraid is doing DNS lookups for mothership.unraid.net 2000-2500 times a day, which seems a bit high. I did ping the my-servers-plugins discord but I think that might have been the wrong place as no one really responded to it. How can I reduce the number lookups? unplucky-diagnostics-20221025-1048.zip

Just upgraded to 6.11.0 and I'm seeing the same grep error messages on boot as @GigaTech above. I can provided for h/w details if needed.

You don't tempt me with a good time. lol

Kind of suspected it to be a Linux thing and how it deals with files, just couldn't find a definitive with my google-foo. Appreciate the confirmation!

I prefer CLI vs GUI for basic file management, call me old school. I'm seeing some unexpected behaviour that I'm not 100% is an actual bug. Figured I should post in here before opening one. I'll do my best to explain this clearly but forgive me if I don't... Let me preface this by saying that if I use a GUI file manager (dynamix plugin, MacOS Finder, MacOS Commander One) everything works as expected, the file goes where it should. This only occurs when done from the unRAID CLI. NOTES: The following is all done using /mnt/user/<share> and then verifying where the file goes by looking in /mnt/<cache drive> The following is done on a recently created file (uploaded or manually created) BEFORE Mover runs The following does NOT occur if Mover has already moved the file on share-A from the cache drive to the associated data drive If the 'cp' command is used the file goes where expected given the share settings Config details: share-A is set to "Yes : cache-1" share-B is set to "Prefer : cache-2" Various tests showed that the "Included disk(s):" setting did not affect the behaviour Description: When moving (mv command) a recently created file from share-A to share-B, the file incorrectly gets put on cache-1 in a directory for share-B. Thus Mover, correctly, does not move the file because it is not on the data drive set for share-B. Let me know what additional info is needed. I have attached a copy of the diagnostics just in case. unplucky-diagnostics-20220801-1030.zip

Yeah, this is 100% broken. The USB creator doesn't register any USB drives regardless of USB3 or USB2. Nothing I do can get around this. Sadly the previously created and working USB drive just got corrupted and not my unRAID server is down until I can figure out how to get a new one created which right now isn't looking so good. This is a MASSIVE issue!!!!!!!!!! I'm left without a working server. Unacceptable!