I’m seeing the same issue here. HassOS in a proxmox vm. No deconz but I do have a CC2531.
Curiously I’m having a lot of trouble using either the built-in Samsung TV integration or any of the HACS integrations. ollo69 integration was working a treat for months. May just be a coincidence.
same here.
supervisor-2021.02.6
core-2021.2.2
Home Assistant OS 5.11
proxmox 6.3.3
Same problem here
ESXI 6.7
HassOs update 5.10 > 5.11
supervisor-2021.02.6
core-2021.2.2
I am runnng
Zigbee2MQTT
C2531 zigbee stick
Node Red
The last months i had more problems, so i make snapshot in ESXI before.
After waiting for 30 minutes i reverted to the old snapshot and running in less then 1 minute.
Pretty sure it was Supervisor 2021.2.5 or 6 that did it.
3 Likes
Every restart of Homeassistant is now terribly slow… never had that…
Home Assistant is starting, not everything will be available until it is finished.
Takes forever
So far so good. Managed to update both supervisor and Core without any problems.
Updating supervisor and core is not the problem. The delay during a home assistant restart is.
I will try to submit an issue in Github homes assistant core tomorrow.
Yesterday I installed new debian buster and moved my instalation backup there and made ESX snapshot.
Right now everything works ok but as soon I restart my ha OS I get address in use.
My setup.
I also get…
Something is blocking Home Assistant from wrapping up the start up phase. We’re going to continue anyway. Please report the following info at https://github.com/home-assistant/core/issues: … and then a huge list of my “things”
Boot not proceeding with VirtualBox running on Mac following the upgrade of the HA OS. Trying a different VM instance now.
Hi All, I have same issue.
Using Proxmox, updated the new core and that seemed to go ok, I then updated HACS and when that completed hit reboot and got this error - so not really sure what caused it - only that I am in the same situation.
In Proxmox I can still access the console and I have ‘checked’ core (couldn’t update it says see supervisor) in there that looked ok too so the OS seems somewhat intact.
Confused but eagerly awaiting someone smarter than me to fix (or at least with more hours left in your day!!)
Whats really weird is now it is working again! For me the Browser would not engage at all but the console was working - as a final refresh the browser is now up and running again!. will have a quick look round to see if anything obvious is wrong!
cybergrimes,
Are you running Linux, Debian, Ubuntu, etc…for your VM instance in VirtualBox? I’m running Linux 2.6 on a MacBook Pro and was relatively quick until HA OS 5.11 and Supervisor 2021.02.6, and now I can’t boot up. Are you able to boot?
At this point, I guess I’m just adding a “me too”. I have all the problems listed here after upgrading to 2021.2.1. I can’t upgrade to 2012.2.2 (Can’t execute wrapper while a task is in progress
). My logs and history are missing. I have the “bind failed: Address in use”, although I’m starting wonder whether that is a red herring. I have removed all plugins, and the problem has not gone away. Not sure what to do next…
Same supervisor and core but VirtualBox is hosted from Windows 10. It’s booting fine just seeing the error message same as everyone else.
I only even noticed because I was playing with spinning up a second instance for testing.
That’s what I was afraid of, I’m 1hr in and stuck in startup. Something is not gelling here with OS 5.11 and 2021.02.6, as I would boot up from a dead start in the VM in ~20min before. Irrespective of the udev error code. Thanks brother, let me keep looking
As is usually the case, as soon as I posted this, I figured out the problem. Several threads I had read mentioned ZWave problems, so I had removed the ZWave dongle and the ZWave entries in configuration.yaml. This did not help, but I had forgotten about the integrations! I found that I have two ZWave integrations loaded. I removed them both, rebooted, and everything came up.
I don’t have any ZWave. I have some Wyze components (which the sensors aren’t working), but that’s it. No Zigbee or Zwave
same issue as everyone here. HA was running fine. I rebooted VMWare and got this error. I read this thread and another. in the other someone suggested an HA supervisor repair. I gave it a try and it worked. HA is back up and running.
2 Likes