BoKKeR

Hopefully this helps someone in the future, I have been facing this error: operation failed: unable to find any master var store for loader /etc/libvirt/qemu/nvram/1b777903-7a8f-451f-95cd-eac2f843354d_VARS-pure-efi.fd I checked in /etc/libvirt/qemu/nvram and the file was not created The solution was the following, the nvram path in macinabox docker container, hidden paths, has been set to READ ONLY, I changed it to read and write. Unfortunately I had to delete the vm to be able to re-run the docker and then it created the nvram file, but if you want to, you can probably just run the missing command manually, which generates the file https://github.com/SpaceinvaderOne/Macinabox/blob/d2b961f831cf10523bcc7cb66918b42b837b960e/Macinabox/run/unraid.sh#L317

It was because I was sharing my nvidia gpu with other containers

To disable the vm service using the dhcp and tftp port run the following and reboot virsh net-autostart --disable default For those of you who dont have the right ip under interface, I solved this by changing the network adapter from bridge to host for this docker container!

This window vm is crashing my server upon starting it passed in GPU passed in drive, and a vdisk on a cache drive. 2-4 cores, (min 4 cores free for unraid) upon starting the vm it crashes the server web-ui wont load anymore forced to reboot over ssh. Running 7.2.2 but I doubt that its caused by the update. unraid-diagnostics-20260116-0906.zip

Thanks that solved it, works also on 7.0.1 seems like.

I am posting diagnostic s before and after update to rc, the update seems to have not fixed the issue. unraid-diagnostics-20250425-1039.zip unraid-diagnostics-20250425-1105.zip

Thanks thats good to know, will just wait it out

--------Nothing to do, Nvidia Driver v575.51.02 already downloaded!--------- ------------------------------Verifying CHECKSUM!------------------------------ ----------------------------------CHECKSUM OK!--------------------------------- root@unraid:~# nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. root@unraid:~# sudo modprobe nvidia modprobe: ERROR: could not insert 'nvidia': No such devic running with a RTX3070. This started happening after upgrade to 7.0.0, any ideas?

Has this been removed? I cant find it in the app browser

Might be a little bit off topic, I noticed that many might be using this iscsi target for kubernetes, with some users naming their targets as k8s. Could anyone share their yaml setup? I have been looking at democratic-csi and as far I understand I would have to use node-manual driver. This might not create new targets automatically as I understand. Great plugin btw!

I have checked on it but since I am using typescript and this is a backend+frontend project it quite difficult to build in a way that both components work In the meanwhile could you remove dangling images, I usually run this command, read in the console what it doas: docker system prune -a WARNING! This will remove: - all stopped containers - all networks not used by at least one container - all images without at least one container associated to them - all build cache

https://discord.gg/GjAyxvuyEx Feel free to join my discord for direct support.

@StylishQuoter the logs say that it’s because of the self signed certificate. I haven’t tested that functionality. Can you tell me how you set it up? Self signed cert only for an ip. What’s the use case?

@PilaScat increase MQTTRefreshRate=240 and enable logs LOG_LEVEL=debug

@the_lucifer try setting LOG_LEVEL to debug @ABEIDO it’s currently running in dev mode, it’s something I totally forgot about. Today I managed to build the files and rewrite the dockerfile. Yet Somehow the backend did not package properly. Once I figure it out the size will be around 370mb

I have pushed a new update to the 6.12 tag with better fetching and error handling, and have started looking into 7.0.0 which seems to work mostly out of the box on first tests. I also fixed the missing mqttDisabledJson error @Ludditus and I will look into the server naming @DeekB To enable more logging use LOG_LEVEL=debug

Havent had time to look into unraid 7.0.0 yet, I am having some issues rewriting the existing code base to be testable, and I am not happy with how much the container calls the unraid UI, would like to focus on testability and adding exponential backoff for fetching the UI. I will hopefully do some of the work this weekend if nothing else happens. As said before, its a new codebase for me also and I am discovering things as I go It requires quite a lot of free time to wrap my head around the code base thats why I have been more absent than usual from this project. Coupled with real life responsibilities. Hopefully we will get to a stable release cycle There is a branch I am currently working on which would require testing: 6.12-async docker tag can be pulled

What is the error? Describe your setup

I tested it on my test VM and it works on 6.12.11, the only thing that is broken is that the version does not report properly. Otherwise stopping array, start/stop containers and vm-s are tested. @skankThe error you are getting might be related to the service overloading your server and your server returning a 503. I have plans on adding a backoff strategy in case the requests start failing but I havent had time to do it yet...

I havent really had time to update it for 6.12.11 yet

Running into this intermittent issue. The vm works initially, then when I stop it, start it a few times. I stumble upon the following error. One would think its space related, but I can create files in the folder where its trying to write. There is plenty of space, removing the log file does not solve the problem. There is plenty of space left on all shares. What really solves the problem is a full reboot. unraid-diagnostics-20240630-2149.zip

I quickly added the home assistant repo functionality. So far the build is only for x86-64. It should work if you add the repository: https://github.com/BoKKeR/unraidapi-re More info in the readme. I have also enabled issues on the repo. Please open issues there.

Its in the first post in this thread, and in the Github readme. I will add it to the template and the webpage

@emilgil env variable in the template. 20 000 should be 20 seconds Also you are running the tag 6.11 with unraid 6.12. They have to match