Corrupted block database detected. #21013

issue ghost openend this issue on January 26, 2021
  1. ghost commented at 1:55 pm on January 26, 2021: none

    Hello,

    i dont know what it is but i wanted to install Bitcoin Core V.0.21.0 but ervery time at a random Point this comes:Corrupted block database detected. and then the program closed and wont work anymore.

    My specs:

    AMD Ryzen 3600XT Nvidia 2060Ti Gaming X 4TB western digital Windows 10 Home

    It looks like this

    2021-01-26T13:32:25Z Bitcoin Core version v0.21.0 (release build) 2021-01-26T13:32:25Z Qt 5.9.8 (static), plugin=windows (static) 2021-01-26T13:32:25Z System: Windows 10 (10.0), x86_64-little_endian-llp64 2021-01-26T13:32:25Z Screen: \.\DISPLAY1 1920x1080, pixel ratio=2.0 2021-01-26T13:32:25Z Screen: \.\DISPLAY2 1920x1080, pixel ratio=1.0 2021-01-26T13:32:25Z Assuming ancestors of block 0000000000000000000b9d2ec5a352ecba0592946514a92f14319dc2b367fc72 have valid signatures. 2021-01-26T13:32:25Z Setting nMinimumChainWork=00000000000000000000000000000000000000001533efd8d716a517fe2c5008 2021-01-26T13:32:25Z Using the ‘shani(1way,2way)’ SHA256 implementation 2021-01-26T13:32:25Z Using RdSeed as additional entropy source 2021-01-26T13:32:25Z Using RdRand as an additional entropy source 2021-01-26T13:32:26Z Default data directory C:\Users\Loggorus\AppData\Roaming\Bitcoin 2021-01-26T13:32:26Z Using data directory D:\Bitcoin\chain 2021-01-26T13:32:26Z Config file: D:\Bitcoin\chain\bitcoin.conf (not found, skipping) 2021-01-26T13:32:26Z Using at most 125 automatic connections (2048 file descriptors available) 2021-01-26T13:32:26Z GUI: “registerShutdownBlockReason: Successfully registered: Bitcoin Core wurde noch nicht sicher beendet…” 2021-01-26T13:32:26Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2021-01-26T13:32:26Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2021-01-26T13:32:26Z Script verification uses 11 additional threads 2021-01-26T13:32:26Z scheduler thread start 2021-01-26T13:32:26Z Using wallet directory D:\Bitcoin\chain 2021-01-26T13:32:26Z init message: Verifiziere Wallet(s)… 2021-01-26T13:32:26Z init message: Lade Sperrliste… 2021-01-26T13:32:26Z SetNetworkActive: true 2021-01-26T13:32:26Z Using /16 prefix for IP bucketing 2021-01-26T13:32:26Z Cache configuration: 2021-01-26T13:32:26Z * Using 2.0 MiB for block index database 2021-01-26T13:32:26Z * Using 8.0 MiB for chain state database 2021-01-26T13:32:26Z * Using 1990.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space) 2021-01-26T13:32:26Z init message: Lade Blockindex… 2021-01-26T13:32:26Z Switching active chainstate to Chainstate [ibd] @ height -1 (null) 2021-01-26T13:32:26Z Opening LevelDB in D:\Bitcoin\chain\blocks\index 2021-01-26T13:32:27Z Opened LevelDB successfully 2021-01-26T13:32:27Z Using obfuscation key for D:\Bitcoin\chain\blocks\index: 0000000000000000 2021-01-26T13:32:29Z LoadBlockIndexDB: last block file = 128 2021-01-26T13:32:29Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=621, size=125788462, heights=293039…294068, time=2014-03-29…2014-04-04) 2021-01-26T13:32:29Z Checking all blk files are present… 2021-01-26T13:32:29Z Opening LevelDB in D:\Bitcoin\chain\chainstate 2021-01-26T13:32:30Z Opened LevelDB successfully 2021-01-26T13:32:30Z Using obfuscation key for D:\Bitcoin\chain\chainstate: b7ab9a346d3beacb 2021-01-26T13:32:30Z Loaded best chain: hashBestChain=000000000000000066c41c5c2265a9f821212622215eba24ba7ebf7a3f6ebfef height=293630 date=2014-04-01T20:41:44Z progress=0.059174 2021-01-26T13:32:30Z init message: Verifiziere Blöcke… 2021-01-26T13:32:32Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) started 2021-01-26T13:32:32Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) completed (0.00s) 2021-01-26T13:32:32Z init message: Verifiziere Blöcke… 2021-01-26T13:32:32Z Verifying last 6 blocks at level 3 2021-01-26T13:32:32Z [0%]…ERROR: ReadBlockFromDisk: Deserialize or I/O error - CAutoFile::read: end of file: iostream error at FlatFilePos(nFile=128, nPos=37424931) 2021-01-26T13:32:32Z ERROR: VerifyDB(): *** ReadBlockFromDisk failed at 293630, hash=000000000000000066c41c5c2265a9f821212622215eba24ba7ebf7a3f6ebfef 2021-01-26T13:32:32Z : Corrupted block database detected. Please restart with -reindex or -reindex-chainstate to recover. 2021-01-26T13:32:46Z init message: Lade Blockindex… 2021-01-26T13:32:46Z should not be overwriting a chainstate 2021-01-26T13:32:46Z Error: Error opening block database 2021-01-26T13:32:48Z Shutdown: In progress… 2021-01-26T13:32:48Z scheduler thread exit 2021-01-26T13:32:48Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) started 2021-01-26T13:32:48Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) completed (0.00s) 2021-01-26T13:32:49Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) started 2021-01-26T13:32:49Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) completed (0.00s) 2021-01-26T13:32:50Z Shutdown: done

  2. MarcoFalke commented at 2:02 pm on January 26, 2021: member

    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

  3. MarcoFalke added the label Data corruption on Jan 26, 2021
  4. ghost commented at 2:06 pm on January 26, 2021: none

    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

    How can i do that?

  5. practicalswift commented at 2:18 pm on January 26, 2021: contributor
    • 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

    How can i do that?

    The best way is simply to altavista “how to use memtest86” and proceed from there.

  6. ghost commented at 2:20 pm on January 26, 2021: none
    • 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

    How can i do that?

    The best way is simply to altavista “how to use memtest86” and proceed from there.

    and then?

    i mean i buy it new a month ago

  7. practicalswift commented at 2:28 pm on January 26, 2021: contributor

    and then?

    When you’ve tested your RAM, CPU and storage device using the tools suggested above you report your results here :)

    If you’re unsure about how to use the suggested tools you’ll either have to set aside some time to read up on those tools, or set aside some money to pay someone to do the job for you.

    DIY or outsource: I don’t think there is any third option TBH :)

  8. ghost commented at 3:16 pm on January 26, 2021: none
    Ok i am very sry but the Sites are lucking very sus and the Programs dont look better.the Programs are very complx and i can not see what to do also why the program say me that i have to sit here a couple hours just to farm some Bitcoins and i have a visit at my doctor in an half hour
  9. MarcoFalke deleted a comment on Jan 28, 2021
  10. MarcoFalke commented at 11:50 am on February 8, 2021: member
    Closing due to lack of progress in testing the hardware for defects
  11. MarcoFalke closed this on Feb 8, 2021

  12. DrahtBot locked this on Aug 18, 2022

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2024-09-28 22:12 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me