# Blockchain won't fully sync after running latest update
**URL:** https://community.umbrel.com/t/blockchain-wont-fully-sync-after-running-latest-update/4250
**Category:** Support and Troubleshooting
**Created:** [October 24, 2021, 3:45am UTC](https://community.umbrel.com/t/blockchain-wont-fully-sync-after-running-latest-update/4250 "2021-10-24T03:45:21Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@danonthemoon](https://community.umbrel.com/u/danonthemoon)
#### Post date: [October 24, 2021, 3:45am UTC](https://community.umbrel.com/t/blockchain-wont-fully-sync-after-running-latest-update/4250/1 "2021-10-24T03:45:21Z")
My Umbrel node running on a Raspberry Pi 4 (8 GB/1TB SSD) no longer fully syncs. Instead, it gets to within a few blocks of the highest block and then reverts back to a much older block (2-3 days prior) and tries to sync again. It’s been doing this in an endless loop for over two weeks now. The problem began after updating to 0.4.4 and I had hoped 0.4.5 would fix the issue, but it has not.
Do I need to fully restore the node from the backup seed? I have over 20 Lightning channels (backed up) that are currently down. What’s the best way to fix this?
---
### Author:  [@DarthCoin](https://community.umbrel.com/u/DarthCoin)
#### Post date: [October 24, 2021, 8:50am UTC](https://community.umbrel.com/t/blockchain-wont-fully-sync-after-running-latest-update/4250/2 "2021-10-24T08:50:21Z")
Please check [Umbrel troubleshooting guide](http://community.umbrel.com/t/umbrel-troubleshooting-guide/3632)
No need to restore your node.
Could be:
- electrs is still indexing blocks (after 0.4.4 update electrs is re-indexing all blocks compacting the database, so be patient.
- some error line in your lnd.conf file (check the troubleshooting guide for that)
- check the logs see what is hanged.
---
### Author:  [@danonthemoon](https://community.umbrel.com/u/danonthemoon)
#### Post date: [November 2, 2021, 12:25pm UTC](https://community.umbrel.com/t/blockchain-wont-fully-sync-after-running-latest-update/4250/3 "2021-11-02T12:25:43Z")
Thanks. I solved it by doing a manual reindex of the blockchain and then installing the latest update from the repo. Everything is back to normal now.