Bitcoin Core Crashes Everytime When Starting

[kshlalala]

2015-11-19 07:23:52 Pre-allocating up to position 0xd00000 in rev00330.dat
2015-11-19 07:23:52 UpdateTip: new best=000000000000000006b8de17e4e90932e00ff2353c8c60e46070ff75ca7963b3  height=373409  log2_work=83.313992  tx=82674672  date=2015-09-07 11:25:24 progress=0.924407  cache=53.9MiB(14775tx)
2015-11-19 07:23:52 UpdateTip: new best=00000000000000000a8a6fbc9cd3205bd4d0987c506f5818ccbbece325f6b117  height=373410  log2_work=83.314021  tx=82674673  date=2015-09-07 11:26:18 progress=0.924408  cache=53.9MiB(14776tx)
2015-11-19 07:23:53 UpdateTip: new best=00000000000000000566b7e65212b50279c231f3c2d085889f682ce63e6c1018  height=373411  log2_work=83.314051  tx=82674927  date=2015-09-07 11:27:48 progress=0.924409  cache=58.2MiB(15687tx)
2015-11-19 07:23:54 UpdateTip: new best=00000000000000000be7550345115f2f162229d0b0351abc09f9ff6a366da719  height=373412  log2_work=83.31408  tx=82675206  date=2015-09-07 11:31:20 progress=0.924412  cache=63.0MiB(16390tx)
2015-11-19 07:23:56 Corruption: block checksum mismatch
2015-11-19 07:23:56 *** System error while flushing: Database corrupted
2015-11-19 07:24:05 ERROR: ProcessNewBlock: ActivateBestChain failed
2015-11-19 07:24:05 receive version message: /Satoshi:0.11.1/: version 70002, blocks=384274, us=175.156.246.57:56427, peer=3
2015-11-19 07:24:05 Added time data, samples 4, offset -26 (+0 minutes)
2015-11-19 07:24:05 opencon thread interrupt
2015-11-19 07:24:05 addcon thread interrupt
2015-11-19 07:24:05 msghand thread interrupt
2015-11-19 07:24:05 scheduler thread interrupt
2015-11-19 07:24:05 net thread interrupt
2015-11-19 07:24:05 Shutdown: In progress...
2015-11-19 07:24:05 StopNode()
2015-11-19 07:24:05 Corruption: block checksum mismatch
2015-11-19 07:24:05 *** System error while flushing: Database corrupted
2015-11-19 07:24:07 Shutdown: done

Please help, i have quite a few bitcoins in the wallet :/ Thanks!

[1714848272]

1714848272

[1714848272]

1714848272

[1714848272]

1714848272

[ranochigo]

Apparently, it looks like your Bitcoin Core got corrupted. Try backing up your wallet.dat and run it again with -reindex option from command line or command prompt. It might just be some harddrive failures that's causing this.

If you can't wait, run Bitcoin Core, go to help, debug window, then console and unlock your wallet if applicable by inserting

Code:

walletpassphrase (password) 600 

then extract the private key by using

Code:

dumpprivkey [Bitcoin address]

. You can then import it into electrum or any other wallet.

[shorena]

Apparently, it looks like your Bitcoin Core got corrupted. Try backing up your wallet.dat and run it again with -reindex option from command line or command prompt. It might just be some harddrive failures that's causing this.

If you can't wait, run Bitcoin Core, go to help, debug window, then console and unlock your wallet if applicable by inserting

Code:

walletpassphrase (password) 600 

then extract the private key by using

Code:

dumpprivkey [Bitcoin address]

. You can then import it into electrum or any other wallet.

Please dont export your private keys unless you absolutly have to.

[BitAurum]

Apparently, it looks like your Bitcoin Core got corrupted. Try backing up your wallet.dat and run it again with -reindex option from command line or command prompt. It might just be some harddrive failures that's causing this.

If you can't wait, run Bitcoin Core, go to help, debug window, then console and unlock your wallet if applicable by inserting

Code:

walletpassphrase (password) 600 

then extract the private key by using

Code:

dumpprivkey [Bitcoin address]

. You can then import it into electrum or any other wallet.

Please dont export your private keys unless you absolutly have to.

Why are you advising the OP not to export the private keys of his bitcoin addresses from the wallet.dat file?

[shorena]

-snip-
Why are you advising the OP not to export the private keys of his bitcoin addresses from the wallet.dat file?

Because handling unprotected private keys is the easiest way to make mistakes which can lead to lost coins. It should always be considered a last resort option and never done just to speed things up. Esp. if a simple -reindex will most likely fix the problem within a few hours.

[BitAurum]

-snip-
Why are you advising the OP not to export the private keys of his bitcoin addresses from the wallet.dat file?

Because handling unprotected private keys is the easiest way to make mistakes which can lead to lost coins. It should always be considered a last resort option and never done just to speed things up. Esp. if a simple -reindex will most likely fix the problem within a few hours.

Handling unprotected private keys is dangerous only when you are doing it on a machine that is used for your day-to-day tasks.
If its done on a separate machine that only handles your bitcoin wallet it can be very safe.

[whizz94]

I've had similar trying to -resynch a bitcoin-qt 0.11.0 full node.
It resynchs for a couple of days, only needing two or three reboots and restarts without -resynch,
and then at seemingly random times through the past year or two worth of blocks, it hangs and the next restart won't get past "Activating Best Chain" before it hangs with "Error reading from database, shutting down".

I eventually found that it would -reindex from block 1 in 2009 but that takes days and has crashed every time eventually.
I'd be supporting the blockchain with a full node by now, a full 10 days after upgrading, if it would.

What do people think of some coding changes so that
on its own, -reindex does what it has always done; reindexing from the start
and new code can accept an =integer after -reindex
such that -reindex=280000 starts the reindexing from block 280000
and gets it a little further before it crashes again.
from a crash at 342000, you could for example
bitcoin-qt -reindex=340000
and eventually get synched and up to date, going over errors if necessary

If I see three ++ comments then I'll find a suggestion box to copy this post to.  If not then its just my grotty old computer which has a problem so it is not worth bothering the devs with it.

[onemorexmr]

I've had similar trying to -resynch a bitcoin-qt 0.11.0 full node.
It resynchs for a couple of days, only needing two or three reboots and restarts without -resynch,
and then at seemingly random times through the past year or two worth of blocks, it hangs and the next restart won't get past "Activating Best Chain" before it hangs with "Error reading from database, shutting down".

I eventually found that it would -reindex from block 1 in 2009 but that takes days and has crashed every time eventually.
I'd be supporting the blockchain with a full node by now, a full 10 days after upgrading, if it would.

What do people think of some coding changes so that
on its own, -reindex does what it has always done; reindexing from the start
and new code can accept an =integer after -reindex
such that -reindex=280000 starts the reindexing from block 280000
and gets it a little further before it crashes again.
from a crash at 342000, you could for example
bitcoin-qt -reindex=340000
and eventually get synched and up to date, going over errors if necessary

If I see three ++ comments then I'll find a suggestion box to copy this post to.  If not then its just my grotty old computer which has a problem so it is not worth bothering the devs with it.

i am against your idea for two reasons:

1) reindex isnt done regulary. so it doesnt really matter if it takes a while.
2) if someone enters the wrong blockindex for his reindex it may lead to very strange and hard to debug errors which may even go unnoticed for a longer time. better stay safe

not sure if it is even possible - this would only work if the index is handled by bitcoin-core and not by bdb - and i dont know how its implemented.