System not start

[kaidem4]

Describe the issue you are experiencing

After update to last version, the system dont start anymore. black screen and not keyboard abailable. Only ping responses.
rpi 5 8Gb

What operating system image do you use?

rpi5-64 (Raspberry Pi 5 64-bit OS)

What version of Home Assistant Operating System is installed?

14.0

Did the problem occur after upgrading the Operating System?

Yes

Hardware details

rpi5

Steps to reproduce the issue

1.automatic from ha web
2.
3.
...

Anything in the Supervisor logs that might be useful for us?

i cant access the system to view

Anything in the Host logs that might be useful for us?

The sistem not start. I cant view anything

System information

No response

Additional information

No response

[bigskookum]

I also got this, upgrading to 14.2 from 14.1 on x86. I managed to boot back into 14.1 using this procedure:

#2272 (comment)

The /dev/sda8 partition was named haaos-data-dis

[idcrook]

Doing HAOS 14.2 Update from 14.1 I also got an unresponsive system. rpi5-64 as well.

Update: 11 minutes later, Unplugged power, and attached a USB mouse, USB keyboard, and HDMI monitor. When plugged back in power to troubleshoot, the system booted into HAOS 14.1 -- and Settings update was offering 14.2 Update again.

FWIW, rpi5 4GB HAOS on m.2 NVMe SSD

[idcrook]

HAOS seems to know it was "bad"

Update: When plugged back in power to troubleshoot, the system booted into HAOS 14.1 -- and Settings update was offering 14.2 Update again.

FWIW, rpi5 4GB HAOS on m.2 NVMe SSD

ha > os info 
board: rpi5-64
boot: A
boot_slots:
  A:
    state: booted 
    status: good 
    version: "14.1"
  B:
    state: inactive
    status: bad 
    version: "14.2"
data_disk: INTEL-SSDPEKNUO10TZ-PHKA12630BBY1P0B
update_available: true 
version: "14.1"
version_latest: "14.2"

[dengi76]

Hello! I want to say that I have the same thing on my virtual box!

[VHC2020]

i get this afther update en try to restart in any way normal of save

Failed to perform the action homeassistant/restart. The system cannot restart because the configuration is not valid: Error loading /config/configuration.yaml: while scanning for the next token found character '%' that cannot start any token in "/config/sensors.yaml", line 8, column 12

i did not chnage any thing there just a update, is lucky my test server main server will not be updated so far

[nodinosaur]

I am also getting this issue, RPi5
(I have tried to apply the change twice failed both times)

[dengi76]

I managed to update on the fourth try!

[larrybml]

How did you managed to update? I can't connect to HA RPi5 anymore.

[dengi76]

Three times in a row we pressed update, and all three times, after rebooting, the old version remained. After the fourth attempt to update, HA rebooted and the new version 14.2 was installed

[larrybml]

OK, thank you!

[petepall]

I have a home assistant green and am no longer able to get it to boot after the 14.2 OS update.
I don't have a HDMI monitor available to check the issue how can I get this to work again?

Update: After 4 reboots of the system I have access again and system returned back to OS14.1

[larrybml]

Same here, after 3 failed tries to update, I gave up, still on 14.1 , HA OS installed on an RPi5.

[LANNELONGUE]

Pareil ici, après 3 essais ratés de mise à jour, j'ai abandonné, toujours sur 14.1 (14.1), HA OS installé sur un RPi5.

[claytonjcoleman]

Pushed the button on 14.2, failed to come up. I'm remote so could not see anything on a screen. IP was not offered from DHCP from the router so not pingable. Made me consider a cloud connected switch to reboot this. Asked somone at home to pull power and it came back up -my octopus rates card, restored and all back to 14.1.

[DieterC1984]

Three times in a row we pressed update, and all three times, after rebooting, the old version remained. After the fourth attempt to update, HA rebooted and the new version 14.2 was installed

Same for me. RPI5

[VHC2020]

I also rebooted Hard cut power off en on, came in a recovery mode every thing was back core update and os update, but had problems with the setting sensors.yaml i trun it of and reboot system was ok one version lower updates are there and i don't touch them, now fix my sensors.yaml who i did not touch when i was updaten pretty strange.

