Updating HAOS VM (since 13.1 -> 13.2) results in the VM never rebooting automatically #3714
Labels
Comments
|
So, I literally just did the same procedure I used to successfully update from 13.1 to 13.2 and this time the update succeeded. Essentially, all I did was.. "host reboot" from the CLI and allow the VM to reboot successfully (it did) and then immediately take a snapshot (just incase) and then attempt an update to HAOS 14 and this time the update completed and rebooted successfully. Obviously there is entirely no way to capture everything that's printed in the console during the reboot, but I did make a screen recording of the console while that was doing its thing. |
|
This is basically the same as my issue that i raised earlier today. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue you are experiencing
Ever since attempting to update my HAOS VM (running on proxmox) from 13.1 to 13.2 I've been having issues. The first time I attempted 13.1 -> 13.2 the system never restarted (I think there is a post somewhere about that) and I had no clue how to troubleshoot so I just restored a previous backup. Just last night I attempted the update again and this time I noted it hung on "target reached: system reboot." I manually rebooted the VM and 13.2 loaded just fine. I subsequently tried "cli host reboot" and the system rebooted just fine back into 13.2 without issue. I also didn't note anything of interest in the system logs.
This morning I saw the release of HAOS 14 and attempted to update, making sure to make a snapshot right before. This time the 13.2 -> 14 update got stuck at "Unmounting HassOS data partition..." and after about 5mins I just threw in the towel and rolled back to my snapshot. Per https://github.com/home-assistant/operating-system/discussions/3711#discussioncomment-11461465 I'm raising this issue and providing the output of
blkidThe above output was entirely too difficult to actually get.. it's from a screenshot that I then had to select the "text" from, so some of it may not have "translated" correctly. Apparently there is zero way to get to a login prompt on the host system to be able to run blkid in such a way as to be able to copy and paste the output. I tried installing the ssh add-on, but that just drops you into a shell inside docker with zero access to blkid. You get access to "ha" but there is no "ha login" within that environment. Perhaps someone else knows a way to actually get access to the host is in a meaningful way?
@agners
**Also, all the log output that was pasted in below is from my rolled back 13.2 install, NOT 14.**What operating system image do you use?
ova (for Virtual Machines)
What version of Home Assistant Operating System is installed?
13.2
Did the problem occur after upgrading the Operating System?
Yes
Hardware details
Proxmox 8.2.7
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 Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Additional information
No response
The text was updated successfully, but these errors were encountered: