-
Notifications
You must be signed in to change notification settings - Fork 965
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
13.1 rc1 will not load #3545
Comments
Right, there's no information about the issue in these logs. The messages shown at boot are the host logs, but by default the log contains only 100 last lines. You can try running If the error happens after mounting the data disk, it should be persisted, but if it happens early in the boot, it may be empty. In that case watching VirtualBox console to determine where it fails would be needed as the first step. |
I did another attempt to upgrade through the UI, and it came back up again as 12.4. This is the log file: hostlogs.txt |
I will take a look at the console when I am at home, I can't do that from here. Everything flashes by real fast though, too fast to read sometimes. I'll see if I can use a screengrabber to record it, unless you know of a better trick. |
OK, I stopped the VM using the ACPI shutdown command, changed the settings to reflect your screenshot above, then restarted the VM. It booted normally into 12.4. Then I typed 'os update' into the terminal CLI. It restarted but ended up in 'rescue mode'. I got a prompt and typed 'exit'. Then in booted back up normally in 12.4. |
I don't see any attempt to boot to OS 13 in that log. Can you check manually select the other boot slot in the boot loader before it boots automatically?
That's okay, it's the emulated firmware's attempt to boot from optical drive that doesn't exist. |
Okay, I'm not quite sure what happened, but it seems the problems is fixed with the 13.1 release :-) . I wasn't aware the release was already done. I did the update a few moments ago from the console. The first attempt it selected slot B (okay=1 , try =1), and since things were weird before I selected the other slot (A, ok=1, try=0). That booted int o 12.4, so I did another |
Well, I didn't say ALL issues were resolved. But since in my case the system still started, and the problem only occurred in the beta release, I think yours is a different issue and should be reported as such.
Devoman71 ***@***.***> schreef op 22 augustus 2024 04:39:37 CEST:
…I have just broken my live enstance by applying OS 13..1 so the issue seems not resolved as it's not booting up. I'm using a generic Intel machine.
I will have to rebuild from my backups and I will not use OS 13,1
--
Reply to this email directly or view it on GitHub:
#3545 (comment)
You are receiving this because you modified the open/close state.
Message ID: ***@***.***>
|
Well, it seems I have to reopen this issue. I rebooted my VM today, and to my great surprise it booted back up in OS 12.4! I had a notification badge for upgrading both OS (to 13.1) and core (to 8.3 from 8.2). I started with the core update, but that resulted in a very long wait with nothing happening except the instance going offline. I could not even shut it down from the Virtualbox manager app, had to kill it from the host OS. I have no idea what happened, the instance probably booted from another slot that still had 12.4 in it? After killing the VM I could start it again and it booted back into 12.4. I don't have too much time right now to tinker, but if there are any tests I can do let me know |
I tried installing a clean 13.1 and a backup of my system. 13.1 installs just fine with all settings the same as the current VM. Backup of the 12.4 OS/8.2 core system can be restored to that installation no problem (backup doesn't change OS of course, so then it is 13.1os/8.2 core. At least one manual restart resulted in no problems. Running the update to 8.3 core made the VM freeze again, again requiring a kill from the guest OS to shut it down. Really strange. |
Describe the issue you are experiencing
I am trying to upgrade to the 13.1. rc version for beta testing but I don't get it to load. See also my comments in 'discussion' but I guess that wasn't the place for it?
The short of it: when I attempt to upgrade, the system simply boots back up in the existing 12.4
Three consecutive upgrade attempts put me into 'rescue mode'
What operating system image do you use?
ova (for Virtual Machines)
What version of Home Assistant Operating System is installed?
12.4
Did the problem occur after upgrading the Operating System?
Yes
Hardware details
Host OS: Linux Mint 22. Hypervisor: Virtualbox 7.0.16. USB devices: sonoff zigbee dongle 'e', USB ssd drive (passthrough enabled in Virtualbox but not physically connected).
Steps to reproduce the issue
os upgrade
in the CLI...
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
I can't seem to find the log file that holds the full set of messages that appear on boot (bootlog, I guess that is called) That may contain useful information but it's not in the 'host' log. Where is that located, or is it not stored?
The text was updated successfully, but these errors were encountered: