This is now the second time this has happened to me since I have switched to Knots:
After receiving the same error the first time, I reindexed the chainstate as per the log and patiently waited 12 days for my node to sync to 100%. Once it syncd, I restarted all my apps. Knots stops running and I get the same errors:
Ya. I suspect that. As of now I am reindexing the entire drive. Moving forward though I am periodically making a backup copy of the blockchain so if it bricks again I can start from a more recent place to avoid the 3 week process.
It shouldn’t take you more than 3 days if you are not running another node within the local network.
To increase the download speed, allocate 50%-80% of the unused ram that you see on your dashboard to dbcache in the submenu and restart. For instance, in a computer with 8GB ram, set this to 4096
Other overrides that will speed it up (but do these temporarily in the override section):
par=-1
banscore=10
listen=0
bantime=500
you can find some nodes to connect to manually to boost download sources by finding them at: Bitcoin Network Snapshot - Bitnodes , but you will have to do this several times as discovery is turned off.
You would add them in the override section like:
connect=51.81.56.15:8333
But you should do at least 5 of these especially if they are bandwidth limited
I was having this exact same issue and rebuilt the index at least three times. Finally I allocated more RAM to my VM (I am running umbrel in a Virtual machine).
As soon as I did that I have never had the issue again. I did throw a lot of RAM at it (24Gb to be exact) but I had a lot of spare RAM in the host.
Perhaps this might help the devs to identify the issue.
What is the memory usage on the desktop dashboard?
And what kind of storage the PI5 is using?
it could be either swap file allocation or disk i/o
What do you get when you run at the terminal: