I amended my start post after reading that back:
EDIT: To be clear. It was not me that has selected “the solution”. Frenck did do that himself. I still have the error and weird problems after posting this. Also following this with great interest.
I can understand that if you have a problem with your Home Assistant instance and you see this error, you think this error has something to do with it.
I did the same. But my problem had nothing to do with it. My database was broken. After I deleted it everything was working fine again.
And the error in this topic was still on the screen of my vm.
This weekend I did a clean install for a friend. Even with a clean install this error appeared.
And that Home Assistant instance was working perfectly fine.
So I think Frenck is right (of course he is, he is one of the developers 
)
So if you have this error and a problem with your Home Assistant instance try to ignore this error and look further than this error. 
Only to stop the feeling of an dangerous case. This message means nothing. It will be gone soon as the new Audio Plugin update is out. It’s only a warning which shows if an older HA Core (< 2021.02) is startup or the old Audio Plugin because they use the old in-container udev and not the new Host udev.
The udev message is may not related to, but i identified my shutdown lag of 220 sec:
With this config entry HA restart need long time!
Feb 15 16:14:43 homeassistant dockerd[327]: time="2021-02-15T16:14:43.667177443Z" level=info msg="Container eb59b5ec4f8f640b1d69514b096cfb214f3178bcec28c1839be02345d93aa3e3 failed to exit within 220 seconds of signal 15 - using the force"
## EnOcean Config USB300 DB
enocean:
device: /dev/serial/by-id/usb-EnOcean_GmbH_EnOcean_USB_300_DB_FT3B4REQ-if00-port0
I have a Home Assistant instance in a Proxmox VM running which was built with https://github.com/whiskerz007/proxmox_hassos_install
Question: what can I do so I can see what is happening when the VM is booting, and while Home Assistant is starting? Do you have any tips which logs to examine, which log settings to set in Home Assistant, etc?
At the moment I only know how to take a look in the Home Assistant log after everything started. I don’t know for example how to examine the Linux system log in the VM.
I’ve had this exact same error and I am BRAND NEW to HA this is literally my first ever install on a VirtualBox machine on an i5 laptop that I installed a clean windows build on with nothing else running.
I’ve read through so much of this post to figure out what is wrong and none of this relates to me as I can’t even start HA for the first time after getting this error let alone change the number of things people are suggesting might be the culprit.
I really need advice as this Noob has no idea what to do and its quickly scaring me off my migration to HA.
SOMEONE PLEASE HELP
1 Like
Welcome @Gtwizzy!
Good that you try Home Assistant!
You can try to find a good guide to help you install HA in VirtualBox. Example: https://peyanski.com/home-assistant-on-windows-using-virtualbox/
And even though you may get the error, HA may still have started successfully.
What makes you say that Home Assistant is not starting?
Do you know the IP address of HA and tried to surf to http://a.b.c.d:8123 where a.b.c.d is the IP address?
Hi mchangsp
Thankyou for the helpful link. I had tried to navigate to the home assistant login using the 3 different methods outlined in the install guide eg. homeassitant.local:8123, homeassistant:8213 and finally my IP address http://192.168.x.x:8212 and none of these will bring me to the login screen.
However I have just watched the beginning of the video in the link you sent me and now understand that I can make some changes in the system before getting into the login screen (like set a static IP) which I will now try out tomorrow to see if this allows me to login.
I’ll let you know how I go. Thank you in advance 
Ok so I set up static IP addresses and tried the whole thing again using the new static ipv4 address that I created and still can’t reach the login screen. I’m not sure what I’m doing wrong. I think at this point I should probably just start a clean install, and if I’m still having the issue post a new thread to the ‘installation’ area of the forums.
Thanks for your help though @mchangsp
Hi @sender it started as the same problem but seems to now no longer be this. I have already begun a new topic. Sorry for the inconvenience
I personally had this issue today, on a brand new install of Home Assistant OS in a fresh vm on Proxmox VE 6.3-3. I solved the issue by changing my “machine” from Q35 to i440fx.
This is under the Hardware heading.
My VM was already at i440fx before the problems started. Perhaps I have to switch to Q35? 
I’m having the same error, except it’s showing devd[205] - this is the first time that I’ve installed HA on my computer, using VMware Workstation 16 Pro on a Windows machine. I’ve deleted the image, adjusted compatibility settings, changed network connections - all nada. If anyone finds a solution to this, please @ me. I can’t be too upset as it’s free and open source but I just spent 3 hours trouble shooting and can’t find a solution…
5.11 seems to be junk, updating to it broke my HA setup. I used the 5.9 image and all is good again even though this error was present in that version too.
You can download it here…
1 Like
I was actually able to fix mine - I needed to go into the VMware Virtual Network Editor and manually add the Network Bridge. Hope this helps anyone else struggling with this issue on initial setup in VMware Workstation 16 Pro.
As @frenck predicted the error message “bind failed” disappeared when I upgraded to supervisor-2021.02.11.
Average reboot times for me (from the event “Home Assistant stopped” to “Home Assistant started”) is 4 minutes. Before Home Assistant version 2012.02 it was 2 minutes.
I will try to use https://developers.home-assistant.io/docs/operating-system/debugging/
to see if I can find the source of the delay.
What for USB Sticks do you use?
I am using the following USB devices in my Intel NUC - BOXNUC8I5BEH2:
- a 500 GB WD USB hard disk in the back USB 2 port
- a Conbee2 stick in the back USB 2 port
- a Vodafone UMTS modem stick in the left front USB port of the NUC
WD USB hard disk and Conbee2 stick are working reliably.
The Vodafone stick works after restart of the NUC, and sometimes stops working silently.
Conbee stick details
- name: 6-2
sysfs: '/sys/devices/pci0000:00/0000:00:1e.0/0000:01:1b.0/usb6/6-2'
dev_path: /dev/bus/usb/006/002
subsystem: usb
by_id: null
attributes:
BUSNUM: '006'
DEVNAME: /dev/bus/usb/006/002
DEVNUM: '002'
DEVPATH: '/devices/pci0000:00/0000:00:1e.0/0000:01:1b.0/usb6/6-2'
DEVTYPE: usb_device
DRIVER: usb
ID_BUS: usb
ID_MODEL: ConBee_II
ID_MODEL_ENC: ConBee\x20II
ID_MODEL_ID: '0030'
ID_PATH: 'pci-0000:01:1b.0-usb-0:2'
ID_PATH_TAG: pci-0000_01_1b_0-usb-0_2
ID_REVISION: '0100'
ID_SERIAL: dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2219203
ID_SERIAL_SHORT: DE2219203
ID_USB_INTERFACES: ':020201:0a0000:'
ID_VENDOR: dresden_elektronik_ingenieurtechnik_GmbH
ID_VENDOR_ENC: dresden\x20elektronik\x20ingenieurtechnik\x20GmbH
ID_VENDOR_ID: 1cf1
MAJOR: '189'
MINOR: '641'
PRODUCT: 1cf1/30/100
SUBSYSTEM: usb
TYPE: 2/0/0
USEC_INITIALIZED: '2325398'
- name: ttyACM0
sysfs: >-
/sys/devices/pci0000:00/0000:00:1e.0/0000:01:1b.0/usb6/6-2/6-2:1.0/tty/ttyACM0
dev_path: /dev/ttyACM0
subsystem: tty
by_id: >-
/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2219203-if00
attributes:
DEVLINKS: >-
/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2219203-if00
/dev/serial/by-path/pci-0000:01:1b.0-usb-0:2:1.0
DEVNAME: /dev/ttyACM0
DEVPATH: >-
/devices/pci0000:00/0000:00:1e.0/0000:01:1b.0/usb6/6-2/6-2:1.0/tty/ttyACM0
ID_BUS: usb
ID_MODEL: ConBee_II
ID_MODEL_ENC: ConBee\x20II
ID_MODEL_ID: '0030'
ID_PATH: 'pci-0000:01:1b.0-usb-0:2:1.0'
ID_PATH_TAG: pci-0000_01_1b_0-usb-0_2_1_0
ID_REVISION: '0100'
ID_SERIAL: dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2219203
ID_SERIAL_SHORT: DE2219203
ID_TYPE: generic
ID_USB_DRIVER: cdc_acm
ID_USB_INTERFACES: ':020201:0a0000:'
ID_USB_INTERFACE_NUM: '00'
ID_VENDOR: dresden_elektronik_ingenieurtechnik_GmbH
ID_VENDOR_ENC: dresden\x20elektronik\x20ingenieurtechnik\x20GmbH
ID_VENDOR_ID: 1cf1
MAJOR: '166'
MINOR: '0'
SUBSYSTEM: tty
TAGS: ':systemd:'
USEC_INITIALIZED: '2450839'
Vodafone stick details
- name: ttyUSB0
sysfs: '/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0/ttyUSB0/tty/ttyUSB0'
dev_path: /dev/ttyUSB0
subsystem: tty
by_id: /dev/serial/by-id/usb-HUAWEI_Technology_HUAWEI_Mobile-if00-port0
attributes:
DEVLINKS: >-
/dev/serial/by-id/usb-HUAWEI_Technology_HUAWEI_Mobile-if00-port0
/dev/serial/by-path/pci-0000:00:1d.7-usb-0:2:1.0-port0
DEVNAME: /dev/ttyUSB0
DEVPATH: '/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0/ttyUSB0/tty/ttyUSB0'
ID_BUS: usb
ID_MODEL: HUAWEI_Mobile
ID_MODEL_ENC: HUAWEI\x20Mobile
ID_MODEL_ID: '1465'
ID_PATH: 'pci-0000:00:1d.7-usb-0:2:1.0'
ID_PATH_TAG: pci-0000_00_1d_7-usb-0_2_1_0
ID_REVISION: '0000'
ID_SERIAL: HUAWEI_Technology_HUAWEI_Mobile
ID_TYPE: generic
ID_USB_DRIVER: option
ID_USB_INTERFACES: ':ffffff:0206ff:0a0000:080650:'
ID_USB_INTERFACE_NUM: '00'
ID_VENDOR: HUAWEI_Technology
ID_VENDOR_ENC: HUAWEI\x20Technology
ID_VENDOR_ID: 12d1
MAJOR: '188'
MINOR: '0'
SUBSYSTEM: tty
TAGS: ':systemd:'
USEC_INITIALIZED: '2506383'
- name: ttyUSB1
sysfs: '/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.3/ttyUSB1/tty/ttyUSB1'
dev_path: /dev/ttyUSB1
subsystem: tty
by_id: /dev/serial/by-id/usb-HUAWEI_Technology_HUAWEI_Mobile-if03-port0
attributes:
DEVLINKS: >-
/dev/serial/by-id/usb-HUAWEI_Technology_HUAWEI_Mobile-if03-port0
/dev/serial/by-path/pci-0000:00:1d.7-usb-0:2:1.3-port0
DEVNAME: /dev/ttyUSB1
DEVPATH: '/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.3/ttyUSB1/tty/ttyUSB1'
ID_BUS: usb
ID_MODEL: HUAWEI_Mobile
ID_MODEL_ENC: HUAWEI\x20Mobile
ID_MODEL_ID: '1465'
ID_PATH: 'pci-0000:00:1d.7-usb-0:2:1.3'
ID_PATH_TAG: pci-0000_00_1d_7-usb-0_2_1_3
ID_REVISION: '0000'
ID_SERIAL: HUAWEI_Technology_HUAWEI_Mobile
ID_TYPE: generic
ID_USB_DRIVER: option
ID_USB_INTERFACES: ':ffffff:0206ff:0a0000:080650:'
ID_USB_INTERFACE_NUM: '03'
ID_VENDOR: HUAWEI_Technology
ID_VENDOR_ENC: HUAWEI\x20Technology
ID_VENDOR_ID: 12d1
MAJOR: '188'
MINOR: '1'
SUBSYSTEM: tty
TAGS: ':systemd:'
USEC_INITIALIZED: '2505881'
- name: ttyUSB2
sysfs: '/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.4/ttyUSB2/tty/ttyUSB2'
dev_path: /dev/ttyUSB2
subsystem: tty
by_id: /dev/serial/by-id/usb-HUAWEI_Technology_HUAWEI_Mobile-if04-port0
attributes:
DEVLINKS: >-
/dev/serial/by-id/usb-HUAWEI_Technology_HUAWEI_Mobile-if04-port0
/dev/serial/by-path/pci-0000:00:1d.7-usb-0:2:1.4-port0
DEVNAME: /dev/ttyUSB2
DEVPATH: '/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.4/ttyUSB2/tty/ttyUSB2'
ID_BUS: usb
ID_MODEL: HUAWEI_Mobile
ID_MODEL_ENC: HUAWEI\x20Mobile
ID_MODEL_ID: '1465'
ID_PATH: 'pci-0000:00:1d.7-usb-0:2:1.4'
ID_PATH_TAG: pci-0000_00_1d_7-usb-0_2_1_4
ID_REVISION: '0000'
ID_SERIAL: HUAWEI_Technology_HUAWEI_Mobile
ID_TYPE: generic
ID_USB_DRIVER: option
ID_USB_INTERFACES: ':ffffff:0206ff:0a0000:080650:'
ID_USB_INTERFACE_NUM: '04'
ID_VENDOR: HUAWEI_Technology
ID_VENDOR_ENC: HUAWEI\x20Technology
ID_VENDOR_ID: 12d1
MAJOR: '188'
MINOR: '2'
SUBSYSTEM: tty
TAGS: ':systemd:'
USEC_INITIALIZED: '2503489'
- name: sr0
sysfs: >-
/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.5/host8/target8:0:0/8:0:0:0/block/sr0
dev_path: /dev/sr0
subsystem: block
by_id: '/dev/disk/by-id/usb-Vodafone_CD_ROM__Huawei_-0:0'
attributes:
DEVLINKS: >-
/dev/cdrom /dev/disk/by-id/usb-Vodafone_CD_ROM__Huawei_-0:0
/dev/disk/by-path/pci-0000:00:1d.7-usb-0:2:1.5-scsi-0:0:0:0
DEVNAME: /dev/sr0
DEVPATH: >-
/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.5/host8/target8:0:0/8:0:0:0/block/sr0
DEVTYPE: disk
ID_BUS: usb
ID_CDROM: '1'
ID_CDROM_MEDIA: '1'
ID_INSTANCE: '0:0'
ID_MODEL: CD_ROM__Huawei_
ID_MODEL_ENC: CD\x20ROM\x20\x28Huawei\x29\x20
ID_MODEL_ID: '1465'
ID_PATH: 'pci-0000:00:1d.7-usb-0:2:1.5-scsi-0:0:0:0'
ID_PATH_TAG: pci-0000_00_1d_7-usb-0_2_1_5-scsi-0_0_0_0
ID_REVISION: '2.31'
ID_SERIAL: 'Vodafone_CD_ROM__Huawei_-0:0'
ID_TYPE: cd
ID_USB_DRIVER: usb-storage
ID_USB_INTERFACES: ':ffffff:0206ff:0a0000:080650:'
ID_USB_INTERFACE_NUM: '05'
ID_VENDOR: Vodafone
ID_VENDOR_ENC: Vodafone
ID_VENDOR_ID: 12d1
MAJOR: '11'
MINOR: '0'
SUBSYSTEM: block
SYSTEMD_MOUNT_DEVICE_BOUND: '1'
TAGS: ':systemd:'
USEC_INITIALIZED: '2785891'
- name: sdb
sysfs: >-
/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.6/host9/target9:0:0/9:0:0:0/block/sdb
dev_path: /dev/sdb
subsystem: block
by_id: '/dev/disk/by-id/usb-Vodafone_Storage__Huawei_-0:0'
attributes:
DEVLINKS: >-
/dev/disk/by-id/usb-Vodafone_Storage__Huawei_-0:0
/dev/disk/by-path/pci-0000:00:1d.7-usb-0:2:1.6-scsi-0:0:0:0
DEVNAME: /dev/sdb
DEVPATH: >-
/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.6/host9/target9:0:0/9:0:0:0/block/sdb
DEVTYPE: disk
ID_BUS: usb
ID_INSTANCE: '0:0'
ID_MODEL: Storage__Huawei_
ID_MODEL_ENC: Storage\x20\x28Huawei\x29
ID_MODEL_ID: '1465'
ID_PATH: 'pci-0000:00:1d.7-usb-0:2:1.6-scsi-0:0:0:0'
ID_PATH_TAG: pci-0000_00_1d_7-usb-0_2_1_6-scsi-0_0_0_0
ID_REVISION: '2.31'
ID_SERIAL: 'Vodafone_Storage__Huawei_-0:0'
ID_TYPE: disk
ID_USB_DRIVER: usb-storage
ID_USB_INTERFACES: ':ffffff:0206ff:0a0000:080650:'
ID_USB_INTERFACE_NUM: '06'
ID_VENDOR: Vodafone
ID_VENDOR_ENC: Vodafone
ID_VENDOR_ID: 12d1
MAJOR: '8'
MINOR: '16'
SUBSYSTEM: block
TAGS: ':systemd:'
USEC_INITIALIZED: '2721904'
Try to remove vodafone stick and usb hd, on my side a enocean stick, prevented a shutdown with 220 sec.
1 Like