History not showing after reboot

I had to reboot my Ubuntu machine (HA is running as a snap). I notice there’s no history showing for times before the reboot. Looking through the logs, there are many errors but nothing mentioning ‘malformed database’ or anything that looks like database corruption.

Examples of errors:

Error handling request
07:39:01 – (ERROR) /snap/home-assistant-snap/574/lib/python3.11/site-packages/aiohttp/web_protocol.py - message first occurred at 2 October 2023 at 19:43:41 and shows up 20 times
[0xFD85:1:0x0b04]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>')]
06:48:58 – (WARNING) Zigbee Home Automation - message first occurred at 2 October 2023 at 13:07:11 and shows up 9 times
Error fetching version data: Error fetching version information from supervisor Cannot connect to host version.home-assistant.io:443 ssl:default [Temporary failure in name resolution]
5 October 2023 at 03:37:13 – (ERROR) Version

The .db file is quite large so I’m guessing it still contains all the history:

-rw-r--r-- 1 root root    19926 Oct  7 07:39 home-assistant.log
-rw-r--r-- 1 root root  2568466 Oct  2 11:59 home-assistant.log.1
-rw-r--r-- 1 root root        0 Oct  2 11:59 home-assistant.log.fault
-rw-r--r-- 1 root root 65916928 Oct  7 11:27 home-assistant_v2.db
-rw-r--r-- 1 root root    32768 Oct  7 11:36 home-assistant_v2.db-shm
-rw-r--r-- 1 root root  4445512 Oct  7 11:37 home-assistant_v2.db-wal

Is there a way to get the HA frontend to display the whole history? Or a way to check if the.db file really is intact?

The reboot was on 2 October.

You are using an unsupported installation method.

Yes I know although when I first installed HA, it appeared to be the accepted method on Ubuntu. It generally works very well so I’m puzzled why it isn’t officially supported. Either way, I can’t see that would have any impact on the database file.