Thanks in advance. I have a RPi 5 with 8G, and my power went out and now I have this error:
“[error] txindex: best block of the index not found. Please rebuild the index. Error: txindex: best block of the index not found. Please rebuild the index](/t/2025-07-09t1112z-error-txindex-best-block-of-the-index-not-found-please-rebuild-the-index-error-txindex-best-block-of-the-index-not-found-please-rebuild-the-index/23226)”
Hey @jharris9999, I might first suggest if you are running new on this to just uninstall Bitcoin Node apps and reinstall it easier. Just uninstall any dependent applications and let us know if there’s any issue there.
Analyzing your previous posts I noticed you mentioned you’re “Running a Raspi 5, with 8 GB, 2T hard drive attached via USB…” I am thinking you may want to make sure all these connections are secure for your Pi 5 in maybe a kit you got and you’re using the official Pi 5 Power Supply included in the official kit and it’s plugged in securely to a reliable power source. Any fluctuation of power here you will continue to have issues with corruptions.
Furthermore, the official FAQ here has removed some of the issues that were redundant in the past such as the peers.dat errors that was patched in the latest versions of Core and things like replacing the timechain manually or using a command to reindex which I believe is also an easier setting maybe somewhere in Bitcoin Node App too and its UI should usually be easily accessible to restart and things without needing to SSH in, and those I believe were removed as not necessary now as things have been improved with the older deprecated commands, after Umbrel’s impressive new umbreld refactor.
These were the previous commands, but before attempting again I might recommend instead @jharris9999 just try securing connections and re-installing (right click apps uninstall, reinstall), use offiical PSU if available and you can also open a Discord Support ticket to ask about any other specific errors maybe or @smolgrrr can hop in on reindex command advice i see the directory for me is ~/umbrel/app-data/bitcoin/data/bitcoin, anything further here are just for reference I don’t think may be needed here as just re-installing and installing will fix ur issue and sync again and end up saving you time… indexing though does not harm currently synced blocks but takes a while and sounds like you have an earlier corruption on a block I assume and we are currently on block 908428 as I type this , if you have something like a gigabit connection it shouldn’t take you more than ~24 hours…
All this after here is just referencing from the previous FAQ, as don’t see it in the newer one:
Resolving a corrupted blockchain is a time-consuming process if this persists (to keep running that). 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.
Previous steps from FAQ:
Connect to your Umbrel device by following the instructions in How to SSH into umbrelOS on Umbrel Home or Rasberry 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 ~/umbrel with the path to your installation directory, as described in Troubleshooting on Linux:sudo nano ~/umbrel/app-data/bitcoin/data/bitcoin/umbrel-bitcoin.conf
Add the following line to the file:reindex=1 or reindex-chainstate=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/reindex-chainstate=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.