Skip to content
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

update to Home Assistant OS 7.2 stopped at "Waiting for Supervisor to startup..." #1728

Closed
glc650 opened this issue Jan 25, 2022 · 6 comments
Labels
board/odroid Hardkernel's ODROID Boards bug stale

Comments

@glc650
Copy link

glc650 commented Jan 25, 2022

Describe the issue you are experiencing

After upgrading to Home Assistant OS 7.2 (from 7.1) my system hung at:
IMG_2251

I waited for ~15 minutes and then did a hard reboot. The update appears to have been successful but this is the first issue I've ever had with an OS update.

What operating system image do you use?

odroid-n2 (Hardkernel ODROID-N2/N2+)

What version of Home Assistant Operating System is installed?

7.2

Did you upgrade the Operating System.

Yes

Steps to reproduce the issue

Click on the update button.

Anything in the Supervisor logs that might be useful for us?

couldn't check logs at the time

Anything in the Host logs that might be useful for us?

couldn't check logs at the time

System Health information

No response

Additional information

No response

@glc650 glc650 added the bug label Jan 25, 2022
@agners agners added the board/odroid Hardkernel's ODROID Boards label Jan 26, 2022
@agners
Copy link
Member

agners commented Jan 26, 2022

Did you have internet connection at that time? Was the second boot successful?

@glc650
Copy link
Author

glc650 commented Jan 26, 2022

Yes to both.

@agners
Copy link
Member

agners commented Jan 27, 2022

I need the debug logs from the underlying OS (e.g. obtained via direct SSH connection using https://developers.home-assistant.io/docs/operating-system/debugging#ssh-access-to-the-host). To get all logs from the previous boot use journalctl -b -1.

@glc650
Copy link
Author

glc650 commented Jan 27, 2022

I've rebooted a few times since then to make sure all was good. Can I still get the logs you need?

@agners
Copy link
Member

agners commented Jan 27, 2022

So the -b -1 says "last reboot". You can use higher values, until you get the logs of the problematic boot. There is also journalctl --list-boots which lists boot. The log buffer is quite large, it should contain logs of a week+.

@github-actions
Copy link

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
board/odroid Hardkernel's ODROID Boards bug stale
Projects
None yet
Development

No branches or pull requests

2 participants