Is there a way to identify the reason and prevent bitcoin nodes from requesting to reindex the chainstate?

I see an error on a running node bitcoin v28.1.knots20250305

2026-02-22T08:59:28Z Checking all blk files are present...
2026-02-22T08:59:32Z Initializing chainstate Chainstate [ibd] @ height -1 (null)
2026-02-22T08:59:32Z Opening LevelDB in /mnt/btc/bitcoin/chainstate
2026-02-22T08:59:32Z Opened LevelDB successfully
2026-02-22T08:59:32Z Using obfuscation key for /mnt/btc/bitcoin/chainstate: 1d24e3daf440ae13
2026-02-22T08:59:32Z : Error initializing block database.
Please restart with -reindex or -reindex-chainstate to recover.
: Error initializing block database.
Please restart with -reindex or -reindex-chainstate to recover.
2026-02-22T08:59:32Z [error] Aborted block database rebuild. Exiting.
2026-02-22T08:59:32Z Shutdown: In progress...
2026-02-22T08:59:32Z scheduler thread exit
2026-02-22T08:59:32Z Flushed fee estimates to fee_estimates.dat.
2026-02-22T08:59:33Z Shutdown: done

There was a reboot before this was first seen

Feb 21 13:08:44 btc bitcoind[1026]: 2026-02-21T13:08:44Z New outbound-full-relay v1 peer connected: version: 70016, blocks=937663, peer=33
Feb 21 13:09:04 btc bitcoind[1026]: 2026-02-21T13:09:04Z New outbound-full-relay v2 peer connected: version: 70016, blocks=937663, peer=35
-- Reboot --
Feb 21 14:29:48 btc systemd[1]: Started bitcoin.
Feb 21 14:29:50 btc bitcoind[1007]: 2026-02-21T14:29:50Z Bitcoin Knots version v28.1.knots20250305 (release build)

What is the cause of this error? Is there a way to prevent this?