Hey there, first off thanks for the awesome tutorial. I did this about 2 months ago and up to about a week ago it ran great. Suddenly it wont boot and I’m getting the following window suggesting the OS isn’t loading right with the Motherboard option I have selected?
Here are my settings for the VM in unraid:
Its all paired with Letsencrypt for my reverse proxy and a number of other VMs/Dockers on the unRaid Host
Additionally, when using Node Red inside the docker its always had connection issues. It says its not connected but everything appears to work just fine.
Not really, I noticed the issue because I went to move the VDisk location onto the cache drive from the designated SSD I use and it wouldn’t boot. I moved it back to the designated SSD and maintained proper directories to it within the VM template and it still wouldn’t boot. I’m unsure if it was working just prior to that however. I do know it was working the night prior, but I forgot to verify it before I made the changes that morning. Judging by that popup I guess that the OS isn’t launching appropriately, the only time I’ve seen the VM like that is with OS issues or with Windows if I don’t have the right BIOS selected when making the VM. So honestly, I cannot fathom what would have made it act this way.
Yes I did. I’m using the VM backup script plugin. I actually tried to restore from a three day old file when I KNOW that it worked and it still didn’t work after I started it back up. Tried pulling the VM Template settings in addition to the VDisk itself still to no avail.
So I was able to re-create the VM from scratch using the existing disk, of course there’s some issues with Zigbee Devices I have been triggering manually, however for the most part everything is working well. It looks like the source of the problem was editing the VM template. I replicated the issue by changing names and directories again and it broke the VM. However, once again making a new template resolved the issue. I’m not sure why it would behave like that but I wanted to make sure that it was noted for anyone else who has troubles with it in the future. I will update this post if I notice any further issues down the line/as I reconnect to devices.
Cheers
I once had two unraid servers going and when I knew some work was going to be done in the basement which required the power to be off for a while, I copied the HA qcow2 to the second server and attached it to a new VM instance, so that process came in handy to keep everything else running as expected.
I’ve also had a windows VM go bad after messing with pci-e passthrough and was able to fix it by re-creating a new instance as well. I ended up converting that back to a physical disk. No expert here, but unraid can be fun!
I am currently using the beta 4.6 qcow2 file (for about 2 weeks) I haven’t had an issue so far. I allocated more space through the unraid UI instead of using the console.
Hey All, how are you doing remote access into your hassio VMs? I used to do just the standard duckdns addon from within the VM but i’m toying with the idea of more SSL based access to other parts of my server (hoping to use multiple duckdns URLS).
I’d previously tried this as second reverse proxy on unraid but ran into errors with doubling up my certificates on the same external IP. A while back I found good instructions specifically for passing though to a hassio VM but now it eludes me.
Are we just following spaceinvader’s general video for reverse proxy?
can someone point me to the benefits of running on a VM over a docker. I get that you don’t get the supervisor, but are the actual limitations on what you can do with Home Assistant?
No limitations. If you run the Home Assistant container from the Unraid App store (not the supervisor container…that’s a mess) you have a nice, fast instance of Home Assistant Core and you can use the rest of the UnRaid app store as your “addon store”.
