vonangelo

Status update: It seemed like it might've worked, limiting the memory usage of my docker containers. Now the dashboards shows around 68-69% memory usage, which seems more accurate. Thank you for your help, @testdasi!

@testdasi Thank you for your reply! I completely forgot about my foldingathome docker container. So I have Plex and foldingathome. I didn't know that I could limit the ram usage of the docker containers. I will try that 🙂 I've attached the diagnostics zip file in my first post.

Hi there, I've previously experienced my VMs to shut down, due to "Out Of Memory" errors. It's been a little while, but I am curious about why this is happening. My unraid server has 16GB's of RAM. My two VMs has allocated 4GB's of RAM each, so 8GB's in total. I also run a Plex docker container, which doesn't seem to use like any memory. At the time of writing this, the RAM usage it about 96%, according to the Dashboard. I've read that this doesn't have to mean anything, since Linux is just reserving the memory - is this correct? I've installed "Tips and Tweaks" and "Fix Common Problems", to investigate further. It just shows the "Out of memory" error. I havn't troubleshooted this alot, so I don't really know what kind of information you guys need, to help me out. So please let me know, and I'll get that for you. Have a great day - stay safe out there! Best regards, Angelo diagnostics-20200809-1350.zip

To those who are experiencing the black screen issue: I've solved the mystery for my own scenario, and it might help you out. Since this docker containers sets up a VM automatically, it might cause you some issues. For instance, the VM could choose a wrong network bridge - it did in my scenario. And for some reason, changing the GUI settings for the VM broke the VM. The icon for my VM was changed and I was facing the black screen issue. But if I installed the Macinabox container without changing any settings, an error showed saying that it couldn't use the network bridge (br0 in this example) as a network adapter. That got me thinking: could I change the settings in the XML and hopefully not brake the VM? It turned out; yes. I changed the network setting for the VM in the XML file from br0 to br4 (since I use br4 in my case) - and now it's installing again!

Great guide! Although I am having difficulties booting up from Clover. While everything else seems to be working just fine, I am facing this issue when pressing "Enter" in the Clover menu. After pressing the "Enter"-button, the screen turns black. I've then tried different approaches, which didn't solve the issue. I've commented the same scenario in the YouTube comment section, and others are experiencing the same issue. Is it possible that anyone has a clue to what I could've done wrong, or what I could try out? I am new in the unraid world, so excuse me in advance for being kind of a noob.