ssnow

tried upgrading to 6.12.2 and still get the same issue attached diagnostics below. tried replacing interface configuration with working from 6.11.5 in XML, but it would be reverted upon save. is this just me? unraid-diagnostics-20230704-1038.zip

Ok. Did some comparisons between working (6.11.5) and non-working (6.12.1) .xml for the VM and found the below discrepancy for interface config. Does a target need to be specified for the interface to come up? Working in 6.11.5 <interface type='bridge'> <mac address='52:54:00:fb:e1:91'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </interface> Not working in 6.12.1 <interface type='bridge'> <mac address='52:54:00:fb:e1:91'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </interface>

Hello! I've tried upgrading from 6.11.5 to 6.12.0 and 6.12.1 but have downgraded due to my Home Assistant VM not getting an IP. In 6.12.0, the VM tab would stay blank. In 6.12.1, I can get to the VM configuration but the same settings seem to result in the VM not having network connectivity. I confirmed the MAC is correct to receive the correct IP from the DHCP reservation on my router. I'm not sure if there is some other setting needed to get this working. Any help appreciated! unraid-diagnostics-20230622-1735.zip

Ok. Thanks. I've increased the limit for that container. Will see if any issues are encountered.

Thanks for the feedback. All containers and VMs have limited RAM. Does this error relate to a container running out of memory or the host running out of memory?

also occurred on Jun 19 at 07:32:09 server time.

Looks to have occurred on Jun 19 at 00:11:34 server time. UID 1035 is for Bazarr. I have limited memory for that container to 750 MB. Dont have anything from the time that shows the container doing something? Am I missing something or is there something I could do better? unraid-diagnostics-20230620-1111.zip

Thank you!

I had never done a force scan. Just ran it and no change. No major rush. Just have a flashing drive on the dashboard. Have fun!

Enjoying the plugin! One thing I'm seeing is critical temp threshold is not reflecting what is configured per drive. I have my NVMe SSDs configured at a drive level for warning at 70* and critical at 80*. The Samsung SSDs are configured at a drive level for warning at 55* and critical at 65*. Looks like warning is pulled correctly, but critical is the global config. Unraid version: 6.11.5 Plugin version: 2023.04.17

I know this is old and not sure if you got it fixed, but noticed your static IP assignment for VLAN 5 is invalid. Can't use .0 for a host in a /24 subnet.