bitcoin daemon database error in a block - page 2.

darkv0rt3x

hero member

Activity: 1274

Merit: 681

I rather die on my feet than to live on my knees

Quote from: ?? on ??

Quote from: nc50lc on June 05, 2020, 08:41:53 PM

Quote from: darkv0rt3x on June 05, 2020, 01:10:27 PM

This is taking ages... It only added about 2000 blocks in like 10 hours. I'm only at ~425000. And I started this almost 24h ago. In the first 12h it did about 22000 block, and in the remaining hours, only about 2000 blocks.

I think it's quite normal.
Sync is usually faster at the first few blocks when there're few transactions in them: smaller blocks sizes.
Then considerably slower at the last few blocks because of the verification that was skipped in the old blocks.
Consider adding tweaks to your config file like dbcache="half_of_your_RAM+" if you're using the default size.

The index folder's size seems fine to me.

A new debug.log entries will help a lot.

I fail how it's normal, unless OP's internet is quite slow (200 kb/s or slower) or there's major bottleneck (indicated by 100% CPU or HDD usage almost all the time).

Quote from: darkv0rt3x on June 06, 2020, 05:02:27 AM

I'll then run the smart tools on this drive to check it's sanity.

If the result is quite bad, you just shorten age of your storage device.

No, my internet is ok. It's Optics Fiber and it's rated at 200/100 Mbits.

An I don't even know if the internet is playing any role right now, because I just add an internet disconnection and the process just continued!
As I have my folder with the total amount it is supposed to have, I think that whatever it is doing, it is only using data that I already have on my drive.

Jet Cash

legendary

Activity: 2814

Merit: 2472

https://JetCash.com

Have you backed up your wallet and associated files? You should do this before you do any experimenting or attempt recovery.

darkv0rt3x

hero member

Activity: 1274

Merit: 681

I rather die on my feet than to live on my knees

Quote from: nc50lc on June 05, 2020, 08:41:53 PM

Quote from: darkv0rt3x on June 05, 2020, 01:10:27 PM

This is taking ages... It only added about 2000 blocks in like 10 hours. I'm only at ~425000. And I started this almost 24h ago. In the first 12h it did about 22000 block, and in the remaining hours, only about 2000 blocks.

I think it's quite normal.
Sync is usually faster at the first few blocks when there're few transactions in them: smaller blocks sizes.
Then considerably slower at the last few blocks because of the verification that was skipped in the old blocks.
Consider adding tweaks to your config file like dbcache="half_of_your_RAM+" if you're using the default size.

The index folder's size seems fine to me.

A new debug.log entries will help a lot.

Yeah, I know about the first blocks being faster and last blocks being significantly slower.

In the meantime I tried to stop bitcoind -reindex-chainstate and restarted bitcoind normally, but using dbcache=12000 (I have 16GB of RAM) and this last night it progressed quite well, considering the last 24h. It's processing around file blk01800.dat.

So, I expect this finishes during today an I hope I have my full data again. I'll then run the smart tools on this drive to check it's sanity.

nc50lc

legendary

Activity: 2534

Merit: 6080

Self-proclaimed Genius

Quote from: darkv0rt3x on June 05, 2020, 01:10:27 PM

This is taking ages... It only added about 2000 blocks in like 10 hours. I'm only at ~425000. And I started this almost 24h ago. In the first 12h it did about 22000 block, and in the remaining hours, only about 2000 blocks.

I think it's quite normal.
Sync is usually faster at the first few blocks when there're few transactions in them: smaller blocks sizes.
Then considerably slower at the last few blocks because of the verification that was skipped in the old blocks.
Consider adding tweaks to your config file like dbcache="half_of_your_RAM+" if you're using the default size.

The index folder's size seems fine to me.

A new debug.log entries will help a lot.

darkv0rt3x

hero member

Activity: 1274

Merit: 681

I rather die on my feet than to live on my knees

This is taking ages... It only added about 2000 blocks in like 10 hours. I'm only at ~425000. And I started this almost 24h ago. In the first 12h it did about 22000 block, and in the remaining hours, only about 2000 blocks.

