Hey @DeKroniek you do have the json error in your recent log, so you do need to follow the troubleshooting provided above by smolgrrr
But you got unlucky and have another error in the Bitcoin Core log too - your first post also had the fatal/corrupt block error asking to reindex,
So you’d also need to do a reindex to fix that too with these steps:
Resolving Corrupted Blockchain Issues
You may see an error in your log that looks like this:
LevelDB read failure: Corruption: block checksum mismatch: /data/.bitcoin/chainstate/1066593.ldb
*The digits may be different, there may be another issue requesting you to reindex, or if you see a message that requires you to turn off an unpruned node specifically this could be unrelated (where you can’t use a pruned node to run applications that must be able to see the entire transaction history)
Resolving a corrupted blockchain is a time-consuming process. Depending on the size of the blockchain and the speed of your device, this process can take several days. It is important to be patient and not interrupt the process, as interrupting it may result in needing to restart the process from the beginning.
Connect to your Umbrel device by following the instructions in How to SSH into Umbrel on a Raspberry Pi or by accessing a terminal on your Linux machine.
Run the following command to open bitcoin.conf in a nano text editor. If you are on a Linux machine, you may need to replace ~ with the path to your installation directory, as described in Troubleshooting on Linux :sudo nano ~/umbrel/app-data/bitcoin/data/bitcoin/bitcoin.conf
Add the following line to the file:reindex=1
Save and exit the file by pressing CTRL+X, then Y, and then ENTER.
Restart your Bitcoin node by running the following command:sudo ~/umbrel/scripts/app restart bitcoin
Your Bitcoin node will now start the process of reindexing. You can monitor the reindexing progress of your node by accessing your Bitcoin Node app through the browser.
After your node is fully synced, follow the same steps to remove reindex=1 from the bitcoin.conf file and restart your Bitcoin Node. If you do not do this, then the lengthy process of reindexing will occur again the next time your node restarts.
Note: It may also take some time for dependant apps like Electrs to resume functioning after the reindex is the complete.
(I always want to remind to clarify above, once you add reindex, avoid rebooting until it’s complete at 100% or it will start over, then once complete you can remove reindex=1)
If you have any other issues let us know!