-
Notifications
You must be signed in to change notification settings - Fork 940
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
OS not properly reboot host #3440
Comments
I'm not sure how related this is but you have multiple HA instances on the network? There appears to be a duel for the hostname
This appears several times with different attempts to assign a number. |
Hi, that's a good thought. However, this does not explain why a hard reset works without problems despite unchanged customization. It seems to have a different cause, as a fallback to 12.3 also works again without customization. My satellites are started 1 minute earlier than the master. Both satellites already have 12.4 installed, start at the same time and have the same integrations. The difference to the master is that the satellites are Raspberry Pi's 4 and have no problems. But I will try that, thanks |
Update: |
What does it mean "does not reboot completely"? What happens when you run the host_reboot service? Anything in Core or Host logs after that point? Does it behave correctly if you run |
Hi, after the upgrade from 12.3 to 12.4 the host starts as usual. If a reboot is initiated with 12.4, the host does not boot. It is noticeable that the status LEDs on the LAN port then remain off. The host also does not come up again via the terminal. Since a hard reset solves the problem, I suspect the reboot process under 12.4. As soon as I go back to 12.3, everything works as usual. home-assistant_2024-06-27T11-08-32.266Z.log service: homeassistant.restart works without problems |
Looks like the computer stucks in grub |
There are 4 Options in Grub: Slot A boots 12.3 |
I did a complete reinstallation with the 12.4 image. The problem still exists. Going back to 12.3 |
Describe the issue you are experiencing
Hello,
I restart my hosts every morning, as this provides the best reliability of HA for me. However, with OS version 12.4, it seems that the host_reboot command is not working properly. After executing the command, the machine does not reboot completely, which is indicated by the status LED on the Mini PC. This does not flash, but lights up constantly as in normal operation. Subsequently, HA does not receive a correct network configuration:
2024-06-21 04:11:46.096 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=32 read=polling write=<idle, bufsize=0>>, socket: <asyncio. TransportSocket fd=32, family=2, type=2, proto=0, laddr=('0.0.0.0', 49442)>
2024-06-21 04:11:46.097 ERROR (MainThread) [async_upnp_client.ssdp] An error was received: [Errno 99] address not available, transport: <_SelectorDatagramTransport fd=57 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=57, family=10, type=2, proto=0, laddr=('::', 55125, 0, 0)>
Then some integrations like AsusRouter and remote_homeassistant cannot be started and block the boot process. However, deactivating the integrations would not help here either, as controlling the master via tablets does not work without a network configuration on the master.
However, a manual hard reset will get the system up and running again.
Best regards
What operating system image do you use?
generic-x86-64 (Generic UEFI capable x86-64 systems)
What version of Home Assistant Operating System is installed?
12.4
Did the problem occur after upgrading the Operating System?
Yes
Hardware details
AMD Ryzen 8845HS
64GB DDR5 RAM
1TB PCi 4.0 SSD
Dual Edge TPU
2.5Gb Ethernet
Conbee2 Stick
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
System Information
Home Assistant Supervisor
Dashboards
Recorder
Additional information
As already mentioned, the master starts normally when I perform a hard reset. My master and the voice assist satellites are in a seperate subnet which blocks internet connection.
Downgrade to 12.3 solves the problem
The text was updated successfully, but these errors were encountered: