BitCore Error: corrupted data base

[Tricky Dicky]

BitCore Error: corrupted data base ---
How to  fix -->

2019-12-13 07:01:10 init message: Rewinding blocks...
2019-12-13 07:01:12 Corruption: block checksum mismatch
2019-12-13 07:01:12 *** System error while flushing: Database corrupted
2019-12-13 07:52:16 Aborted block database rebuild. Exiting.
2019-12-13 07:52:16 scheduler thread interrupt
2019-12-13 07:52:16 Shutdown: In progress...
2019-12-13 07:52:16 StopNode()
2019-12-13 07:52:16 Corruption: block checksum mismatch
2019-12-13 07:52:16 *** System error while flushing: Database corrupted

[1714030707]

1714030707

[1714030707]

1714030707

[1714030707]

1714030707

[nc50lc]

This looks similar to Bitcoin Core's blocks corruption error.

How to  fix -->

This may be a simple corrupted blocks because of sudden shutdowns or force exit of BitCore or a major issue like failing drive.

Try to use a disk health checking software for possible "bad sectors" on your disk;
if there's none, try to delete the last blk.dat file in the blocks directory (Considering it uses the same file format as Bitcoin Core).

[LoyceV]

if there's none, try to delete the last blk.dat file in the blocks directory (Considering it uses the same file format as Bitcoin Core).

Last time I tried that (on a 50 GB pruned node), it triggered a complete rescan re-download, and from someone with a non-pruned full node I heard the same.
That's okay as long as you're not in a hurry or limited on bandwidth. Just don't be surprised

[nc50lc]

if there's none, try to delete the last blk.dat file in the blocks directory (Considering it uses the same file format as Bitcoin Core).

Last time I tried that (on a 50 GB pruned node), it triggered a complete rescan, and from someone with a non-pruned full node I heard the same.
That's okay as long as you're not in a hurry or limited on bandwidth. Just don't be surprised

Ah, I forgot to put a warning.
Yes it will definitely trigger a rescan but AFAIK for a non-pruned node, it will not re-download the existing blocks
Rescan just takes a lot of time.

[LoyceV]

Yes it will definitely trigger a rescan but AFAIK for a non-pruned node, it will not re-download the existing blocks

Sorry, I used the wrong word. I meant a re-download, which I didn't expect for a non-pruned node.
Unfortunately, I don't have enough free disk space to test it by myself.

[LoyceV]

If suggestion by nc50lc doesn't work, then your option is delete all blockchain files created by Bitcore and let Bitcore sync from beginning.

That's what it did on it's own after deleting the latest block file.

[LoyceV]

we're talking about BitCore

I assumed that was a typo, otherwise this thread should be moved to the Altcoins board.

[ABCbits]

we're talking about BitCore

I assumed that was a typo, otherwise this thread should be moved to the Altcoins board.

While there's cryptocurrency called BitCore, there's a Bitcoin full node client called BitCore (https://bitcore.io/).
Unless OP explicitly he's talking about BitCore cryptocurrency, then this thread belongs to this section.

[Tricky Dicky]

Thanks ... 
It's Bitcoin Core.
After 2 days of reloading blocks, still 36 weeks behind, I have a "fatal error" and the software shuts down.
Here is the last part of debug file:

2019-12-16T04:45:57Z ERROR: ConnectTip: ConnectBlock 00000000000000000023712d268712147475cc3ee028ca514e3f74799b20696e failed, bad-txnmrklroot, hashMerkleRoot mismatch (code 16)
2019-12-16T04:45:57Z Failed to connect best block (bad-txnmrklroot, hashMerkleRoot mismatch (code 16))
2019-12-16T04:45:57Z [default wallet] Submitting wtx 4302c64fab0f323fe845e0f0d290e2d9fb8ed1c649cb7979c0235987c60fde78 to mempool for relay
2019-12-16T04:45:57Z [default wallet] Submitting wtx 29803ea363c61975cace8800529c52c65f458aaa3b0ddc46c0037f5a0df8a0b9 to mempool for relay
2019-12-16T04:45:57Z GUI: Platform customization: "windows"
2019-12-16T04:45:58Z GUI: QObject::connect: Cannot queue arguments of type 'size_t'
(Make sure 'size_t' is registered using qRegisterMetaType().)
2019-12-16T04:45:58Z tor: Thread interrupt
2019-12-16T04:45:58Z Shutdown: In progress...
2019-12-16T04:45:58Z opencon thread exit
2019-12-16T04:45:58Z addcon thread exit
2019-12-16T04:45:58Z torcontrol thread exit
2019-12-16T04:45:58Z net thread exit
2019-12-16T04:45:58Z msghand thread exit
2019-12-16T04:45:58Z scheduler thread interrupt
2019-12-16T04:45:59Z [default wallet] Releasing wallet
2019-12-16T04:45:59Z Shutdown: done

What to do next?
Uninstall and re-install?
Thnx
 

[nc50lc]

Now it's "hashMerkleRoot mismatch", that looks like a failing HDD problem than Bitcoin Core specific.

What's the result of the HDD health scanner software? Or you haven't checked your HDD?
Use HD Sentinel or same software first before trying to fix/reinstall Core.

[Tricky Dicky]

I decided to delete the blocks and let the updated software to download the database from scratch.
The data files that I just deleted were in the range of 260GB, divided in approx. 131MB blocks.

As for now, I'm 4Y 32W behind, and it tells me that the operation should be finished in roughly 2 days .. fingers crossed .. 

[nc50lc]

If there's a hardware issue, you'll just download and verify for nothing because there will be another corruption if that particular bad sector(s) was reached.
The first thing that you should be doing is to scan your disk for possible bad sectors, it will only take less than an hour to do.