Do I have any other way, other than '-reindx-chainstate' to try to fix my database?

My 'blocks' folder size says 298GB and my 'index' folder (inside 'blocks' folder), says only 94MB.
So, I think I have all the blocks files but looks like I might be missing some data from folder 'index', no?
Will this be the only way to fix the problem or maybe some other approach can do the trick once I have all the data in 'blocks' folder?

darkv0rt3x

hero member

Activity: 1274

Merit: 681

I rather die on my feet than to live on my knees

Quote from: HCP on June 04, 2020, 06:58:32 PM

Well, it's connected and achieving network connections to peers, so it should be receiving new blocks...

Using the reindex option, you might need to give it some time to finish that process before it starts receiving/validating new blocks... is there anything obvious in the debug.log that might explain why it's not? Huh

Well, my debug log is recent because I forgot to set it up after I accidentally deleted part of my folder.
But I set it up yesterday and again I made a mistake. I set it up like:

Code:

debug=net,httprpc,reindex,proxy,leveldb

I missed a coma. Now, I'm not sure what is it logging.
And probably, if I stop bitcoin daemon, fix the debug setup and start -reindex-chainstate,it will restart the process from the very beginning, no?

HCP

legendary

Activity: 2086

Merit: 4361

Well, it's connected and achieving network connections to peers, so it should be receiving new blocks...

Using the reindex option, you might need to give it some time to finish that process before it starts receiving/validating new blocks... is there anything obvious in the debug.log that might explain why it's not? Huh

darkv0rt3x

hero member

Activity: 1274

Merit: 681

I rather die on my feet than to live on my knees

Quote from: HCP on June 04, 2020, 06:34:27 PM

Quote from: darkv0rt3x on June 04, 2020, 05:15:48 PM

I get only about 402000 blocks.

For whatever reason, it seems like your node is not syncing... is the number of blocks increasing at all?

What output do you get if you run bitcoin-cli getnetworkinfo? Do you see "networkactive": true and "connections": XX where XX is > 0? Huh

Well, I decided to restart bitcoind with -reindex-chainstate...

About getnetworkinfo, i get:

Code:

