-
-
Notifications
You must be signed in to change notification settings - Fork 992
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HomeAssistant OS on Synology VM error at first start #3641
Comments
Hello, |
Hello, |
Excause my bad english - Do you set all User-Rights in the Synology correctly for the VM? Give your VM more Space (80 GB) for HA , 2 Core, 2 GB RAM, For me it was easy to install with help from this site: https://home-assistant-blog.de/homeassistant-synology-installieren/ Maybe it helps - if you not understand use the translator.. good luck |
Hello, Thanks for your return. I check all the network configuration from my NETGEAR router and I don't see anything wierd and my HomeAssistant conect to internet through it now without issue. So I don't understand why it didn't manage to connect for the update of HA core at the first start. Regarding your questions, yes I can connect to the Terminal through the VM without issue. About the space available now everything is installed and running it only take 6Go of the 32Go available for this VM. I also try to install it on a 100GO VM without succes at first (same issue at HA core update) so I don't think this was a problem of space available. Until I discover what was the blocking point at the origin, I'm afraid I will have the same problem next time HAOS need to update the core as the Synology NAS and the VM are back on my home network on the NETGEAR router. |
well, maybe a netgear own special problem? But there I'm out. ;-) Make allways enought Backups - you can restore also over the Terminal in the VM if needed, but normaly there are no Problems (just the Problems what comes with the Updates from the Updates ;-) )... The Diskspace for HA (if I understand you right) you can only change in the VM when HA is OFF I also starts with 30 GB but after 4 Month I have to change the Space to 80 because the VM was nearly full. All Backups also use this space - so if you have 5 Backups you need ~ 10-12 GB after some Times. Sometimes it is helpfull to restart the complete SYN - ah - once - .. If you have a point in your netgear to set for the IP of your Synology to static and that the NAS can open nessesary Ports by itself maybe this you can try to find out when you have Problems. Anyway - when it runs now - have fun and success |
Hello, The errors looks to be cause by network communication issues. Not only from VM to Internet but also inside, I mean, between docker containers like supervisor, core and addons. I rolled back my VM to a snapshot before the HA update and didn’t solved. Before start getting the errors I updated also the DSM, I think I updated all in the same day so I don’t have sure the origin of the problem but I think is something in between HA and DSM updates. Hope I can fix this soon because life without HomeAssistant automations is not the same! 😅 |
I found a solution today and that’s crazy!! @BZH-Taz maybe your problem was the same and the direct router connection “solved” that issue but if it comes back you can try to set additional DNS servers directly on HA config and it’s done. Cheers |
Hello, |
Hello, In HA web interface under System > Network > Network Interfaces > IPV4 > DNS Servers If you cant access the web interface at all, I think you can also do it using the console. |
Describe the issue you are experiencing
I tried to install the latest version of Home Assistant OS (haos_ova-13.2.ova) on a virtual machine on my NAS Synology but it failed each time at the first start of Home Assistant. When I connect to the ipadress:8123 I get the error message : "An error occured while installing Home Assistant, check the logs below for more information."
What operating system image do you use?
ova (for Virtual Machines)
What version of Home Assistant Operating System is installed?
n
Did the problem occur after upgrading the Operating System?
No
Hardware details
NAS Synology DS920+ with 20Go RAM.
Steps to reproduce the issue
...
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: