# Fatal LevelDB error: IO error: /data/.bitcoin/indexes/txindex/300149.ldb: Invalid argument **URL:** \ **Category:** Support and Troubleshooting\ **Created:** [March 4, 2023, 3:51pm UTC](https://community.umbrel.com/t/fatal-leveldb-error-io-error-data-bitcoin-indexes-txindex-300149-ldb-invalid-argument/11720 "2023-03-04T15:51:11Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![hermsats](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/hermsats/32/3809_2.png) [@hermsats](https://community.umbrel.com/u/hermsats)\ **Post date:** [March 4, 2023, 3:51pm UTC](https://community.umbrel.com/t/fatal-leveldb-error-io-error-data-bitcoin-indexes-txindex-300149-ldb-invalid-argument/11720/1 "2023-03-04T15:51:11Z")
Hi all, My Bitcoin node is “running,” but not syncing and keeps dropping peers to 0. I have tried restarting, reflashing the SD, removing/backing up my peers file - but continue to get these errors: when running `tail -n 1000 /mnt/data/umbrel/app-data/bitcoin/data/bitcoin/debug.log` The only error I receive is ``` 2023-03-04T15:05:03Z Fatal LevelDB error: IO error: /data/.bitcoin/indexes/txindex/300149.ldb: Invalid argument 2023-03-04T15:05:03Z You can use -debug=leveldb to get more complete diagnostic messages ``` when running ``` ~/umbrel/scripts/debug ``` I get these errors from the Bitcoin App log ``` App logs -------- bitcoin Attaching to bitcoin_server_1, bitcoin_app_proxy_1, bitcoin_i2pd_daemon_1, bitcoin_bitcoind_1, bitcoin_tor_1 i2pd_daemon_1 | 15:14:09@182/ **error** - SAM: Read error: End of file i2pd_daemon_1 | 15:14:24@182/ **error** - Destination: Can't publish LeaseSet. Destination is not ready i2pd_daemon_1 | 15:14:37@182/ **error** - Destination: Can't publish LeaseSet. Destination is not ready i2pd_daemon_1 | 15:14:54@182/ **error** - SAM: Read error: End of file i2pd_daemon_1 | 15:15:16@182/ **error** - Destination: Can't publish LeaseSet. Destination is not ready i2pd_daemon_1 | 15:15:17@182/ **error** - Destination: Can't publish LeaseSet. Destination is not ready i2pd_daemon_1 | 15:15:24@182/ **error** - SAM: Read error: End of file i2pd_daemon_1 | 15:15:34@182/ **error** - Destination: Can't send LeaseSet request, no inbound tunnels found i2pd_daemon_1 | 15:15:34@182/ **error** - Destination: Can't send LeaseSet request, no outbound tunnels found i2pd_daemon_1 | 15:15:42@182/ **error** - Destination: Can't publish LeaseSet. Destination is not ready ``` I am a complete noob when it comes to linux. Thanks so much in advance! ---
**Author:** ![usernameisJim](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/usernameisjim/32/3309_2.png) [@usernameisJim](https://community.umbrel.com/u/usernameisJim)\ **Post date:** [April 6, 2023, 1:42pm UTC](https://community.umbrel.com/t/fatal-leveldb-error-io-error-data-bitcoin-indexes-txindex-300149-ldb-invalid-argument/11720/2 "2023-04-06T13:42:59Z")
Hey @hermsats if you’re still having this issue you can follow the steps under “Resolving Corrupted Blockchain Issues” in the Official FAQ here: [Official Umbrel Troubleshooting Guide and FAQ](http://community.umbrel.com/t/official-umbrel-troubleshooting-guide-and-faq/9873) If the issue persists please post the full debug log, as a note too when following the steps there avoid rebooting after adding the `reindex=1` line or else it will attempt to reindex after each reboot ---
**Author:** ![vpal](https://avatars.discourse-cdn.com/v4/letter/v/c4cdca/32.png) [@vpal](https://community.umbrel.com/u/vpal)\ **Post date:** [September 1, 2023, 6:32pm UTC](https://community.umbrel.com/t/fatal-leveldb-error-io-error-data-bitcoin-indexes-txindex-300149-ldb-invalid-argument/11720/3 "2023-09-01T18:32:06Z")
Hi @hermsats I am having the same problem as mentioned by you. Have you found a solution? thank you ---
**Author:** ![smolgrrr](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/smolgrrr/32/2825_2.png) [@smolgrrr](https://community.umbrel.com/u/smolgrrr)\ **Post date:** [September 2, 2023, 2:11am UTC](https://community.umbrel.com/t/fatal-leveldb-error-io-error-data-bitcoin-indexes-txindex-300149-ldb-invalid-argument/11720/4 "2023-09-02T02:11:18Z")
Hi @vpal, have you attempted the following? > [@Official Umbrel Troubleshooting Guide and FAQ](https://community.umbrel.com/t/official-umbrel-troubleshooting-guide-and-faq/9873/1): > > 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. > > 1. 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. > 2. 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/bitcoin.conf` > 3. Add the following line to the file:`reindex=1` > 4. Save and exit the file by pressing `CTRL+X`, then `Y`, and then `ENTER`. > 5. 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.