{
"version": 209900,
"subversion": "/Satoshi:0.20.99/",
"protocolversion": 70015,
"localservices": "0000000000000409",
"localservicesnames": [
"NETWORK",
"WITNESS",
"NETWORK_LIMITED"
],
"localrelay": true,
"timeoffset": -3,
"networkactive": true,
"connections": 11,
"networks": [

So, yes, network is active and with 11 connections.
However I can also see that "NETWORK_LIMITED" and I'm not sure what it means in this specific context. I don't know what is usually there when the node is fully running.

HCP

legendary

Activity: 2086

Merit: 4361

Quote from: darkv0rt3x on June 04, 2020, 05:15:48 PM

I get only about 402000 blocks.

For whatever reason, it seems like your node is not syncing... is the number of blocks increasing at all?

What output do you get if you run bitcoin-cli getnetworkinfo? Do you see "networkactive": true and "connections": XX where XX is > 0? Huh

darkv0rt3x

hero member

Activity: 1274

Merit: 681

I rather die on my feet than to live on my knees

Hello again...

Well, my node looks running ok, but when I run:

Code:

bitcoin-cli getblockcount

I get only about 402000 blocks.
What do I need to do to get the missing blocks from the Blockchain?

darkv0rt3x

hero member

Activity: 1274

Merit: 681

I rather die on my feet than to live on my knees

Ok, the proccess is now complete.

Later today, after work, I'll run a few hardware tests, just for the sake of it.
Bitcoind seems to be running ok now.

I'll post feedback later.

Thanks

nc50lc

legendary

Activity: 2534

Merit: 6080

Self-proclaimed Genius

Quote from: darkv0rt3x on June 03, 2020, 01:16:34 PM

It just crashed again. It was working well since yesterday night (when I noticed it was stopped) until 5 minutes ago. It has been working but I can see this block error every now and then, probably when the daemon dumps the cache onto the drive.

Do you think I need to delete the entire 'chainstate' folder? Wouldn't that single file be enough to delete and the daemon re-download it again?

It will ask you to rebuild the whole database even if you delete that single file; it might even produce errors.
Rebuilding the database wont take long compared to syncing the whole blockchain.

Anyways, based from the new replies, it looks like you have more corrupted files than the one in the chainstate folder.
Your .blk files seems to have inconsistencies like missing transactions probably because of corrupted data.
You might need to check for hardware issues.

darkv0rt3x

hero member

Activity: 1274

Merit: 681

I rather die on my feet than to live on my knees

Quote from: HCP on June 03, 2020, 04:10:45 PM

It would appear increasingly likely that there is a hardware issue of some description. Undecided

If you're getting corrupted files occurring randomly, then the most likely culprits are either your HDD/SSD or possibly bad RAM... there is also a possibility that it's the drive/memory controller and/or chipset on the mobo that is failing.

Diagnosing the exact cause of these faults can be tricky... you might also want to try using Memtest86+ and see if there are any issues with your RAM.

Well, at this point I just facked up this shit.

I accidentally deleted part of my .bitcoin folder.

Now I had to re-write my bitcoin.conf file and I don't remember the exact settings I had before.

Anyways, I wrote a new bitcoin.conf file and I started bitcoin with the switch '-reindex' and pray that this fix the missing data in my .bitcoin folder.

I see millions of messages like this in my terminal right now:

Code:

2020-06-03T22:50:20Z Reindexing block file blk00085.dat...
LoadExternalBlockFile: Processing out of order child 00000000000000199dbc751fccefd9990a69d84ce3b65df2111ad353f142f116 of 000000000000000cb8e8600edcc8d919f844ee84a99d6bf85a67073e15497452

and

Code:

2020-06-03T23:09:22Z Reindexing block file blk00719.dat...
LoadExternalBlockFile: Out of order block 000000000000000002aca1df9327326ae86db6fb26c2a4f7174fb3fd68ee5cbf, parent 000000000000000002016b6e847878e3f4ada7eb3fbe23a19ab069270308f151 not known

I hope this can download the missing data and just fix this once and for all.

HCP

legendary

Activity: 2086

Merit: 4361

It would appear increasingly likely that there is a hardware issue of some description. Undecided

If you're getting corrupted files occurring randomly, then the most likely culprits are either your HDD/SSD or possibly bad RAM... there is also a possibility that it's the drive/memory controller and/or chipset on the mobo that is failing.

Diagnosing the exact cause of these faults can be tricky... you might also want to try using Memtest86+ and see if there are any issues with your RAM.

darkv0rt3x

hero member

Activity: 1274

Merit: 681

I rather die on my feet than to live on my knees

Quote from: jackg on June 02, 2020, 06:24:19 PM

It tells you, try starting it up with - debug=leveldb

But it's likely you'll have to redownload the chain.

I hope I don't have to. I have been having this problem since last week. And last week I stopped bitcoin daemon normally, tried the '-reindex' option but then I was told to cancel the '-reindex' and just try to restart the daemon normally. So I did and the laptop was almost 24h checking all transactions from the very beginning. Not downloading the entire chain, just re-checking txo's.
Then it finished and was working since then. So I didn't pay much more attention to it until 2 days ago when I noticed the node was not running.

Quote from: nc50lc on June 02, 2020, 10:32:13 PM

Quote from: darkv0rt3x on June 02, 2020, 06:06:36 PM

Now I started the daemon again and after it was running normally, I shut it down with 'bitcoin-cli stop' and I can see this:

Code:

2020-06-02T23:06:06Z Fatal LevelDB error: Corruption: block checksum mismatch: /media/Storage/Blockchain/chainstate/060607.ldb
-snip-
2020-06-02T23:06:06Z *** System error while flushing: Fatal LevelDB error: Corruption: block checksum mismatch: /media/Storage/Blockchain/chainstate/060607.ldb
-snip-
2020-06-02T23:06:06Z ForceFlushStateToDisk: failed to flush state (System error while flushing: Fatal LevelDB error: Corruption: block checksum mismatch: /media/Storage/Blockchain/chainstate/060607.ldb)
-snip-
2020-06-02T23:06:06Z Fatal LevelDB error: Corruption: block checksum mismatch: /media/Storage/Blockchain/chainstate/060607.ldb
-snip-
2020-06-02T23:06:06Z *** System error while flushing: Fatal LevelDB error: Corruption: block checksum mismatch: /media/Storage/Blockchain/chainstate/060607.ldb
-snip-
2020-06-02T23:06:06Z ForceFlushStateToDisk: failed to flush state (System error while flushing: Fatal LevelDB error: Corruption: block checksum mismatch: /media/Storage/Blockchain/chainstate/060607.ldb)

Seems like there an issue with file: /media/Storage/Blockchain/chainstate/060607.ldb
Is it still crashing?

If it is: Shutdown Core normally then try to delete the "chainstate" folder in "/media/Storage/Blockchain/".
Start Core and it will rebuild the database (not redownload the blockchain); if it still crash, check the latest log.

It just crashed again. It was working well since yesterday night (when I noticed it was stopped) until 5 minutes ago. It has been working but I can see this block error every now and then, probably when the daemon dumps the cache onto the drive.

Do you think I need to delete the entire 'chainstate' folder? Wouldn't that single file be enough to delete and the daemon re-download it again?

Quote from: ?? on ??

OP, you might want to check and test your HDD/SSD health if the problem persists after following advice by other members. Use tools called smartctl to do so.
Just in case you never use it, here's short command that i usually use

* See general information

Code:

sudo smartctl -a /dev/

* Perform short or long test

Code:

sudo smartctl --test=short /dev/

Code:

sudo smartctl --test=long /dev/

Then use sudo smartctl -a /dev/ again to see the test result

Quote from: jackg on June 02, 2020, 06:24:19 PM

It tells you, try starting it up with - debug=leveldb

But it's likely you'll have to redownload the chain.

Only if the blockchain files corrupted as well, from the log, looks like only single chainstate file is corrupted.

Thanks for the cheat sheet of commands.

Edited:

Well, I just noticed the error is now on a different file... A file that doesn't even exist in my chainstate folder. It's '061114.ldb' file.
I also noticed something I'm not sure is normal. I have a symlink inside 'chainstate' to... 'chainstate'...

Code:

-rw------- 1 narayan narayan 88K ago 15 2019 104069.ldb
lrwxrwxrwx 1 narayan narayan 10 ago 10 2019 chainstate -> chainstate
-rw------- 1 narayan narayan 16 ago 15 2019 CURRENT
-rw------- 1 narayan narayan 0 ago 10 2019 LOCK
-rw------- 1 narayan narayan 337K ago 15 2019 MANIFEST-102299

nc50lc

legendary

Activity: 2534

Merit: 6080

Self-proclaimed Genius

Quote from: darkv0rt3x on June 02, 2020, 06:06:36 PM

Now I started the daemon again and after it was running normally, I shut it down with 'bitcoin-cli stop' and I can see this:

Code:

2020-06-02T23:06:06Z Fatal LevelDB error: Corruption: block checksum mismatch: /media/Storage/Blockchain/chainstate/060607.ldb
-snip-
2020-06-02T23:06:06Z *** System error while flushing: Fatal LevelDB error: Corruption: block checksum mismatch: /media/Storage/Blockchain/chainstate/060607.ldb
-snip-
2020-06-02T23:06:06Z ForceFlushStateToDisk: failed to flush state (System error while flushing: Fatal LevelDB error: Corruption: block checksum mismatch: /media/Storage/Blockchain/chainstate/060607.ldb)
-snip-
2020-06-02T23:06:06Z Fatal LevelDB error: Corruption: block checksum mismatch: /media/Storage/Blockchain/chainstate/060607.ldb
-snip-
2020-06-02T23:06:06Z *** System error while flushing: Fatal LevelDB error: Corruption: block checksum mismatch: /media/Storage/Blockchain/chainstate/060607.ldb
-snip-
2020-06-02T23:06:06Z ForceFlushStateToDisk: failed to flush state (System error while flushing: Fatal LevelDB error: Corruption: block checksum mismatch: /media/Storage/Blockchain/chainstate/060607.ldb)

Seems like there an issue with file: /media/Storage/Blockchain/chainstate/060607.ldb
Is it still crashing?

If it is: Shutdown Core normally then try to delete the "chainstate" folder in "/media/Storage/Blockchain/".
Start Core and it will rebuild the database (not redownload the blockchain); if it still crash, check the latest log.

jackg

copper member

Activity: 2856

Merit: 3071

https://bit.ly/387FXHi lightning theory

It tells you, try starting it up with - debug=leveldb

But it's likely you'll have to redownload the chain.

darkv0rt3x

hero member

Activity: 1274

Merit: 681

I rather die on my feet than to live on my knees

Hello.

I'm having some issues keeping my node running.
I'm using Bitcoin Core version v0.20.99.0-e478b11db under Debain Buster.

I have been being surprised multiple times with my node shut down. When I check the debug.log file I can't see much.
Now I started the daemon again and after it was running normally, I shut it down with 'bitcoin-cli stop' and I can see this:

Code:

2020-06-02T23:06:05Z Writing 0 unbroadcast transactions to disk.
2020-06-02T23:06:05Z Dumped mempool: 0.011839s to copy, 0.49971s to dump
2020-06-02T23:06:05Z WriteBatch memory usage: db=index, before=0.0MiB, after=0.0MiB
2020-06-02T23:06:05Z FlushStateToDisk: write coins cache to disk (1089745 coins, 154430kB) started
2020-06-02T23:06:06Z Fatal LevelDB error: Corruption: block checksum mismatch: /media/Storage/Blockchain/chainstate/060607.ldb
2020-06-02T23:06:06Z You can use -debug=leveldb to get more complete diagnostic messages
2020-06-02T23:06:06Z FlushStateToDisk: write coins cache to disk (1089745 coins, 154430kB) completed (0.16s)
2020-06-02T23:06:06Z *** System error while flushing: Fatal LevelDB error: Corruption: block checksum mismatch: /media/Storage/Blockchain/chainstate/060607.ldb
2020-06-02T23:06:06Z Error: A fatal internal error occurred, see debug.log for details
Error: A fatal internal error occurred, see debug.log for details
2020-06-02T23:06:06Z ForceFlushStateToDisk: failed to flush state (System error while flushing: Fatal LevelDB error: Corruption: block checksum mismatch: /media/Storage/Blockchain/chainstate/060607.ldb)
2020-06-02T23:06:06Z WriteBatch memory usage: db=index, before=0.0MiB, after=0.0MiB
2020-06-02T23:06:06Z FlushStateToDisk: write coins cache to disk (705742 coins, 105277kB) started
2020-06-02T23:06:06Z Fatal LevelDB error: Corruption: block checksum mismatch: /media/Storage/Blockchain/chainstate/060607.ldb
2020-06-02T23:06:06Z You can use -debug=leveldb to get more complete diagnostic messages
2020-06-02T23:06:06Z FlushStateToDisk: write coins cache to disk (705742 coins, 105277kB) completed (0.15s)
2020-06-02T23:06:06Z *** System error while flushing: Fatal LevelDB error: Corruption: block checksum mismatch: /media/Storage/Blockchain/chainstate/060607.ldb
2020-06-02T23:06:06Z Error: A fatal internal error occurred, see debug.log for details
Error: A fatal internal error occurred, see debug.log for details
2020-06-02T23:06:06Z ForceFlushStateToDisk: failed to flush state (System error while flushing: Fatal LevelDB error: Corruption: block checksum mismatch: /media/Storage/Blockchain/chainstate/060607.ldb)
2020-06-02T23:06:06Z [default wallet] Releasing wallet
2020-06-02T23:06:06Z Shutdown: done

What can I do to try to fix this?

Topic: bitcoin daemon database error in a block - page 2. (Read 987 times)