jakeshake

Hello, Thank you for keeping the pace going with this plug-in. I am curious - are you able to output video from a Windows VM using the HDMI or Display Port with the iGPU using this plug-in?

ClamAV detecting a trojan when downloading the config file- anyone else?

Try this: put the usb into your windows/linux box and run the "make bootable" executable on the thumb drive, (there's one for each OS). It will make it bootable, again. Problem solved.

Had the same issue after updating from 6.12 (worked fine) to 6.12.1 on a msi z690 12700k. Went into the bios and manually booted into the usb stick and now it restarts/boots just fine. But something in 6.12.1 is gumming things up; just replicated it in my back-up server going from a working 6.12 to 6.12.1

Maybe this was mentioned and I missed it, but, anyone who comes across this make note of the below: tl;dr: 4 sticks do not work at overclock (XMP) speeds in Alderlake. Run at JDEC speeds for stability. You cannot use 4 sticks of ram, (in my case ddr5) and run them overclocked in the Alderlake, (z690 in my case, pun intended). So, no XMP. Just run at JDEC speeds if you have 4 sticks. I've only applied this hardware to Linux, and Windows 11 may do some voodoo magic that somehow allows this, but I think this is just a major fcuk up by Intel and the board manufacturers for not being crystal clear with their customers.

Changed Status to Closed

Fresh install Home Assistant VM fixes sensor issues on RC5. Probably my error- closing this. Thank you for a wonderful product, Unraid team.

Haven't had much time to diagnose but seeing that RC5 is out now I can confirm there is an issue between HomeAssistant (VM) and the upgrade to Unraid from RC4 and up. This affects sensors beyond Frigate. I will keep digging and post resolutions when able to.

Attempted a fresh install of Unraid 6.11.0-rc4 along with a fresh install of the container Frigate and the VM HomeAssistant (utilizing the Frigate proxy) and the same results- object detection not working as intended. I cannot pinpoint it through the Frigate logs so it may be a communication issue beyond Frigate, maybe into the VM HomeAssistant, (although all other functions in HA are working just fine, MQTT etc.) Sadly nothing suspicious in the logs of either. Slap this together on rc3 and it works just fine. For context here is the hardware/software and setup: Intel 12700 cpu Unraid 6.11.0-rc4 HomeAssistant VM running Frigate proxy Frigate container running in docker Next I'll run this setup on older hardware with the new 6.11.0-rc4 and see if I can reproduce the results and report back.

For example, it appears to work with Jellyfin.

Hello, Thought I might ask opinions here... While I understand there will be errors in most cases; has anyone had luck with overclocking their Unraid Adler Lake box? Even minor bumps and/or just an undervolt to save on electricity? If so can you elaborate? Separately, updated to 6.11 and I see the iGPU is now accessible. Would be nice to hear others experiences with that as well.

Rebooted, still nada. Deleted the Nvidia plug-in & folder, (deleted directly off the USB, not sure if that's appropriate). Powered back on, nothing. Also, now each time I reboot, unraid will only boot from a fresh USB port... Tried using the USB configurator and copy over (a working) config folder from a few weeks ago and still, no dice. If there's no other suggestions based on the diagnostic file, I'll just try a fresh install and redo the array...

itimpi, I did try to manually https://my_ip and no dice. Thank you for your suggestion. Squid, thank you for responding so quick. I'll reboot now and see if the problem persists.

Hello, Firstly, thank you to whomever can assist in bringing back access to the WebGUI. This all started shortly after updating the "MyServers" plugin. (I am not sure if that is the culprit). Access to the WebGUI has disappeared while all other functions still operational. I can log in via terminal, docker apps run fine, VM running fine and connectable, I just cannot connect via browser (I tried chrome, edge, firefox) to the WebGUI. tower-diagnostics-20220222-1105.zip Please see attached diagnostics zip.