Database disk image is malformed

Hello. I am having issues with Core Lightning on my Raspiblitz node. I’m not savvy when it comes to these things. The reason for running a node was to support the separation of money and state :) I hope that won’t end up being a costly lesson (I’m worried about my funds).

Anyway, one day, out of the blue, Lightning stopped working. The info screen on the Raspiblitz just said "Lightning progress : prepare sync”. The debug logs gave me this: http://termbin.com/2mjm

I decided to setup a fresh node and restore from a rescue file, however now I’m getting “database disk image is malformed”.

sudo journalctl -fu lightningd gives me this:

Oct 25 17:55:37 raspberrypi systemd[1]: Starting lightningd.service - c-lightning daemon on mainnet...
Oct 25 17:55:37 raspberrypi cl.check.sh[729355]: ls: cannot access '/mnt/hdd/app-data/.lightning/bitcoin/lightning-rpc': No such file or directory
Oct 25 17:55:37 raspberrypi systemd[1]: lightningd.service: Can't open PID file /run/lightningd/lightningd.pid (yet?) after start-post: No such file or directory
Oct 25 17:55:43 raspberrypi systemd[1]: lightningd.service: Supervising process 729353 which is not our child. We'll most likely not notice when it exits.
Oct 25 17:55:43 raspberrypi systemd[1]: Started lightningd.service - c-lightning daemon on mainnet.
Oct 25 17:55:43 raspberrypi sh[729353]: Error executing statement: wallet/wallet.c:4310: DELETE FROM blocks WHERE height > ?: database disk image is malformed
Oct 25 17:55:44 raspberrypi systemd[1]: lightningd.service: Killing process 729353 (n/a) with signal SIGKILL.
Oct 25 17:55:44 raspberrypi systemd[1]: lightningd.service: Killing process 729353 (n/a) with signal SIGKILL.
Oct 25 17:55:44 raspberrypi systemd[1]: lightningd.service: Deactivated successfully.
Oct 25 17:55:44 raspberrypi systemd[1]: lightningd.service: Consumed 4.932s CPU time.

When I try to open Core Lightning Wallet Options in the Raspiblitz menu, I get “Failed to unlock the lightning wallet - giving up after 1 minute”.

I assume the database is corrupted. Is there anything I can attempt to do to try to fix the issue?

I do have a emergency.recover file, but I guess using that is an absolute last resort.

Any help is greatly appreciated.