QT Core wallet crash when starting with “-txindex” #12406

1. 
   user78713 commented at 6:39 pm on February 10, 2018: none

   Steps to reproduce:

   1. Start wallet with “C:\Program Files\Bitcoin\bitcoin-qt.exe” -datadir=d:\BitCoinData -Server "
   2. Let it sync 100%
   3. Close wallet
   4. start again with “-txindex” flag added

   The wallet re-sync, but at some point, the wallet just stop syncing, without any error message. When I close the wallet (press the “X”), error appears “Error: A fatal internal error occurred…”

   Attached debug log debug.log

   Expected behaviour Wallet should sync, and I should be able to use “getrawtransaction” from debug console

   Actual behaviour Wallet stalls and then just crash when I close it

   Screenshots.

2. MarcoFalke added this to the milestone 0.16.0 on Feb 10, 2018
3. MarcoFalke added the label Block storage on Feb 10, 2018
4. 
   MarcoFalke commented at 7:06 pm on February 10, 2018: member

   See #12401
5. 
   Sjors commented at 10:32 am on February 11, 2018: member

   at some point, the wallet just stop syncing, without any error message @MarcoFalke that’s a different error than I saw before making #12401

   From the end of the log file:

    02018-02-10 10:07:16 UpdateTip: new best=0000000000000000005e46d334bc42d19a68393a35f323c5661d2e025d942602 height=507987 version=0x20000000 log2_work=88.059978 tx=297969832 date='2018-02-06 17:43:35' progress=0.996700 cache=102.2MiB(770495txo)
    12018-02-10 10:07:16 receive version message: /bitnodes.earn.com:0.1/: version 70015, blocks=508490, us=37.142.234.51:8333, peer=84
    22018-02-10 10:07:16 net thread exit
    32018-02-10 10:07:16 opencon thread exit
    42018-02-10 10:07:16 msghand thread exit
    52018-02-10 10:07:16 Shutdown: In progress...
    62018-02-10 10:07:16 UPNP_DeletePortMapping() returned: 0
    72018-02-10 10:07:16 upnp thread interrupt
    82018-02-10 10:07:17 IO error: f:\BitCoinData\chainstate\160320.ldb: Data error (cyclic redundancy check).
    92018-02-10 10:07:17 *** System error while flushing: Database I/O error
   102018-02-10 10:07:35 IO error: f:\BitCoinData\chainstate\160320.ldb: Data error (cyclic redundancy check).
   112018-02-10 10:07:35 *** System error while flushing: Database I/O error
   122018-02-10 10:07:38 Shutdown: done
   

6. laanwj added the label Data corruption on Feb 11, 2018
7. 
   Sjors commented at 10:43 am on February 11, 2018: member

   @user78713 can you attach BitCoinData\chainstate\160320.ldb so we can look at the corruption?
8. MarcoFalke removed this from the milestone 0.16.0 on Feb 11, 2018
9. 
   user78713 commented at 9:38 pm on February 11, 2018: none

   Renamed to “.txt” so that I can attach it 160320.ldb.txt
10. 
    msafi commented at 5:37 pm on February 1, 2020: none

    I ran into a similar error earlier. Bitcoin Qt would crash without logging out anything meaningful. I found out what the problem in my case was by running Bitcoin Qt with the debugger attached. When I did that, the breakpoint was triggered on this line. The message variable said something about prune being turned on while txindex is on. I had previously turned on pruning, but I was now trying to run Bitcoin Qt with pruning off by omitting prune=1 from bitcoin.conf. Apparently, omitting prune is not enough. I had to explicitly set prune=0.

    TLDR; setting prune=0 in bitcoin.conf fixed this problem for me.

11. 
    Sjors commented at 8:41 pm on February 1, 2020: member

    @msafi were you using a recent version of master or a release? I believe we briefly introduced a bug that could trigger the message assert, but it’s been reverted. See #17965 (cc @promag, @hebasto).
12. 
    msafi commented at 8:54 pm on February 1, 2020: none

    @Sjors Yes, that may have been the case (I was using a recent version of master, not a release).
13. 
    MarcoFalke commented at 8:46 pm on February 10, 2020: member

    @user78713 Bitcoin Core makes heavy use of CPU, RAM and disk IO. Hardware defects might only become visible when running Bitcoin Core. You might want to check your hardware for defects.

    • memtest86 to check your RAM
    • to check the CPU behaviour under load, use linpack or Prime95
    • to test your storage device use smartctl or CrystalDiskInfo

    Source: https://bitcoin.stackexchange.com/a/12206

14. MarcoFalke added the label Waiting for author on Feb 10, 2020
15. 
    MarcoFalke commented at 8:49 pm on February 10, 2020: member

    Also, Bitcoin Core does not support external drives connected over USB, as they will also cause leveldb corruption.
16. MarcoFalke removed the label Waiting for author on Feb 10, 2020
17. MarcoFalke closed this on Feb 10, 2020

    ---

18. DrahtBot locked this on Feb 15, 2022

Contributors
user78713 MarcoFalke Sjors msafi

Labels
Block storage Data corruption