Closed derolli1976 closed 8 months ago
Same issue and my entire HA OS instance crashes out and becomes unresponsive. Full Host reboot only runs stable for a minute or two and then crashes out with:
Same here, my Home Assistant is not coming online after updating
Same here
@DanDon @maxakash @ang3lx you all get panic: "ro" shorthand is more than one ASCIII character
on the console?
Are you using Hyper-V VM as well?
@DanDon @maxakash @ang3lx you all get
panic: "ro" shorthand is more than one ASCIII character
on the console?Are you using Hyper-V VM as well?
No, I am rrunning HA on Raspberry Pi 4 with sd card
@agners I'm out from home at this moment, so a can't see console I'm running on odroid c4
@DanDon @maxakash @ang3lx you all get
panic: "ro" shorthand is more than one ASCIII character
on the console?Are you using Hyper-V VM as well?
I'm not using Hyper-V ... I'm running the HA OS in a VM on VMware Workstation
Oh I see, this is on the beta channel. This is actually not related to the OS release itself, but to the current CLI instance. The OS lead to a reboot, which started the CLI again, and ultimately printed the error.
Underlying issue is already resolved, see https://github.com/home-assistant/cli/issues/460.
I'll create an updated HA CLI plug-in release, the issue should be resolved soon.
sorry, it's the first time something like this has happened to me... so I'm in trouble. Is the only way to boot properly is to format or restore from backup? or is there any operation to solve the problem
Same here, also reported at https://github.com/home-assistant/core/issues/111397
Issue resolved now. I am able to boot into HA dashboard.
Same. Can't boot after update. What are the recovery steps? Is there a forward fix or do we have to reformat?
Same for me on Raspberry. What can be done ? Only restore from backup ?
Not sure if related but 12.0 also broke my VM (VM running under Proxmox). Just boots to EFI shell. Had to restore full VM backup to get it going again.
Not sure if related but 12.0 also broke my VM (VM running under Proxmox). Just boots to EFI shell. Had to restore full VM backup to get it going again.
This is not really related.
That said, we have been reports of such issues already before, e.g. #2136. Unfortunately I was never able to reproduce this on my Proxmox setup, and we double checked all possible race conditions and make sure things are written to disk before the reboot. We even mount the boot partition "sync" mode, to make sure things hit the disk. Yet on every release (and mainly on virtual machines) we have such reports. If this is reproducible, or you have any logs/traces (maybe from the Hypervisor) which could be helpful, please open a new issue with the details.
Same for me on Raspberry. What can be done ? Only restore from backup ?
Your Home Assistant installation should remain working. You'll get the new CLI update 2024.02.1 within the next few hours. From then on the CLI will work normally again as well.
Same for me on Raspberry. What can be done ? Only restore from backup ?
Your Home Assistant installation should remain working. You'll get the new CLI update 2024.02.1 within the next few hours. From then on the CLI will work normally again as well.
New version fixes the issue for me. CLI is working again. At least for me, HA webclient has been available all the time.
Your Home Assistant installation should remain working. You'll get the new CLI update 2024.02.1 within the next few hours. From then on the CLI will work normally again as well.
Left it running 4-5 hours after your comment and tried a couple restarts. There is 0 activity on network and it never even gets an ip. I had to reinstall everything. Luckily I had a recebt backup so I lost about 36h of data.
What process is in place to catch something like this next time? Why don't we require a backup before an os install?
The main issue here, panic: "ro" shorthand is more than one ASCIII character
on the system console, is resolved by the latest CLI update, as confirmed by @derolli1976 . I am closing the issue.
@nicolazilio @atus your issues are not related to this issue really. Please open a new issue along with all required information.
Describe the issue you are experiencing
Running on Hyper-V VM. Looks like everything else is working fine.
What operating system image do you use?
ova (for Virtual Machines)
What version of Home Assistant Operating System is installed?
12.0
Did you upgrade the Operating System.
Yes
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
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4949 Installed Version | 1.34.0 Stage | running Available Repositories | 1401 Downloaded Repositories | 7Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 12.0 -- | -- update_channel | beta supervisor_version | supervisor-2024.02.0 agent_version | 1.6.0 docker_version | 24.0.7 disk_total | 30.8 GB disk_used | 6.0 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | Advanced SSH & Web Terminal (17.1.1), Studio Code Server (5.15.0), Node-RED (17.0.7), Log Viewer (0.17.0)Dashboards
dashboards | 2 -- | -- resources | 2 views | 1 mode | storageMercedesME 2020
api_endpoint_reachable | ok -- | -- websocket_connection_state | connected cars_connected | 1 version | v0.11.1Recorder
oldest_recorder_run | February 14, 2024 at 7:10 AM -- | -- current_recorder_run | February 26, 2024 at 4:27 PM estimated_db_size | 9.50 MiB database_engine | sqlite database_version | 3.44.2Additional information
No response