HAOS (baremetal/rpi4) won't boot headless after 2024.11.1

I’m running Home Assistant Operating System on a pi4. This morning there were a few updates including ESPHome (requiring my three Bluetooth proxies to be updated as well). Everything went well until the update for Home Assistant Operating System…

The update froze (seemed to freeze) as it often does, giving no feedback because, its rebooting, I surmise? This is “normal” except, this time, it never recovered. I slowly power cycled a dozen times and decided that this wasn’t going to recover on its own.

My next step was to move the pi4 across the office so I could hook-up a monitor and keyboard to it. Watching the monitor closely for signs of error, it booted up perfectly. I thought, YES!.. just a weird glitch, so I moved it back to its headless resting place and powered it up… Nothing!

I moved it back and gave it a monitor again and magic it boots first time. I’ve been running Home Assistant on this pi4 for about a year and a half, headless.

Am I missing something?

MrGrey.

Hello, I seem to have a similar issue. Not sure what you mean by ‘headless’, but my HA is running also on Pi4, and I just upgraded to 14.1 HA OS, and now, HA won’t start. PI does start, though, and I can ssh into it, and I can run all commands like ha resolution blablabla, but no way I can start HA application.

I never investigated how HA is structured within HA OS, so I do not know where to look for.

OS Version: Home Assistant OS 14.1
Home Assistant Core: 2024.12.4

Thanks

ha core logs shows the following logs:

services-up: info: copying legacy longrun home-assistant (no readiness notification)

s6-rc: info: service legacy-services successfully started

[13:18:09] INFO: Home Assistant Core finish process exit code 256

[13:18:09] INFO: Home Assistant Core finish process received signal 4

s6-rc: info: service legacy-services: stopping

s6-rc: info: service legacy-services successfully stopped

s6-rc: info: service legacy-cont-init: stopping

s6-rc: info: service legacy-cont-init successfully stopped

s6-rc: info: service fix-attrs: stopping

s6-rc: info: service fix-attrs successfully stopped

s6-rc: info: service s6rc-oneshot-runner: stopping

s6-rc: info: service s6rc-oneshot-runner successfully stopped

Does that ring a bell to anybody?

Ah, and I found a home-assistant.log.fault file, containing lots of:

Fatal Python error: Illegal instruction                                                         
                                                                                                
Thread 0x0000007f929fee58 (most recent call first):                                             
  File "/usr/local/lib/python3.13/logging/handlers.py", line 1523 in dequeue                    
  File "/usr/local/lib/python3.13/logging/handlers.py", line 1574 in _monitor                   
  File "/usr/local/lib/python3.13/threading.py", line 992 in run                                
  File "/usr/local/lib/python3.13/threading.py", line 1041 in _bootstrap_inner                  
  File "/usr/local/lib/python3.13/threading.py", line 1012 in _bootstrap                        
                                                                                                
Current thread 0x0000007f92fbae58 (most recent call first):                                     
  File "/usr/local/lib/python3.13/site-packages/yaml/constructor.py", line 49 in get_single_data
  File "/usr/local/lib/python3.13/site-packages/yaml/__init__.py", line 81 in load           
  File "/usr/src/homeassistant/homeassistant/util/yaml/loader.py", line 228 in _parse_yaml   
  File "/usr/src/homeassistant/homeassistant/util/yaml/loader.py", line 201 in parse_yaml    
  File "/usr/src/homeassistant/homeassistant/util/yaml/loader.py", line 168 in load_yaml     
  File "/usr/src/homeassistant/homeassistant/util/yaml/loader.py", line 186 in load_yaml_dict
  File "/usr/src/homeassistant/homeassistant/config.py", line 276 in load_yaml_config_file
  File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 58 in run                                                                         
  File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 92 in _worker                                                                     
  File "/usr/local/lib/python3.13/threading.py", line 992 in run                                                                                        
  File "/usr/local/lib/python3.13/threading.py", line 1041 in _bootstrap_inner                                                                          
  File "/usr/local/lib/python3.13/threading.py", line 1012 in _bootstrap                                                                                
                                                                                                                                                        
Thread 0x0000007f9e81e020 (most recent call first):                                                                                                     
  File "/usr/local/lib/python3.13/selectors.py", line 452 in select                                                                                     
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 1989 in _run_once                                                                       
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 679 in run_forever                                                                      
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 708 in run_until_complete                                                               
  File "/usr/src/homeassistant/homeassistant/runner.py", line 154 in run                                                                                
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 213 in main                                                                             
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 227 in <module>                                                                         
  File "<frozen runpy>", line 88 in _run_code                                                                                                           
  File "<frozen runpy>", line 198 in _run_module_as_main                                                                                                
                                                                                                                                                        
Extension modules: _cffi_backend, ciso8601, yaml._yaml, propcache._helpers_c, ulid_transform._ulid_impl, multidict._multidict, yarl._quoting_c, markupsa

You are much smarter than I @vbartro.

I mean running without keyboard and monitor.

After Holidays, I’ll try more. For now, it works with a “head” and I can leave it that way.

You are really smarter than I. I disable ssh because cli will only be used by people smarter than I.

I’m pretty sure things will be fixed. It’s better than last year with all of the ZHA failures.

Best wishes to everyone reading this.

MrGrey.

Hi All,

Just a note that I am also seeing this problem on a fresh install of HA on an PI 5. It boots fine with a usb keyboard attached, but not without.

Did you find any solution to your issue?

I forgot about this post and posted about it again, slap me. :smile:

I have no answer and no information except that Home Assistant will boot (for me) as long as I have a monitor and keyboard attached (hardwired) to my pi4 and it won’t start without it.

I can add that it started around 2024.11.x to 2024.12.1, not that, that helps any.

MrGrey.

Edit: Reflecting: (14.1) is 2024.11.1 so I’m changing heading to reflect that.