Chainstate Corruption: error in middle of Win64 version 0.10.0

VikingNation commented at 2:11 pm on March 7, 2015: none

The chain state database is corrupted quite often. This occurs regardless of program successful shutdown or crash. The amount of corruption makes the Bitcon application unuseable because the database must be reindexed every time.

2015-03-07 13:46:31 Bitcoin version v0.10.0 (2015-02-13 09:55:11 +0100) 2015-03-07 13:46:31 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015 2015-03-07 13:46:31 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2015-03-07 13:46:31 Default data directory C:\Users[NameRemoved]\AppData\Roaming\Bitcoin 2015-03-07 13:46:31 Using data directory C:\Users[NameRemoved]\AppData\Roaming\Bitcoin 2015-03-07 13:46:31 Using config file C:\Users[NameRemoved]\AppData\Roaming\Bitcoin\bitcoin.conf 2015-03-07 13:46:31 Using at most 125 connections (2048 file descriptors available) 2015-03-07 13:46:31 Using 4 threads for script verification 2015-03-07 13:46:31 Using wallet wallet.dat 2015-03-07 13:46:31 init message: Verifying wallet… 2015-03-07 13:46:31 CDBEnv::Open : LogDir=C:\Users[NameRemoved]\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users[NameRemoved]\AppData\Roaming\Bitcoin\db.log 2015-03-07 13:46:31 Bound to [::]:8333 2015-03-07 13:46:31 Bound to 0.0.0.0:8333 2015-03-07 13:46:31 init message: Loading block index… 2015-03-07 13:46:31 Opening LevelDB in C:\Users[NameRemoved]\AppData\Roaming\Bitcoin\blocks\index 2015-03-07 13:46:31 Opened LevelDB successfully 2015-03-07 13:46:31 Opening LevelDB in C:\Users[NameRemoved]\AppData\Roaming\Bitcoin\chainstate 2015-03-07 13:46:44 Corruption: error in middle of record

SeverinAequus commented at 2:23 am on April 19, 2015: none

I am having this issue also. As far as I know, the computer has not been shutdown improperly nor has the application crashed. I also have plenty of available disk space. If there is a way to recover from this by rebuilding the chainstate from the downloaded blocks, that would be ideal. The only other option is to resync everything.

laanwj added the label Bug on Jun 17, 2015

laanwj added the label Windows on Jun 17, 2015

evilworm commented at 7:19 am on September 9, 2015: none

Having the same behavior. This happened already for the third time in two month period. Really annoying because you have to rebuild the db from scratch which takes a lot of time.

Debug output from the last successful launch and then the following unsuccessful launch. Note that the gap in the log file is there, I haven’t created that by myself. I had a power outage at that moment so I guess that has to do something with the error.

The D drive is WD Green WD20EARS 2TB 64MB on NTFS.

 02015-09-05 04:40:23 UpdateTip: new best=000000000000000011adbee5b98e072c463f90d20147ca7f92ea42cff13e63ec  height=373062  log2_work=83.30377  tx=82395716  date=2015-09-05 00:34:49 progress=0.999808  cache=37.0MiB(17222tx)
 12015-09-05 04:40:54 UpdateTip: new best=00000000000000000954f9a8a3ade8e22ee56c7421a18ddb1f09cc321af0c3bf  height=373063  log2_work=83.303799  tx=82396309  date=2015-09-05 00:42:24 progress=0.999813  cache=51.1MiB(18889tx)
 22015-09-05 04:40:54 ERROR: AcceptToMemoryPool: non-final
 32015-09-05 04:40:54 receive version message: /Satoshi:0.11.0/: version 70002, blocks=357861, us=***.***.***.***:8333, peer=13
 42015-09-05 04:40:54 Added time data, samples 11, offset -40 (+0 minutes)
 52015-09-05 04:40:54 nTimeOffset = +0  (+0 minutes)
 62015-09-05 04:40:54 ERROR: AcceptToMemoryPool: non-final
 72015-09-05 04:40:54 ERROR: AcceptToMemoryPool: non-final
 82015-09-05 04:40:54 ERROR: AcceptToMemoryPool: non-final
 92015-09-05 04:40:55 ERROR: AcceptToMemoryPool: non-final
102015-09-05 04:41:37 UpdateTip: new best=000000000000000012aade3900c329c3dd6d0bdb0cc0fa863d867afe514ef470  height=373064  log2_work=83.303829  tx=82397881  date=2015-09-05 01:06:18 progress=0.999831  cache=62.8MiB(21888tx)
112015-09-05 04:41:37 ERROR: AcceptToMemoryPool: non-final
122015-09-05 04:41:37 receive version message: /Satoshi:0.9.2.1/: version 70002, blocks=352943, us=***.***.***.***:8333, peer=14
132015-09-05 04:41:37 Added time data, samples 12, offset -8 (+0 minutes)
142015-09-05 04:41:37 ERROR: AcceptToMemoryPool: non-final
152015-09-05 04:42:01 UpdateTip: new best=0000000000000000059f75c608690cb93cc6fde550944a2e84107f21999ea3e8  height=373065  log2_work=83.303858  tx=82398600  date=2015-09-05 01:14:29 progress=0.999837  cache=10.0MiB(2563tx)
162015-09-05 04:42:01 ERROR: AcceptToMemoryPool: non-final
172015-09-05 04:42:19 UpdateTip: new best=000000000000000010c8d1f7ed391da514b30b937f50653a3dfe3c2b7d936880  height=373066  log2_work=83.303888  tx=82399294  date=2015-09-05 01:23:47 progress=0.999844  cache=14.0MiB(4417tx)
182015-09-05 04:42:28 UpdateTip: new best=00000000000000000756dfe59e0133866e6a181a117dc4b2dd44d8563c9222b0  height=373067  log2_work=83.303918  tx=82399694  date=2015-09-05 01:28:43 progress=0.999848  cache=17.3MiB(5452tx)
192015-09-05 04:42:36 UpdateTip: new best=000000000000000010f52ad243cbfc1e37085249c5f975004e37c34c0fc455d1  height=373068  log2_work=83.303947  tx=82400153  date=2015-09-05 01:34:55 progress=0.999853  cache=18.6MiB(6525tx)
202015-09-05 04:42:45 UpdateTip: new best=00000000000000001004e5b5c0a4f21d3f76727000f610c38df7a3041fe58233  height=373069  log2_work=83.303977  tx=82400774  date=2015-09-05 01:42:35 progress=0.999859  cache=19.3MiB(7815tx)
212015-09-05 04:42:54 UpdateTip: new best=00000000000000000c68dfb349e72eadc8c2a6788d1262f22d2e47f9695d4607  height=373070  log2_work=83.304006  tx=82401125  date=2015-09-05 01:51:46 progress=0.999866  cache=21.4MiB(8676tx)
222015-09-05 04:43:24 UpdateTip: new best=000000000000000005a5c082a69db099595290bdadc52f022ddbe51800f732ac  height=373071  log2_work=83.304036  tx=82402680  date=2015-09-05 02:10:41 progress=0.999880  cache=41.0MiB(12283tx)
232015-09-05 04:43:29 UpdateTip: new best=00000000000000001292629b98eb69c6e8d12c8f80d5aecbb2620c33608a3bf8  height=373072  log2_work=83.304065  tx=82402895  date=2015-09-05 02:13:49 progress=0.999883  cache=41.2MiB(12733tx)
242015-09-05 04:43:43 UpdateTip: new best=00000000000000000a93d16d850ab47efa6fdbc933c8365c412a2b0138bcd2d4  height=373073  log2_work=83.304095  tx=82403869  date=2015-09-05 02:34:59 progress=0.999899  cache=48.5MiB(14668tx)
252015-09-05 05:21:17 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..." 
262015-09-05 05:21:17 
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
472015-09-05 05:21:17 Bitcoin version v0.11.0 (2015-07-10 19:23:55 +0200)
482015-09-05 05:21:17 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015
492015-09-05 05:21:17 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
502015-09-05 05:21:17 Default data directory C:\Users\*******\AppData\Roaming\Bitcoin
512015-09-05 05:21:17 Using data directory D:\bt-data
522015-09-05 05:21:17 Using config file D:\bt-data\bitcoin.conf
532015-09-05 05:21:17 Using at most 125 connections (2048 file descriptors available)
542015-09-05 05:21:17 Using 8 threads for script verification
552015-09-05 05:21:17 Using wallet wallet.dat
562015-09-05 05:21:17 scheduler thread start
572015-09-05 05:21:17 init message: Verifying wallet...
582015-09-05 05:21:17 CDBEnv::Open: LogDir=D:\bt-data\database ErrorFile=D:\bt-data\db.log
592015-09-05 05:21:18 Bound to [::]:8333
602015-09-05 05:21:18 Bound to 0.0.0.0:8333
612015-09-05 05:21:18 Cache configuration:
622015-09-05 05:21:18 * Using 2.0MiB for block index database
632015-09-05 05:21:18 * Using 32.5MiB for chain state database
642015-09-05 05:21:18 * Using 65.5MiB for in-memory UTXO set
652015-09-05 05:21:18 init message: Loading block index...
662015-09-05 05:21:18 Opening LevelDB in D:\bt-data\blocks\index
672015-09-05 05:21:18 Opened LevelDB successfully
682015-09-05 05:21:18 Opening LevelDB in D:\bt-data\chainstate
692015-09-05 05:21:21 Corruption: error in middle of record
702015-09-05 05:35:23 Aborted block database rebuild. Exiting.
712015-09-05 05:35:23 scheduler thread interrupt
722015-09-05 05:35:23 Shutdown: In progress...
732015-09-05 05:35:23 StopNode()
742015-09-05 05:35:23 Shutdown: done
752015-09-07 07:38:58 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..." 
762015-09-07 07:38:59

laanwj added the label Data corruption on Feb 9, 2016

fanquake commented at 11:41 am on November 12, 2016: member

Closing this in an effort to cleanup issues. The debug logs here are from 0.10.0 and 0.11.0, so if there are corruption issues with a more current release, a new issue can be opened.

fanquake closed this on Nov 12, 2016

MarcoFalke locked this on Sep 8, 2021

Chainstate Corruption: error in middle of Win64 version 0.10.0 #5865