Never seen this before: home-assistant.log.fault

Configuration
1

Hundreds of lines of Python errors, nothing that I recognize.

The top:

Fatal Python error: Segmentation fault

Thread 0x00007f9419e69b30 (most recent call first):
  File "/usr/local/lib/python3.13/threading.py", line 363 in wait
  File "/usr/local/lib/python3.13/threading.py", line 659 in wait
  File "/usr/src/homeassistant/homeassistant/components/stream/__init__.py", line 468 in _run_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

Hundreds more similar to the above
And the tail:

Thread 0x00007fb1e0701b30 (most recent call first):
  File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 90 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

Current thread 0x00007fb1eac88b28 (most recent call first):
  File "/usr/local/lib/python3.13/site-packages/aioesphomeapi/client.py", line 395 in device_info
  File "/usr/src/homeassistant/homeassistant/util/async_.py", line 45 in create_eager_task
  File "/usr/src/homeassistant/homeassistant/components/esphome/manager.py", line 356 in _on_connnect
  File "/usr/src/homeassistant/homeassistant/components/esphome/manager.py", line 336 in on_connect
  File "/usr/local/lib/python3.13/site-packages/aioesphomeapi/reconnect_logic.py", line 210 in _try_connect
  File "/usr/local/lib/python3.13/site-packages/aioesphomeapi/reconnect_logic.py", line 297 in _connect_once_or_reschedule
  File "/usr/local/lib/python3.13/asyncio/events.py", line 89 in _run
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 2033 in _run_once
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 678 in run_forever
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 707 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, markupsafe._speedups, _brotli, aiohttp._http_writer, aiohttp._http_parser, aiohttp._websocket.mask, aiohttp._websocket.reader_c, frozenlist._frozenlist, _awscrt, charset_normalizer.md, simplejson._speedups, requests.packages.charset_normalizer.md, requests.packages.chardet.md, zeroconf._utils.time, zeroconf._dns, zeroconf._protocol.outgoing, zeroconf._protocol.incoming, zeroconf._cache, zeroconf._record_update, zeroconf._history, zeroconf._updates, zeroconf._services, zeroconf._utils.ipaddress, zeroconf._services.info, zeroconf._services.registry, zeroconf._handlers.answers, zeroconf._handlers.multicast_outgoing_queue, zeroconf._handlers.query_handler, zeroconf._handlers.record_manager, zeroconf._listener, zeroconf._services.browser, sqlalchemy.cyextension.collections, sqlalchemy.cyextension.immutabledict, sqlalchemy.cyextension.processors, sqlalchemy.cyextension.resultproxy, sqlalchemy.cyextension.util, greenlet._greenlet, fnv_hash_fast._fnv_impl, PIL._imaging, isal.igzip_lib, isal.isal_zlib, audioop._audioop, numpy._core._multiarray_umath, numpy.linalg._umath_linalg, cached_ipaddress.ipaddress, dbus_fast.signature, dbus_fast._private.marshaller, dbus_fast.message, dbus_fast.service, dbus_fast._private.address, dbus_fast.unpack, dbus_fast.message_bus, dbus_fast._private.unmarshaller, dbus_fast.aio.message_reader, bluetooth_data_tools.gap, bluetooth_data_tools._time_impl, bluetooth_data_tools._utils_impl, bluetooth_data_tools.utils, habluetooth.models, habluetooth.advertisement_tracker, habluetooth.manager, habluetooth.base_scanner, habluetooth.scanner, av._core, av.logging, av.bytesource, av.buffer, av.audio.format, av.enum, av.error, av.utils, av.option, av.descriptor, av.container.pyio, av.dictionary, av.format, av.stream, av.container.streams, av.sidedata.motionvectors, av.sidedata.sidedata, av.opaque, av.packet, av.container.input, av.container.output, av.container.core, av.codec.context, av.video.format, av.video.reformatter, av.plane, av.video.plane, av.video.frame, av.video.stream, av.codec.codec, av.frame, av.audio.layout, av.audio.plane, av.audio.frame, av.audio.stream, av.filter.pad, av.filter.link, av.filter.context, av.filter.graph, av.filter.filter, av.audio.resampler, av.audio.codeccontext, av.audio.fifo, av.bitstream, av.video.codeccontext, psutil._psutil_linux, psutil._psutil_posix, PIL._imagingft, cchardet._cchardet, lxml._elementpath, lxml.etree, evdev._input, evdev._ecodes, evdev._uinput, kasa_crypt._crypt_impl, google._upb._message, aioesphomeapi.client_callbacks, aioesphomeapi._frame_helper.base, aioesphomeapi._frame_helper.noise, aioesphomeapi._frame_helper.plain_text, aioesphomeapi.connection, grpc._cython.cygrpc, gpiod._ext, psycopg2._psycopg, PIL._imagingmath (total: 134)

This is the first time that I have ever needed to run ha core restart. Any clues what might have happened?

2

Your system storage is corrupt/dying.

3

That fits. My next remedy would be to flash another M.2 with HAOS and restore to a backup from yesterday.

4

Update.

Looking at the `home-assistant.log.1` file the last entry was: 
ValueError: Sensor sensor.glucose_and_trend has device class 'None', state class 'None' unit 'mmol' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: '161, Trend unknown' (<class 'str'>)

I searched the whole file for sensor.glcuose_and_trend and found it 7,516 times.

The sensor was created in Node Red, and not used anywhere, so it was easily deleted. However, I noticed that the function node that preceded the sensor node had some errors. I don’t know why Node Red didn’t complain when I deployed. I also deleted that node.

24-hours later the system is still running, so I have to wonder if the errors in the function node were accumulating until there was a segmentation error, crashing the core?