x3rt

Still having this issue with 7.2.3 when using the Black theme (or the light theme with the nav menu at the top) I've tried removing Unraid Connect and rebooting but the issue persisted. Currently upgrading to 7.2.6 and hoping that it'll be fixed. --header-text-primary is unset Update: Issue persists after updating to 7.2.6

Hello, I just purchased a Basic License not realizing I was above the 6 devices limit. I do not see a way to upgrade my license without first redeeming it. I am lost and just wish to upgrade my license to the Plus tier so that I can redeem it.

Alright. Guess I won't cache backups in the future. It's 65% done after 26h I'm still not clear on the 6.12 caching options. For example array->cache seems scary and unsafe and should never be done? Would that data be stuck on the cache? Is it always unprotected? Why would you do such a thing? Sorry if I'm being dumb.

Not sure what else I can provide really

I managed to upload the in-progress diagnostic that failed. Not sure how complete/incomplete it is or if it's even anonymized properly mercury-diagnostics-20230721-1039-self (1).zip

I legitimately cannot generate diagnostic logs as it is trying to `sed` every single file in the backup. Using the CLI command does nothing as /boot/logs remain empty root@Mercury:~# diagnostics Starting diagnostics collection... I can try to manually zip up what it generated previously when I was using the WebGUI up until my browser window crashed

Also just an update on the diagnostics... It has been generating for 30 minutes and it is starting to slow down my entire browser and I'm not sure what to do about that or whether I can safely close that browser window until it is done. The diagnostic browser window is currently using 5 GB of RAM & 50% of my CPU Update: Browser ran out of memory after generating Diagnostics for 50 minutes

Hello, I'm running Unraid v6.12.3. With valid Parity Intel Xeon E5-2470 v2 @ 2.40GHz | 10 Core 20 Thread 48 GiB DDR3 Multi-bit ECC I set up an NVMe drive yesterday to use as a cache pool. It has since filled up with 612GB of windows system backups. I had the mover scheduled for 4:30am and it is now nearly 11am. It is still at 612GB, and looking at my array activity; every 3 - 5 seconds it has less than a MB of activity. I even tried using Turbo Write with absolutely no difference. I'm considering just abandoning using cache but I would still need to actually have mover move the files at least this once. I have taken down all docker containers so the files aren't in use. This would take over 2 months to move... htop shows barely any cpu usage. With a normal file transfer to my Array it goes to about 150MB/s, but less than a MB every few seconds with mover is unusable. I'm at a loss. Also I've been waiting for the diagnostics to generate for 20 minutes I'll attach them once they generate.