I followed the steps downloading the new operating system and flashing my SD card for my Raspberry Pi 4. Before the update I had a minor issue with my node and allowed it to synch back to 100% with the bitcoin network.
After the new flash my apps showed up but bitcoin node will not finish “starting” and my synching appears to be stuck at 83%
tried looking at debug script “~/umbrel/scripts/debug” which showed I was still running 0.5.4 which seemed odd. tried reflashing several times but still same issues with bitcoin node app not starting. It’s been a while since I got into debugging my umbrel so any pointers to scripts and / or things to check out would be very helpful. Thanks
Could you please provide the logs for your Umbrel and the Bitcoin Node app? You can do so through the http://umbrel.local/ dashboard as well as using the terminal like you have done with the debug script.
You can also try running sudo journalctl -u umbrel.service which, at least on version 1.x, should provide you with additional information - if in the event the upgrade did succeed, but you’re seeing the wrong version being reported which can happen.
If you’d like me to clarify something or to walk you through the steps, do let me know.
I also added “reindex=1” to the bitcoin.conf file which finally got the Bitcoin Node application to have a “running” status.
There is still an issue where not after it started reindexing it reset to 0% again and restarted indexing and synching after maybe 10% synching was completed. The process seems to start loading the total number of blocks then confirming / synching from what I’ve observed (not super familiar with the process)
Thanks for being patient. It does look like you are on version 1.2.1 of umbrelOS so the debug script must be reporting the version incorrectly which sometimes happens after an upgrade.
With regard to your Bitcoin Node issue, could you provide the logs by right clicking the app icon and choosing “Troubleshoot”?
Also if you’re using any of the following apps or otherwise have any funds linked to your Umbrel, then it’s crucial to ensure any private keys or wallet passphrases are backed up in a secure location before attempting any fixes or troubleshooting steps.
I’m using SSH to go through things. I only have bitcoin and lightning on this machine. what files beyond the channel. I have the seed phrase created when I first started the node, but what else should I export beyond that to make sure I can rebuild if anything really goes wrong?
also I’m trying to relearn command line so I’m trying to do it all from SSH for instance:
Channel backup from cmd
scp umbrel@umbrel.local:~/umbrel/app-data/lightning/data/lnd/data/chain/bitcoin/mainnet/channel.backup C:\Users\User1\Downloads
Export debug log for bitcoin app
scp umbrel@umbrel.local:~/umbrel/app-data/bitcoin/data/bitcoin/debug.log C:\Users\User1\Downloads
So far I have been trying the following bits of code from other people encountering similar problems:
make sure files are moved to the location for the new version
sudo mv umbrel/app-data/bitcoin/data/bitcoin/peers.dat umbrel/app-data/bitcoin/data/bitcoin/peers.dat.bak
When I reindex or reindex-chainstate the problem I always encounter is something along these lines:
2024-10-05T11:05:01Z LevelDB read failure: Corruption: block checksum mismatch: /data/.bitcoin/chainstate/068357.ldb
2024-10-05T11:05:01Z Fatal LevelDB error: Corruption: block checksum mismatch: /data/.bitcoin/chainstate/068357.ldb
2024-10-05T11:05:01Z You can use -debug=leveldb to get more complete diagnostic messages
2024-10-05T11:05:01Z Fatal LevelDB error: Corruption: block checksum mismatch: /data/.bitcoin/chainstate/068357.ldb
which causes my reindexing to stall out and reset. usually this happens a little over 50% into the download which is very frustrating. I’m trying to do it again to and to be around or get the log from the 1st failure to see if there is anything else going on because this failure just goes on repeat once the reindexing stops/
Starting Umbrel v1.2.1