was just about to do this…think ill give it a miss for now as also running on an Intel NUC
After upgrading my RaspberryPi 4: I now have problems with my ZHA (Zigbee Home Automation): it does not startup anymore, because it can’t start the “deCONZ RaspBee I/II coordinator”. Also my HACS ble_monitor has no connection to bluetooth anymore - so my house is dark now 
2 Likes
@Sangoku @mrbasque this issue has been reported here as well: HA 8.0 fails to boot (incorrect compressed chunk) · Issue #1912 · home-assistant/operating-system · GitHub. It seems that GRUB2 has problems on some x86-64 systems reading from the compressed, squashfs bsaed kernel partition. Please share the details of your system in that issue report, it would help narrow down affected systems.
@Boklak we had similar reports during the RC, but it got resolved in 8.0 for most people, see Error updating versions higher than Home Assistant OS 8.0.dev20220321 · Issue #1830 · home-assistant/operating-system · GitHub. Did you upgrade to the final 8.0 release?
@LeoSko haven’t seen that issue so far, can you open an issue in the Home Assistant OS repository? Sign in to GitHub · GitHub
Homeassistant OS 8, in VMWare updated successfully, VMware, reports "Version Other Linux 5.x kernel 64-bit.
Ha reports Kernel version 5.15.38
Upgraded from latest OS, Supervisor, Core Versions
Windows 10 P(latest update), i7-4700MQ(MSI GE60), VMware VMCI Host Device - Driver Version 9.8.16.0 (Vmware Workstation 16)
PS: VMware installed on separate exFat Disk
Edit: All disks are GPT
NOTE: After reading below posts, i checked my HOST-File , and did found it “peculiar” thou i’ve never paid any special attention to the HOST-Log , But in regards to i’e network interfaces ect. Only USB shows a “strange behavior” ( New Device Found )
[ 1.367219] ACPI: bus type USB registered
[ 1.367534] usbcore: registered new interface driver usbfs
[ 1.368505] usbcore: registered new interface driver hub
[ 1.369544] usbcore: registered new device driver usb
[ 3.230689] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 3.236283] ehci-pci 0000:02:03.0: new USB bus registered, assigned bus number 1
[ 3.247889] ehci-pci 0000:02:03.0: USB 2.0 started, EHCI 1.00
[ 3.249986] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15
[ 3.252399] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.254494] usb usb1: Product: EHCI Host Controller
[ 3.255930] usb usb1: Manufacturer: Linux 5.15.38 ehci_hcd
[ 3.257543] usb usb1: SerialNumber: 0000:02:03.0
[ 3.259058] hub 1-0:1.0: USB hub found
[ 3.261589] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 3.264722] uhci_hcd: USB Universal Host Controller Interface driver
[ 3.268634] uhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2
[ 3.272893] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.15
[ 3.275313] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.277422] usb usb2: Product: UHCI Host Controller
[ 3.278850] usb usb2: Manufacturer: Linux 5.15.38 uhci_hcd
[ 3.280441] usb usb2: SerialNumber: 0000:02:00.0
[ 3.282287] hub 2-0:1.0: USB hub found
[ 3.287042] xhci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 3
[ 3.293476] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15
[ 3.295925] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.298027] usb usb3: Product: xHCI Host Controller
[ 3.299455] usb usb3: Manufacturer: Linux 5.15.38 xhci-hcd
[ 3.301075] usb usb3: SerialNumber: 0000:03:00.0
[ 3.302654] hub 3-0:1.0: USB hub found
[ 3.307411] xhci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 4
[ 3.309596] xhci_hcd 0000:03:00.0: Host supports USB 3.1 Enhanced SuperSpeed
[ 3.311800] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[ 3.314125] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.15
[ 3.316581] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.318687] usb usb4: Product: xHCI Host Controller
[ 3.320106] usb usb4: Manufacturer: Linux 5.15.38 xhci-hcd
[ 3.321768] usb usb4: SerialNumber: 0000:03:00.0
[ 3.323313] hub 4-0:1.0: USB hub found
[ 3.326657] usbcore: registered new interface driver usblp
[ 3.328465] usbcore: registered new interface driver usb-storage
[ 3.330281] usbcore: registered new interface driver usbserial_generic
[ 3.332171] usbserial: USB Serial support registered for generic
[ 3.388043] usbcore: registered new interface driver usbhid
[ 3.389908] usbhid: USB HID core driver
[ 3.505863] usb 2-1: new full-speed USB device number 2 using uhci_hcd
[ 3.551880] usb 3-1: new full-speed USB device number 2 using xhci_hcd
[ 3.781697] usb 2-1: New USB device found, idVendor=0e0f, idProduct=0008, bcdDevice= 1.00
[ 3.794160] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.805080] usb 2-1: Product: Virtual Bluetooth Adapter
[ 3.813894] usb 2-1: Manufacturer: VMware
[ 3.820846] usb 2-1: SerialNumber: 000650268328
[ 3.840706] usb 3-1: New USB device found, idVendor=0e0f, idProduct=0003, bcdDevice= 1.03
[ 3.845331] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3.849485] usb 3-1: Product: VMware Virtual USB Mouse
[ 3.852648] usb 3-1: Manufacturer: VMware
[ 3.860961] input: VMware VMware Virtual USB Mouse as /devices/pci0000:00/0000:00:15.0/0000:03:00.0/usb3/3-1/3-1:1.0/0003:0E0F:0003.0001/input/input4
[ 3.869305] hid-generic 0003:0E0F:0003.0001: input,hidraw0: USB HID v1.10 Mouse [VMware VMware Virtual USB Mouse] on usb-0000:03:00.0-1/input0
[ 3.947009] usb 2-2: new full-speed USB device number 3 using uhci_hcd
[ 4.089167] usb 2-2: New USB device found, idVendor=0e0f, idProduct=0002, bcdDevice= 1.00
[ 4.092521] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4.095298] usb 2-2: Product: VMware Virtual USB Hub
[ 4.097401] usb 2-2: Manufacturer: VMware, Inc.
[ 4.107190] hub 2-2:1.0: USB hub found
[ 5.061323] usbcore: registered new interface driver btusb
Could be the cause of “lost” USB-Devices, turning up as “New”, For some Users
EDIT: Maybe because i only have a wired mouse attached , everything was “seamless”
Since upgrading to OS 8.0, my Z-Wave is broken, with the error “Driver: Failed to open the serial port: Error: No such file or directory, cannot open /dev/serial/by-id/usb-0658_0200-if00”.
Running 2022.5.4 in a Proxmox VM.
1 Like
RPi4 over here. Upgraded to HA OS 8.0 and the Deconz firmware which strangely shows “Not connected” in Phoscon…
I am using Deconz add-on 6.13.0
After restarting, Deconz is no longer booting up.
On https://xxx.duckdns.org:8123/hassio/addon/core_deconz/config , line
/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2254892-if00
seems to be playing hide and seek.
After selecting it eventually and clicking Save, error ?!
Failed to save add-on configuration
It’s a total mess 
I had a canable USB stick too , not connected anymore… In my case I had to turn off, not restart… After boot it was up again, maybe that helps with deconz too… running on esxi here
For intel NUC the uefy boot menu was the solution.
I enabled legacy boot. Rebooted. enabled Uefy boot manager and it worked like a charm.
1 Like
Fixed via totally shutting down (power off) the host then restarting. Thanks for the suggestion pergola.fabio!
Same here, cant turn off my lights in the middle of the night wanting to go to bed 
any fix yet on your side?
I switched off my RPi, unplugged the Conbee 2 stick, restarted HA and the host, all this no to avail.
I’ve just noticed that, in the Phoscon interface, my Conbee II name and logo had been replaced by Raspbee with a new icon 
So I’m wondering if the firmware update I made within the Phoscon interface has not broken something…
BEFORE
AFTER
I’m afraid of restoring the previous Phoscon backup and having to pair my switches again…
So FWIW updated to 8.0 and after restarting nothing. Pulled the power a couple of times, still nothing. My 'pi is normally running headless so I hooked up a monitor and could see nothing - so another cold boot - and this time it started up ok albeit running 7.6 so it had reverted to the fallback. I might hold off trying the update for a few days… 
1 Like
Had some issues after upgrading to 8.0. Very long shutdown and boot-up times. It failed boot once; got hung up on the docker container initialization, and went into emergency shell. Another forced reboot and i saw it flash up quickly and select “slot 2”, and it booted ok, but still took forever.
Noticed it was using almost all the allocated 8GB of ram before reboot, but only 3 GB after reboot.
running HASS OS under Proxmox 7.1 in OVMF, 4 cores, 128GB partition, 8 GB RAM, 2x USB 2.0 devices passed through by ID (Conbee II and zWave stick),
AddOns: Deconz, zWave JS, SSH, Studio Code Server, HACS, ESPHome
I noticed in the deconz config the device address had changed to the wrong one suddenly, changing this back fixed it for me. In my case it was set to /dev/ttyS0 while it had to be the /dev/ttyAMA0
Hmm, interesting.
Even when I choose /dev/ttyAMA0 , Save and restart the add-on, the stick is still not picked up.
Yesterday I upgraded HA OS to 8.0 AND upgraded the Deconz firmware (within the Phoscon interface)
Not sure which one broke something, if not both…
I could restore a previous version of Hassio (downgrading to OS 7.x) but I’m not sure it’ll be sufficient since I also updated the firmware in Phoscon (which I don’t know how to downgrade)
Anyway, in the Phoscon web interface, what version of firmware do you have (*) and does it say RaspBee or ConBee II like it should ?
I’m afraid if I “Reset gateway” (in Phoscon) I will have to pair all my devices again 
(*) mine is currently 2.15.3 / 21/04/2022
[Edit] I will try upgrade the FW manually following the instructions within that issue.
I have a Raspbee II, version 2.15.03 / 21-4-2022. It’s also shown correctly, Can’t recall if it showed incorrect when it didn’t work.
For the Conbee II you should see a serial/by-id device like so (this is from my Rasberry Pi 4 test device running HAOS 8.0)
I guess deCONZ changed the graphics because you are using a ttyAMA0 device, which is what you would use if you had a Raspbee II.
If the serial/by-id device not appearing anymore, there is some lower level problem (driver not loading correctly/hardware problem). Are the host (kernel dmesg) logs saying something? Also try to unplug/replug the device at runtime.
What is your setup using exactly (what Raspberry Pi model/SD-card or SSD)?
When you connect a monitor after startup it often is not showing anything. If you try again, connect the monitor before updating. Your issue seems similar to what is described in this report: Restart issues on 8.0.rc1-4 - System seems to hang · Issue #1888 · home-assistant/operating-system · GitHub
Unfortunately, I was unable to reproduce this so far.
Yep, I do get that entry
/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2254892-if00
if I play around with the tabs and radio buttons going back and forth 
But like mentioned earlier, whenever this entry shows up and I select it, saving fails…
I’ll try to upgrade the Conbee II stick manually on Windows thanks to these links
Hm, that is weird, can you try restart the add-on and then save again? Maybe the front-end somehow has stale config entries, is the device still listed when reloading using Ctrl+F5? If its still present, is there maybe something in the Supervisor logs?