-
Set parameter for docker container (set buffer pool size for MariaDB)
Not yet.
-
Set parameter for docker container (set buffer pool size for MariaDB)
I installed mariadb and photoprism, and currently tweaking performance because the latency is really high after adding 200k+ photos and videos. Following https://docs.photoprism.app/getting-started/troubleshooting/performance/ I hope to add `--innodb-buffer-pool-size=1G` parameter some where to adjust the buffer pool size. I tried it in both Extra Parameters and Post Arguments, non of them worked. Is there a `docker-compose.yml` for mariadb to update? Or where else can I add the parameter? Thanks! Jason
-
[SOLVED] network unreachable after upgrade to 6.10.2-Resolved / New issue - cache unmountable.
Got it. Alright, rebuilt cache file system as XFS. Thanks for your support.
-
[SOLVED] network unreachable after upgrade to 6.10.2-Resolved / New issue - cache unmountable.
Ah... bonkers. All docker apps/libraries are running in cache drive. I may have lost all the appconfig. What caused the drive to be unmountable? is this the data corruption that happened? I thought the update blocked the NIC, and data corruption wouldn't have occured.
-
[SOLVED] network unreachable after upgrade to 6.10.2-Resolved / New issue - cache unmountable.
Now I'm seeing my cache unmountable. (attaching diags). I have not restarted the system. "Unmountable: Wrong or no file sysem" ("system" misspelled BTW). tower-diagnostics-20220611-2205.zip
-
[SOLVED] network unreachable after upgrade to 6.10.2-Resolved / New issue - cache unmountable.
Thank you for all the support! Best of luck finding the fix!
-
[SOLVED] network unreachable after upgrade to 6.10.2-Resolved / New issue - cache unmountable.
Cache was mounting before updating - correct. I was doing a big cache flush (600GB or so) before the reboot following the update. Diags are unfortunately not from the first boot. I rebooted it several times wondering why I couldn't connect to the webGUI.
-
[SOLVED] network unreachable after upgrade to 6.10.2-Resolved / New issue - cache unmountable.
It was 6.9.x Sorry I don't remember the minor version. Cache was not unmountable. Restarted the server after the update as usual.
-
[SOLVED] network unreachable after upgrade to 6.10.2-Resolved / New issue - cache unmountable.
Disabled VT-d, and webGUI is back! Thanks!
-
[SOLVED] network unreachable after upgrade to 6.10.2-Resolved / New issue - cache unmountable.
Thanks for the prompt reply! Yes. It is an HP. Is the next step to create the empty file config/modprobe.d/tg3.conf ? Is there anyway to verify tg3 will work with the build? (I don't want to wait till data corruption happens. Edit: Read through this post, and seems like the recommendation for now is to disable VT-d.
-
-
[SOLVED] network unreachable after upgrade to 6.10.2-Resolved / New issue - cache unmountable.
I have not experienced this before in the past (10 years?) with unraid. Console boots and it looks normal (see attached), but I can't get to the web gui. The IP address (192.168.1.3) is unreachable via ping. Other iLO IP address is fine, indicating NIC is ok. Checked clients via router, should not have ip conflict. How should I diagnose further? (diagnostics attached) tower-diagnostics-20220608-1442.zip
liujason
Members
-
Joined
-
Last visited