0.13.2 node crashed. | Bitcointalksearch.org

darkfur93

member

Activity: 110

Merit: 10

I redownloaded the blockcoin from a backup I had two years ago.
The 0.14.0 client was syncing up to height 454094 then I got a database corrupted error again.

Code:

2017-04-18 07:46:30 UpdateTip: new best=00000000000000000143315f49aaaf27a4d86e6db8861592476b25ea0b7fb89d height=454090 version=0x20000002 log2_work=86.016088 tx=198487963 date='2017-02-21 20:29:04' progress=0.928275 cache=1697.7MiB(1976210tx)
2017-04-18 07:46:30 Pre-allocating up to position 0x500000 in rev00744.dat
2017-04-18 07:46:30 UpdateTip: new best=000000000000000000a08072eecf1f3b58a75fd6db65c220070c507389f29e1c height=454091 version=0x20000002 log2_work=86.016123 tx=198491203 date='2017-02-21 20:29:09' progress=0.928277 cache=1698.3MiB(1978351tx)
2017-04-18 07:46:30 UpdateTip: new best=00000000000000000215c01701685f080f30d6cc19c61abae8a4c9bd053f150d height=454092 version=0x20000000 log2_work=86.016158 tx=198493336 date='2017-02-21 20:47:32' progress=0.928293 cache=1702.4MiB(1980010tx)
2017-04-18 07:46:30 UpdateTip: new best=0000000000000000020eb999832487d18f24cd859ea7db742a92b0567ab91ca1 height=454093 version=0x30000000 log2_work=86.016193 tx=198495351 date='2017-02-21 21:01:12' progress=0.928305 cache=1702.7MiB(1981227tx)
2017-04-18 07:46:30 UpdateTip: new best=000000000000000000d6c24c1ace1e7b3da8bc06c29178a597a78e5515ea45ae height=454094 version=0x20000000 log2_work=86.016228 tx=198497964 date='2017-02-21 21:00:54' progress=0.928305 cache=1703.8MiB(1983896tx)
2017-04-18 07:46:36 Corruption: block checksum mismatch
2017-04-18 07:46:36 *** System error while flushing: Database corrupted
2017-04-18 07:46:38 version handshake timeout from 18
2017-04-18 07:48:05

Log after I restarted the client:

Code:

2017-04-18 07:50:15 Bitcoin version v0.14.0.0-g43a987c1c
2017-04-18 07:50:15 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-04-18 07:50:15 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures.
2017-04-18 07:50:15 Default data directory /home/USER/.bitcoin
2017-04-18 07:50:15 Using data directory /home/USER/.bitcoin
2017-04-18 07:50:15 Using config file /home/USER.bitcoin/bitcoin.conf
2017-04-18 07:50:15 Using at most 175 automatic connections (1024 file descriptors available)
2017-04-18 07:50:15 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2017-04-18 07:50:15 Using 2 threads for script verification
2017-04-18 07:50:15 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2017-04-18 07:50:15 Using wallet wallet.dat
2017-04-18 07:50:15 init message: Verifying wallet...
2017-04-18 07:50:15 scheduler thread start
2017-04-18 07:50:15 CDBEnv::Open: LogDir=/home/USER/.bitcoin/database ErrorFile=/home/USER/.bitcoin/db.log
2017-04-18 07:50:15 Bound to [::]:8333
2017-04-18 07:50:15 Bound to 0.0.0.0:8333
2017-04-18 07:50:15 Cache configuration:
2017-04-18 07:50:15 * Using 2.0MiB for block index database
2017-04-18 07:50:15 * Using 8.0MiB for chain state database
2017-04-18 07:50:15 * Using 1014.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-04-18 07:50:15 init message: Loading block index...
2017-04-18 07:50:15 Opening LevelDB in /home/USER/.bitcoin/blocks/index
2017-04-18 07:50:15 Opened LevelDB successfully
2017-04-18 07:50:16 Using obfuscation key for /home/USER/.bitcoin/blocks/index: 0000000000000000
2017-04-18 07:50:16 Opening LevelDB in /home/USER/.bitcoin/chainstate
2017-04-18 07:50:16 Opened LevelDB successfully
2017-04-18 07:50:16 Using obfuscation key for /home/USER/.bitcoin/chainstate: 0000000000000000
2017-04-18 07:50:19 LoadBlockIndexDB: last block file = 744
2017-04-18 07:50:19 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=66, size=61895652, heights=454035...454139, time=2017-02-21...2017-02-22)
2017-04-18 07:50:19 Checking all blk files are present...
2017-04-18 07:50:19 LoadBlockIndexDB: transaction index disabled
2017-04-18 07:50:19 LoadBlockIndexDB: hashBestChain=0000000000000000000f62301cc883023932d0a20875c09e8f34d723c958a039 height=452928 date=2017-02-14 00:04:05 progress=0.918082
2017-04-18 07:50:19 init message: Rewinding blocks...
2017-04-18 07:50:20 Corruption: block checksum mismatch
2017-04-18 07:50:20 *** System error while flushing: Database corrupted
2017-04-18 07:50:22 Aborted block database rebuild. Exiting.
2017-04-18 07:50:22 scheduler thread interrupt
2017-04-18 07:50:22 Shutdown: In progress...
2017-04-18 07:50:22 Corruption: block checksum mismatch
2017-04-18 07:50:22 *** System error while flushing: Database corrupted

Foxpup

legendary

Activity: 4326

Merit: 3041

Vile Vixen and Miss Bitcointalk 2021-2023

The Raw Error Rate is completely meaningless except in comparison to Hardware ECC Recovered - if the numbers match, there's no problem. Even the Normalised Error Rate is fairly useless - some drives are just better or worse than others in that respect, and as long as the errors are recoverable, it doesn't really matter. If SMART says nothing else is wrong, it's more likely filesystem corruption or misbehaving antivirus software.

ranochigo

legendary

Activity: 2954

Merit: 4158

Could you try to delete the entire blockchain data and download everything from there?

I can't tell anything from your data, can you post the whole test instead of the values? It's hard to tell if the drive is failing. What OS are you using?

darkfur93

member

Activity: 110

Merit: 10

I been running a node for years and never had a problem that reindexing didn't fix.
I downloaded 0.14.0 and tried to reindex but about halfway through I got a error that said the database is corrupted.
I restarted the Bitcoin 0.14.0 client then I got a error message that said Unable to rewind the database to a pre-fork state. You will need to redownload the blockchain.
I might try reindexing on 0.13.2 if that doesn't work I might look for a backup copy of the blockchain so I don't have to redownload the whole thing.

SMART Data: Read Error Rate > 200,000,000 Seek Error Rate 140,000,000
HDD failing?

Topic: 0.13.2 node crashed. (Read 891 times)