[linux4life798]

For the people experiencing the Raspberry Pi not booting, after a system reboot (have to do a hard power-off and power-on to recover). It is likely #3740.

[jhalldn]

Seems like there's many ppl having issues with the upgrade to 14.2 - also me too. I would like to see a new build or version that is possible to upgrade without any issues. I'm stay on 14.1 After a faulty attempt to do 14.2.

[anilkusaksiz]

I'm running HA on VirtualBox on Windows 11.

Upgraded to 14.2 today and it started crashing every few minutes. Update process was also very troubled, machine didn't come online several times and I couldn't reach it for more than 20 minutes.

Won't recommend updating to 14.2

In case if you need to roll back to 14.1:

ha os update --version "14.1"

[villasenor]

@sairon FYI I know you are busy, but thought I'd bump this to the top of your notifications because this looks like a breaking regression, and seems different than past issues because it is happening on Home Assistant Green and VMs (not just RPI). I haven't experienced this yet because I haven't done the update yet, but would it be worth rolling back the release until the root cause is determined?

[spencermacca]

please fix hoe assistat

[ManiakNL]

please fix hoe assistat

I think that is another service buddy :)

[spencermacca]

please fix hoe assistat

I think that is another service buddy :)

typo my bad

[sairon]

@sairon FYI I know you are busy, but thought I'd bump this to the top of your notifications because this looks like a breaking regression, and seems different than past issues because it is happening on Home Assistant Green and VMs (not just RPI). I haven't experienced this yet because I haven't done the update yet, but would it be worth rolling back the release until the root cause is determined?

