Reboot of host outside of container causes unclean shutdown of Home Assistant container

[Baxxy13]

Describe the issue you are experiencing

This is a follow up to home-assistant/core#109343

When I restart my HA from outside the container, e.g. with reboot from the os-console, I always get the following messages.

2024-12-20 19:29:07.789 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
2024-12-20 19:29:07.852 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=530 from 2024-12-20 17:15:52.068267)

This also happens when I use “Restart” from the Proxmox UI on a Homeassistant VM.

If I use Settings -> System -> Hardware - Reboot System then I do not get the messages.

What operating system image do you use?

rpi4-64 (Raspberry Pi 4/400 64-bit OS)

What version of Home Assistant Operating System is installed?

14.1

Did the problem occur after upgrading the Operating System?

No

Hardware details

Raspberry Pi4B-2GB with USB3-SATA-SSD

Steps to reproduce the issue

1. reboot the system from os-console with reboot
2. see the warnings in the core-log

...

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

-

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

-

System information

System Information

version	core-2024.12.5
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.13.0
os_name	Linux
os_version	6.6.62-haos-raspi
arch	aarch64
timezone	Europe/Berlin
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	4999
Installed Version	2.0.1
Stage	running
Available Repositories	1496
Downloaded Repositories	7

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 14.1
update_channel	stable
supervisor_version	supervisor-2024.12.0
agent_version	1.6.0
docker_version	27.2.0
disk_total	219.4 GB
disk_used	8.5 GB
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization
board	rpi4-64
supervisor_api	ok
version_api	ok
installed_addons	File editor (5.8.0), Samba share (12.3.2), Node-RED (18.1.1), Mosquitto broker (6.4.1), Advanced SSH & Web Terminal (19.0.0), Portainer (2.24.1), RaspberryMatic CCU (snapshot) (3.79.6.20241220-bcf7eaf), Remote Backup (2024.6.0), DbStats (0.5.11)

Dashboards

dashboards	4
resources	3
views	1
mode	storage

Recorder

oldest_recorder_run	7. Dezember 2024 um 08:24
current_recorder_run	20. Dezember 2024 um 18:15
estimated_db_size	176.24 MiB
database_engine	sqlite
database_version	3.45.3

Additional information

I assume that it is a timing / timeout problem. That's why I did a simple stopwatch test.
Here are the results:

reboot from	to host reset	to cli	to fully started
os-console	24s	90s	165s
frontend	55s	120s	195s

We can see that the first section takes about 30s longer when I initiate the reboot via the frontend.
Of course, this doesn't necessarily mean anything, but it could be an indication of where to look further.
Anyway, I need a good guide to provide more information and useful logs here.