@villasenor While we can't rule out anything, I don't feel there is a strong indication about a breaking regression affecting more platforms. Of course, the kernel update could have introduced some issues for particular hypervisors or Green as well but many other systems are running fine and I am not able to reproduce anything similar on my end either (upgraded Green couple of times in the morning and now it's running for couple of hours straight). Basically, with ~1M installs, every update which results in a host reboot wakes up some gremlins that were waiting for their prime time - if there's a real issue, we need to figure out the pattern, and we need logs for that.

What I unfortunately can't deny is that there's an issue with Raspberry Pi 5, it's been reported in couple of threads already and some summary can be found in post by @linux4life798. However, that is likely an intermittent problem that couldn't have been introduced by 14.2, as there are simply no changes between 14.1 and 14.2 that could have caused it. So far the common pattern is that it happens on RPi 5 running from NVMe on unofficial NVMe HATs. But being intermittent, it affects different people than before. And also, I still need to be able to successfully reproduce it here, I don't have any of the problematic HATs (yet) but with the official M.2 HAT+ or when running from an SD card, there are no issues.

---

For everyone, spamming issues with "me too" reports doesn't help anyone. If you want to comment, at least provide more details about your setup, i.e. is it running from an SD card or an NVMe? What HATs and peripherals are connected to it? Can you connect an HDMI display and check what's there? The more information, the better.

[bigskookum]

How can I produce logs? My update failed on x86 and rolled itself back to 14.1.

[ManiakNL]

@sairon FYI I know you are busy, but thought I'd bump this to the top of your notifications because this looks like a breaking regression, and seems different than past issues because it is happening on Home Assistant Green and VMs (not just RPI). I haven't experienced this yet because I haven't done the update yet, but would it be worth rolling back the release until the root cause is determined?

@villasenor While we can't rule out anything, I don't feel there is a strong indication about a breaking regression affecting more platforms. Of course, the kernel update could have introduced some issues for particular hypervisors or Green as well but many other systems are running fine and I am not able to reproduce anything similar on my end either (upgraded Green couple of times in the morning and now it's running for couple of hours straight). Basically, with ~1M installs, every update which results in a host reboot wakes up some gremlins that were waiting for their prime time - if there's a real issue, we need to figure out the pattern, and we need logs for that.

What I unfortunately can't deny is that there's an issue with Raspberry Pi 5, it's been reported in couple of threads already and some summary can be found in post by @linux4life798. However, that is likely an intermittent problem that couldn't have been introduced by 14.2, as there are simply no changes between 14.1 and 14.2 that could have caused it. So far the common pattern is that it happens on RPi 5 running from NVMe on unofficial NVMe HATs. But being intermittent, it affects different people than before. And also, I still need to be able to successfully reproduce it here, I don't have any of the problematic HATs (yet) but with the official M.2 HAT+ or when running from an SD card, there are no issues.

For everyone, spamming issues with "me too" reports doesn't help anyone. If you want to comment, at least provide more details about your setup, i.e. is it running from an SD card or an NVMe? What HATs and peripherals are connected to it? Can you connect an HDMI display and check what's there? The more information, the better.

I have the following connected to my RPi-5

SSD connected using a SATA to USB3 cable, the OS is installed on the SATA drive, the PI does not have a SD card inserted.
1 Zigbee Dongle (Conbee II)
1 Zigbee Dongle (SONOFF ZigBee 3.0 USB Dongle Plus)

Edit, i yoloed it and tried to install the update again.
It finished in a couple of minutes with out problem.
I have not changed anything to the PI nor homeassistent in the meanwhile.
I guess for me this problem resolved it self. Everything seems to be working just fine, including my zigbee devices.

Now running on:

Core 2025.1.4
Supervisor 2024.12.3
Operating System 14.2
Frontend 20250109.2

[spencermacca]

For everyone, spamming issues with "me too" reports doesn't help anyone. If you want to comment, at least provide more details about your setup, i.e. is it running from an SD card or an NVMe? What HATs and peripherals are connected to it? Can you connect an HDMI display and check what's there? The more information, the better.

out of the box raspi5 with out of the box raspi power supply. could be adguard related tho? this happened like immediately after I setup adguard

[TechSysEng]

Same issues as other are stating here on a Pi5. I tried 3 times to update from 14.1 to 14.2. After the update it reloads and takes a good 30 minutes or more to come back up at which time I get SSL handshake errors. I then hard power cycle the Pi and then it will come back up, and still on 14.1. No custom integrations, all basic things.

I use a base Pi, stock Pi 5 power supply, no hats on the Pi, using a regular micro sd card. Pi is 8gb, plenty of space, easily replicated the issue 3 times.

Core 2025.1.4
Supervisor 2024.12.3
Operating System 14.1
Frontend 20250109.2

2025-01-27 21:08:22.818 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/aiohttp/client_proto.py", line 92, in connection_lost
uncompleted = self._parser.feed_eof()
^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 508, in aiohttp._http_parser.HttpParser.feed_eof
aiohttp.http_exceptions.TransferEncodingError: 400, message:
Not enough data for satisfy transfer length header.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 480, in _handle_request
resp = await request_handler(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 569, in _handle
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
aiohttp.client_exceptions.ClientPayloadError: Response payload is not completed: <TransferEncodingError: 400, message='Not enough data for satisfy transfer length header.'>
2025-01-27 21:08:22.821 ERROR (MainThread) [supervisor.api] Failed to get supervisor logs using advanced_logs API
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/aiohttp/client_proto.py", line 92, in connection_lost
uncompleted = self._parser.feed_eof()
aiohttp.client_exceptions.ClientPayloadError: Response payload is not completed: <TransferEncodingError: 400, message='Not enough data for satisfy transfer length header.'>
s6-rc: info: service legacy-services: stopping
2025-01-27 21:08:23.236 INFO (MainThread) [supervisor.misc.scheduler] Shutting down scheduled tasks
2025-01-27 21:08:23.237 INFO (MainThread) [supervisor.docker.monitor] Stopped docker events monitor
2025-01-27 21:08:23.238 INFO (MainThread) [supervisor.api] Stopping API on 172.30.32.2
[02:08:23] INFO: Watchdog restart after closing
2025-01-27 21:08:23.247 INFO (MainThread) [supervisor.hardware.monitor] Stopped Supervisor hardware monitor
2025-01-27 21:08:23.250 INFO (MainThread) [supervisor.dbus.manager] Closed conection to system D-Bus.
2025-01-27 21:08:23.252 INFO (MainThread) [supervisor.core] Supervisor is down - 0
2025-01-27 21:08:23.253 INFO (MainThread) [main] Closing Supervisor
[02:08:23] WARNING: Halt Supervisor
[02:08:23] INFO: Supervisor restart after closing

[mickhei]

Same issue here on Raspi Pi5 8GB with Raspberry Pi SSD Kit with 512GB (Raspberry Pi M.2 HAT+ with Raspberry Pi NVMe SSD). No SD card connected. Nothing unofficial from my point of view. Coming from 14.1. Installed 14.2 and the machine didn't come back. Cut the power and waited for some minutes and the machine came back to 14.1 with the option to install 14.2 again.

[sairon]

Anyone with RPi 5 update failing, can you please post the output of ha host logs -v -n100 -t rauc and ha host logs -v -b-1 -t hassio_supervisor obtained right after the update fails and boots back to the old version? The cause for some reboot failures was identified and fixed in #3842, I need to confirm if it's anyhow related, because this one I'm not able to reproduce.

For anyone with issues on other platforms than Raspberry Pi 5 - most likely we're talking about a different issue, let's track it separately and keep this one strictly for RPi 5.

[TechSysEng]

@sairon those logs below per your request. The second produced no output

[mickhei]

[sairon]

@TechSysEng @mickhei I should have emphasized the "right after the update" part, the times are somewhat too far in the past. Also make sure to properly add all flags and not clip anything from the output.

In the case when the second command didn't produce anything, what's the output of ha host logs -v -b-1 -n 100?

[mickhei]

@sairon Sorry, I thought you meant from the point where the update was tried. That was on the 27.01.2025 in my case. No more data for the 27.01.

[TechSysEng]

@sairon I did it 3 times the other night so those are all the logs I have. If I get brave and want to risk it being down for another night, maybe I'll try again to get fresh logs when i get home frm work and try it again. nothing was missing from my screenshot as far as the output goes from the first command. I do see in that screenshot there is a line referencing 14.2. If there is data there, (pardon my ignorance) regardless of from when and the timestamps, it still provides no value? As far as the first command goes.

The second command gives no output or error, just back to a new line

The output of ha host logs -v -b-1 -n 100 is probably going to be too old as it only goes back a day.

[TechSysEng]

@sairon I got home and went to update to break it for the cause. :) I updated and this 4th try worked. VERY bizarre. Regardless, below is the FULL output from your original 2 requested commands. Not sure if it helps anymore since it worked this time. This was very shortly after it updated, I pulled these. Maybe it still helps.

[core-ssh ~]$ ha host logs -v -n100 -t rauc
2025-01-28 01:44:43.116 homeassistant rauc[2288]: tryboot set-state B good
2025-01-28 01:44:43.124 homeassistant rauc[2291]: tryboot get-state A
2025-01-28 01:44:43.124 homeassistant rauc[2291]: returning bad
2025-01-28 01:44:43.126 homeassistant rauc[2292]: tryboot get-state B
2025-01-28 01:44:43.127 homeassistant rauc[2292]: returning good
2025-01-28 01:45:55.766 homeassistant rauc[4385]: tryboot get-state A
2025-01-28 01:45:55.766 homeassistant rauc[4385]: returning bad
2025-01-28 01:45:55.768 homeassistant rauc[4387]: tryboot get-state B
2025-01-28 01:45:55.768 homeassistant rauc[4387]: returning good
2025-01-28 02:06:35.205 homeassistant rauc[530]: input bundle: /mnt/data/supervisor/tmp/hassos-14.2.raucb
2025-01-28 02:06:35.269 homeassistant rauc[6930]: tryboot set-state A bad
2025-01-28 02:07:34.998 homeassistant rauc[7047]: tryboot set-primary A
2025-01-28 12:23:55.304 homeassistant rauc[1816]: tryboot get-state A
2025-01-28 12:23:55.304 homeassistant rauc[1816]: returning bad
2025-01-28 12:23:55.306 homeassistant rauc[1818]: tryboot get-state B
2025-01-28 12:23:55.307 homeassistant rauc[1818]: returning good
2025-01-28 12:23:57.970 homeassistant rauc[2272]: tryboot set-primary B
2025-01-28 12:23:58.014 homeassistant rauc[2285]: tryboot set-state B good
2025-01-28 12:23:58.022 homeassistant rauc[2288]: tryboot get-state A
2025-01-28 12:23:58.022 homeassistant rauc[2288]: returning bad
2025-01-28 12:23:58.024 homeassistant rauc[2289]: tryboot get-state B
2025-01-28 12:23:58.024 homeassistant rauc[2289]: returning good
2025-01-28 12:25:12.322 homeassistant rauc[4380]: tryboot get-state A
2025-01-28 12:25:12.322 homeassistant rauc[4380]: returning bad
2025-01-28 12:25:12.323 homeassistant rauc[4382]: tryboot get-state B
2025-01-28 12:25:12.323 homeassistant rauc[4382]: returning good
2025-01-28 14:31:52.284 homeassistant rauc[14975]: tryboot get-state A
2025-01-28 14:31:52.284 homeassistant rauc[14975]: returning bad
2025-01-28 14:31:52.286 homeassistant rauc[14977]: tryboot get-state B
2025-01-28 14:31:52.286 homeassistant rauc[14977]: returning good
2025-01-28 16:38:32.811 homeassistant rauc[25092]: tryboot get-state A
2025-01-28 16:38:32.811 homeassistant rauc[25092]: returning bad
2025-01-28 16:38:32.813 homeassistant rauc[25094]: tryboot get-state B
2025-01-28 16:38:32.813 homeassistant rauc[25094]: returning good
2025-01-28 18:45:13.264 homeassistant rauc[34936]: tryboot get-state A
2025-01-28 18:45:13.264 homeassistant rauc[34936]: returning bad
2025-01-28 18:45:13.266 homeassistant rauc[34938]: tryboot get-state B
2025-01-28 18:45:13.266 homeassistant rauc[34938]: returning good
2025-01-28 20:51:53.706 homeassistant rauc[44172]: tryboot get-state A
2025-01-28 20:51:53.706 homeassistant rauc[44172]: returning bad
2025-01-28 20:51:53.708 homeassistant rauc[44174]: tryboot get-state B
2025-01-28 20:51:53.708 homeassistant rauc[44174]: returning good
2025-01-28 22:58:34.249 homeassistant rauc[54131]: tryboot get-state A
2025-01-28 22:58:34.249 homeassistant rauc[54131]: returning bad
2025-01-28 22:58:34.251 homeassistant rauc[54133]: tryboot get-state B
2025-01-28 22:58:34.251 homeassistant rauc[54133]: returning good
2025-01-29 01:05:14.681 homeassistant rauc[64054]: tryboot get-state A
2025-01-29 01:05:14.681 homeassistant rauc[64054]: returning bad
2025-01-29 01:05:14.683 homeassistant rauc[64056]: tryboot get-state B
2025-01-29 01:05:14.683 homeassistant rauc[64056]: returning good
2025-01-29 03:11:55.135 homeassistant rauc[73304]: tryboot get-state A
2025-01-29 03:11:55.135 homeassistant rauc[73304]: returning bad
2025-01-29 03:11:55.138 homeassistant rauc[73306]: tryboot get-state B
2025-01-29 03:11:55.138 homeassistant rauc[73306]: returning good
2025-01-29 05:18:35.578 homeassistant rauc[83061]: tryboot get-state A
2025-01-29 05:18:35.578 homeassistant rauc[83061]: returning bad
2025-01-29 05:18:35.579 homeassistant rauc[83063]: tryboot get-state B
2025-01-29 05:18:35.580 homeassistant rauc[83063]: returning good
2025-01-29 07:25:16.021 homeassistant rauc[92841]: tryboot get-state A
2025-01-29 07:25:16.021 homeassistant rauc[92841]: returning bad
2025-01-29 07:25:16.023 homeassistant rauc[92843]: tryboot get-state B
2025-01-29 07:25:16.023 homeassistant rauc[92843]: returning good
2025-01-29 09:31:56.461 homeassistant rauc[102147]: tryboot get-state A
2025-01-29 09:31:56.461 homeassistant rauc[102147]: returning bad
2025-01-29 09:31:56.463 homeassistant rauc[102149]: tryboot get-state B
2025-01-29 09:31:56.463 homeassistant rauc[102149]: returning good
2025-01-29 11:38:36.911 homeassistant rauc[110671]: tryboot get-state A
2025-01-29 11:38:36.911 homeassistant rauc[110671]: returning bad
2025-01-29 11:38:36.912 homeassistant rauc[110673]: tryboot get-state B
2025-01-29 11:38:36.912 homeassistant rauc[110673]: returning good
2025-01-29 13:45:17.365 homeassistant rauc[119866]: tryboot get-state A
2025-01-29 13:45:17.365 homeassistant rauc[119866]: returning bad
2025-01-29 13:45:17.367 homeassistant rauc[119868]: tryboot get-state B
2025-01-29 13:45:17.367 homeassistant rauc[119868]: returning good
2025-01-29 15:51:57.805 homeassistant rauc[128877]: tryboot get-state A
2025-01-29 15:51:57.805 homeassistant rauc[128877]: returning bad
2025-01-29 15:51:57.806 homeassistant rauc[128879]: tryboot get-state B
2025-01-29 15:51:57.806 homeassistant rauc[128879]: returning good
2025-01-29 17:58:38.265 homeassistant rauc[138040]: tryboot get-state A
2025-01-29 17:58:38.265 homeassistant rauc[138040]: returning bad
2025-01-29 17:58:38.267 homeassistant rauc[138042]: tryboot get-state B
2025-01-29 17:58:38.267 homeassistant rauc[138042]: returning good
2025-01-29 19:29:47.210 homeassistant rauc[531]: input bundle: /mnt/data/supervisor/tmp/hassos-14.2.raucb
2025-01-29 19:29:47.277 homeassistant rauc[144763]: tryboot set-state A bad
2025-01-29 19:30:41.754 homeassistant rauc[144844]: tryboot set-primary A
2025-01-29 19:32:19.622 homeassistant rauc[1764]: tryboot get-state A
2025-01-29 19:32:19.625 homeassistant rauc[1764]: returning bad
2025-01-29 19:32:19.627 homeassistant rauc[1766]: tryboot get-state B
2025-01-29 19:32:19.627 homeassistant rauc[1766]: returning good
2025-01-29 19:32:22.870 homeassistant rauc[2223]: tryboot set-primary A
2025-01-29 19:32:22.914 homeassistant rauc[2236]: tryboot set-state A good
2025-01-29 19:32:22.933 homeassistant rauc[2236]: Committing tryboot state to primary boot
2025-01-29 19:32:22.963 homeassistant rauc[2258]: tryboot get-state A
2025-01-29 19:32:22.963 homeassistant rauc[2258]: returning good
2025-01-29 19:32:22.965 homeassistant rauc[2259]: tryboot get-state B
2025-01-29 19:32:22.965 homeassistant rauc[2259]: returning good
2025-01-29 19:33:32.280 homeassistant rauc[4595]: tryboot get-state A
2025-01-29 19:33:32.280 homeassistant rauc[4595]: returning good
2025-01-29 19:33:32.282 homeassistant rauc[4597]: tryboot get-state B
2025-01-29 19:33:32.282 homeassistant rauc[4597]: returning good

[core-ssh ~]$ ha host logs -v -b-1 -t hassio_supervisor
2025-01-29 19:31:31.730 homeassistant hassio_supervisor[626]: File "/usr/src/supervisor/supervisor/utils/systemd_journal.py", line 80, in journal_logs_reader
2025-01-29 19:31:31.730 homeassistant hassio_supervisor[626]: line = await resp.content.readuntil(b"\n")
2025-01-29 19:31:31.730 homeassistant hassio_supervisor[626]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-29 19:31:31.730 homeassistant hassio_supervisor[626]: File "/usr/local/lib/python3.12/site-packages/aiohttp/streams.py", line 386, in readuntil
2025-01-29 19:31:31.730 homeassistant hassio_supervisor[626]: await self._wait("readuntil")
2025-01-29 19:31:31.730 homeassistant hassio_supervisor[626]: File "/usr/local/lib/python3.12/site-packages/aiohttp/streams.py", line 347, in _wait
2025-01-29 19:31:31.730 homeassistant hassio_supervisor[626]: await waiter
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: aiohttp.client_exceptions.ClientPayloadError: Response payload is not completed: <TransferEncodingError: 400, message='Not enough data for satisfy transfer length header.'>
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: 2025-01-29 14:31:31.690 ERROR (MainThread) [aiohttp.server] Error handling request
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: Traceback (most recent call last):
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: File "/usr/local/lib/python3.12/site-packages/aiohttp/client_proto.py", line 92, in connection_lost
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: uncompleted = self._parser.feed_eof()
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: ^^^^^^^^^^^^^^^^^^^^^^^
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: File "aiohttp/_http_parser.pyx", line 508, in aiohttp._http_parser.HttpParser.feed_eof
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: aiohttp.http_exceptions.TransferEncodingError: 400, message:
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: Not enough data for satisfy transfer length header.
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]:
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: The above exception was the direct cause of the following exception:
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]:
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: Traceback (most recent call last):
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 480, in _handle_request
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: resp = await request_handler(request)
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 569, in _handle
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: return await handler(request)
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: ^^^^^^^^^^^^^^^^^^^^^^
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 117, in impl
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: return await handler(request)
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: ^^^^^^^^^^^^^^^^^^^^^^
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: File "/usr/src/supervisor/supervisor/api/middleware/security.py", line 199, in block_bad_requests
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: return await handler(request)
2025-01-29 19:31:31.731 homeassistant hassio_supervisor[626]: ^^^^^^^^^^^^^^^^^^^^^^
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: File "/usr/src/supervisor/supervisor/api/middleware/security.py", line 215, in system_validation
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: return await handler(request)
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: ^^^^^^^^^^^^^^^^^^^^^^
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: File "/usr/src/supervisor/supervisor/api/middleware/security.py", line 285, in token_validation
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: return await handler(request)
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: ^^^^^^^^^^^^^^^^^^^^^^
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: File "/usr/src/supervisor/supervisor/api/middleware/security.py", line 298, in core_proxy
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: return await handler(request)
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: ^^^^^^^^^^^^^^^^^^^^^^
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: File "/usr/src/supervisor/supervisor/api/utils.py", line 104, in wrap_api
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: msg_data = await method(api, *args, **kwargs)
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: File "/usr/src/supervisor/supervisor/api/host.py", line 278, in advanced_logs
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: return await self.advanced_logs_handler(request, identifier, follow)
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: File "/usr/src/supervisor/supervisor/api/host.py", line 257, in advanced_logs_handler
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: async for cursor, line in journal_logs_reader(resp, log_formatter):
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: File "/usr/src/supervisor/supervisor/utils/systemd_journal.py", line 80, in journal_logs_reader
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: line = await resp.content.readuntil(b"\n")
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: File "/usr/local/lib/python3.12/site-packages/aiohttp/streams.py", line 386, in readuntil
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: await self._wait("readuntil")
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: File "/usr/local/lib/python3.12/site-packages/aiohttp/streams.py", line 347, in _wait
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: await waiter
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: aiohttp.client_exceptions.ClientPayloadError: Response payload is not completed: <TransferEncodingError: 400, message='Not enough data for satisfy transfer length header.'>
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: 2025-01-29 14:31:31.692 ERROR (MainThread) [supervisor.api] Failed to get supervisor logs using advanced_logs API
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: Traceback (most recent call last):
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: File "/usr/local/lib/python3.12/site-packages/aiohttp/client_proto.py", line 92, in connection_lost
2025-01-29 19:31:31.732 homeassistant hassio_supervisor[626]: uncompleted = self._parser.feed_eof()
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]: ^^^^^^^^^^^^^^^^^^^^^^^
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]: File "aiohttp/_http_parser.pyx", line 508, in aiohttp._http_parser.HttpParser.feed_eof
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]: aiohttp.http_exceptions.TransferEncodingError: 400, message:
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]: Not enough data for satisfy transfer length header.
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]:
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]: The above exception was the direct cause of the following exception:
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]:
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]: Traceback (most recent call last):
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]: File "/usr/src/supervisor/supervisor/api/init.py", line 403, in get_supervisor_logs
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]: return await self._api_host.advanced_logs_handler(
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]: File "/usr/src/supervisor/supervisor/api/host.py", line 257, in advanced_logs_handler
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]: async for cursor, line in journal_logs_reader(resp, log_formatter):
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]: File "/usr/src/supervisor/supervisor/utils/systemd_journal.py", line 80, in journal_logs_reader
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]: line = await resp.content.readuntil(b"\n")
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]: File "/usr/local/lib/python3.12/site-packages/aiohttp/streams.py", line 386, in readuntil
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]: await self._wait("readuntil")
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]: File "/usr/local/lib/python3.12/site-packages/aiohttp/streams.py", line 347, in _wait
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]: await waiter
2025-01-29 19:31:31.733 homeassistant hassio_supervisor[626]: aiohttp.client_exceptions.ClientPayloadError: Response payload is not completed: <TransferEncodingError: 400, message='Not enough data for satisfy transfer length header.'>
2025-01-29 19:31:32.244 homeassistant hassio_supervisor[626]: s6-rc: info: service legacy-services: stopping
2025-01-29 19:31:32.281 homeassistant hassio_supervisor[626]: [19:31:32] INFO: Watchdog restart after closing
2025-01-29 19:31:32.282 homeassistant hassio_supervisor[626]: 2025-01-29 14:31:32.282 INFO (MainThread) [supervisor.misc.scheduler] Shutting down scheduled tasks
2025-01-29 19:31:32.283 homeassistant hassio_supervisor[626]: 2025-01-29 14:31:32.283 INFO (MainThread) [supervisor.docker.monitor] Stopped docker events monitor
2025-01-29 19:31:32.313 homeassistant hassio_supervisor[626]: 2025-01-29 14:31:32.312 INFO (MainThread) [supervisor.api] Stopping API on 172.30.32.2
2025-01-29 19:31:32.324 homeassistant hassio_supervisor[626]: 2025-01-29 14:31:32.323 INFO (MainThread) [supervisor.hardware.monitor] Stopped Supervisor hardware monitor
2025-01-29 19:31:32.327 homeassistant hassio_supervisor[626]: 2025-01-29 14:31:32.327 INFO (MainThread) [supervisor.dbus.manager] Closed conection to system D-Bus.
2025-01-29 19:31:32.331 homeassistant hassio_supervisor[626]: 2025-01-29 14:31:32.330 INFO (MainThread) [supervisor.core] Supervisor is down - 0
2025-01-29 19:31:32.332 homeassistant hassio_supervisor[626]: 2025-01-29 14:31:32.332 INFO (MainThread) [main] Closing Supervisor
2025-01-29 19:31:32.859 homeassistant hassio_supervisor[626]: [19:31:32] WARNING: Halt Supervisor
2025-01-29 19:31:32.862 homeassistant hassio_supervisor[626]: [19:31:32] INFO: Supervisor restart after closing
2025-01-29 19:31:32.864 homeassistant hassio_supervisor[626]: s6-rc: info: service legacy-services successfully stopped
2025-01-29 19:31:32.864 homeassistant hassio_supervisor[626]: s6-rc: info: service legacy-cont-init: stopping
2025-01-29 19:31:32.869 homeassistant hassio_supervisor[626]: s6-rc: info: service legacy-cont-init successfully stopped
2025-01-29 19:31:32.869 homeassistant hassio_supervisor[626]: s6-rc: info: service fix-attrs: stopping
2025-01-29 19:31:32.870 homeassistant hassio_supervisor[626]: s6-rc: info: service fix-attrs successfully stopped
2025-01-29 19:31:32.870 homeassistant hassio_supervisor[626]: s6-rc: info: service s6rc-oneshot-runner: stopping
2025-01-29 19:31:32.875 homeassistant hassio_supervisor[626]: s6-rc: info: service s6rc-oneshot-runner successfully stopped

[ktvanzwol]

@sairon attached output of both commands right after a failed upgrade. I had to power cycle the RPi5 to get it boot again.

host.log
supervisor.log

[erkr]

Just to chime in. I had to power cycle my fresh imaged (and a restored backup) RPi5-8Gb 3 times, the first time I rebooted the pi. That happened already with HAOS 14.1, not 14.2. The bug was probably introduced in 14.1