Blockchain sync ended with some errors

kosuodhmwa commented at 3:45 am on March 3, 2024: none

Is there an existing issue for this?

I have searched the existing issues

Current behaviour

Blockchain sync ended with some errors. Details in attached file.

I used the newest self-compiled version:

cd ~ apt install build-essential autogen pkg-config libtool libboost-all-dev git clone https://github.com/bitcoin/bitcoin.git cd bitcoin ./autogen.sh ./configure make all

-> then started “bitcoind”

debug log here: https://fastupload.io/MymrQQJTSGXUNc9/file

Expected behaviour

No crash like that!

Steps to reproduce

cd ~ apt install build-essential autogen pkg-config libtool libboost-all-dev git clone https://github.com/bitcoin/bitcoin.git cd bitcoin ./autogen.sh ./configure make all

then start “bitcoind”

Relevant log output

debug log here: https://fastupload.io/MymrQQJTSGXUNc9/file

How did you obtain Bitcoin Core

Compiled from source

What version of Bitcoin Core are you using?

Newest version on 03-02-2024 on https://github.com/bitcoin/bitcoin.git

Operating system and version

Debian 12.5 most current version

Machine specifications

VirtualBox 7.0.14 VM on Windows 10 x64 Pro with most current updates bitcoind-problem

araujo88 commented at 3:57 am on March 4, 2024: contributor

Can you please copy and paste the contents of debug.log here?

kosuodhmwa commented at 10:46 am on March 4, 2024: none

[…] 2024-03-02T22:25:18Z UpdateTip: new best=00000000000000000047769fad477383a16875655c6635621b2680091c32425e height=514719 version=0x20000000 log2_work=88.412973 tx=306189176 date=‘2018-03-22T20:58:20Z’ progress=0.313967 cache=716.1MiB(6275922txo) 2024-03-02T22:25:18Z UpdateTip: new best=0000000000000000003a72605c6f5309b90563bd1526760c908e157fc47b5b14 height=514720 version=0x20000000 log2_work=88.413025 tx=306192300 date=‘2018-03-22T21:01:40Z’ progress=0.313970 cache=716.4MiB(6278401txo) 2024-03-02T22:25:18Z UpdateTip: new best=0000000000000000002cf5c699676496b18dea6c3672cd4b689500f23d1405af height=514721 version=0x20000000 log2_work=88.413077 tx=306194692 date=‘2018-03-22T21:12:19Z’ progress=0.313973 cache=716.6MiB(6279891txo) 2024-03-02T22:25:18Z UpdateTip: new best=00000000000000000003ab0587298c368df4b9e89ae82756fa31c3606b5335ce height=514722 version=0x20000000 log2_work=88.413129 tx=306195666 date=‘2018-03-22T21:16:48Z’ progress=0.313974 cache=716.9MiB(6282482txo) 2024-03-02T22:26:14Z Fatal LevelDB error: IO error: /root/.bitcoin/chainstate/110632.ldb: Input/output error 2024-03-02T22:26:14Z You can use -debug=leveldb to get more complete diagnostic messages 2024-03-02T22:26:15Z *** System error while flushing: Fatal LevelDB error: IO error: /root/.bitcoin/chainstate/110632.ldb: Input/output error 2024-03-02T22:26:15Z Error: A fatal internal error occurred, see debug.log for details 2024-03-02T22:26:15Z ERROR: ProcessNewBlock: ActivateBestChain failed (System error while flushing: Fatal LevelDB error: IO error: /root/.bitcoin/chainstate/110632.ldb: Input/output error) 2024-03-02T22:26:15Z tor: Thread interrupt 2024-03-02T22:26:15Z opencon thread exit 2024-03-02T22:26:15Z addcon thread exit 2024-03-02T22:26:15Z Shutdown: In progress… 2024-03-02T22:26:15Z ERROR: ConnectBlock: Consensus::CheckTxInputs: 9efb41e7b818a25cd73b7ca91f4b7d159ce1a1109e5132816d4bc725d597e067, bad-txns-inputs-missingorspent, CheckTxInputs: inputs missing/spent 2024-03-02T22:26:15Z InvalidChainFound: invalid block=0000000000000000001dff78d8df8d1ca1ac9726cb239b26beeea059b4e21211 height=514723 log2_work=88.413181 date=2018-03-22T21:19:02Z 2024-03-02T22:26:15Z InvalidChainFound: current best=00000000000000000003ab0587298c368df4b9e89ae82756fa31c3606b5335ce height=514722 log2_work=88.413129 date=2018-03-22T21:16:48Z 2024-03-02T22:26:15Z ERROR: ConnectTip: ConnectBlock 0000000000000000001dff78d8df8d1ca1ac9726cb239b26beeea059b4e21211 failed, bad-txns-inputs-missingorspent, CheckTxInputs: inputs missing/spent 2024-03-02T22:26:15Z torcontrol thread exit 2024-03-02T22:26:15Z InvalidChainFound: invalid block=00000000000000000013bd968c85c9a7df268ddb77c658048661d7c3ed347a53 height=514729 log2_work=88.413493 date=2018-03-22T22:47:00Z 2024-03-02T22:26:15Z net thread exit 2024-03-02T22:26:15Z InvalidChainFound: current best=00000000000000000003ab0587298c368df4b9e89ae82756fa31c3606b5335ce height=514722 log2_work=88.413129 date=2018-03-22T21:16:48Z 2024-03-02T22:26:15Z Fatal LevelDB error: IO error: /root/.bitcoin/chainstate/110632.ldb: Input/output error 2024-03-02T22:26:15Z You can use -debug=leveldb to get more complete diagnostic messages 2024-03-02T22:26:15Z *** System error while flushing: Fatal LevelDB error: IO error: /root/.bitcoin/chainstate/110632.ldb: Input/output error 2024-03-02T22:26:15Z Error: A fatal internal error occurred, see debug.log for details 2024-03-02T22:26:15Z ERROR: ProcessNewBlock: ActivateBestChain failed (System error while flushing: Fatal LevelDB error: IO error: /root/.bitcoin/chainstate/110632.ldb: Input/output error) 2024-03-02T22:26:15Z msghand thread exit 2024-03-02T22:26:15Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat started 2024-03-02T22:26:15Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat completed (0.00s) 2024-03-02T22:26:15Z scheduler thread exit 2024-03-02T22:26:15Z Writing 0 unbroadcast transactions to disk. 2024-03-02T22:26:15Z Dumped mempool: 0.000s to copy, 0.004s to dump 2024-03-02T22:26:15Z Flushed fee estimates to fee_estimates.dat. 2024-03-02T22:26:18Z Fatal LevelDB error: IO error: /root/.bitcoin/chainstate/110632.ldb: Input/output error 2024-03-02T22:26:18Z You can use -debug=leveldb to get more complete diagnostic messages 2024-03-02T22:26:18Z *** System error while flushing: Fatal LevelDB error: IO error: /root/.bitcoin/chainstate/110632.ldb: Input/output error 2024-03-02T22:26:18Z Error: A fatal internal error occurred, see debug.log for details 2024-03-02T22:26:18Z ForceFlushStateToDisk: failed to flush state (System error while flushing: Fatal LevelDB error: IO error: /root/.bitcoin/chainstate/110632.ldb: Input/output error) 2024-03-02T22:26:55Z Fatal LevelDB error: IO error: /root/.bitcoin/chainstate/110632.ldb: Input/output error 2024-03-02T22:26:55Z You can use -debug=leveldb to get more complete diagnostic messages 2024-03-02T22:26:55Z *** System error while flushing: Fatal LevelDB error: IO error: /root/.bitcoin/chainstate/110632.ldb: Input/output error 2024-03-02T22:26:55Z Error: A fatal internal error occurred, see debug.log for details 2024-03-02T22:26:55Z ForceFlushStateToDisk: failed to flush state (System error while flushing: Fatal LevelDB error: IO error: /root/.bitcoin/chainstate/110632.ldb: Input/output error) 2024-03-02T22:26:59Z Shutdown: done

araujo88 commented at 11:39 am on March 4, 2024: contributor

Dumb question: do you have enough disk space? You can check with df -Th. Besides, can you rerun bitcoind with the flag -debug=leveldb?

Also, can you post the results of sudo fsck -n /dev/sdaX?

kosuodhmwa commented at 1:08 pm on March 4, 2024: none

before there was a problem with that, because it mounted the mount point wrongly…

after i mounted it correctly, there shoud be 1023 GB:

Mounted ISCSI drive in Windows 10 pro x64 host system as B:\ (1TB, 1024GB)
Created a virtal disk (.img) in VirtualBox with 1023GB size
Mounted that img. drive in Debian 12.5

Now, i will try i mount that ISCSI targert in Debian 12.5 directly, not the “indirecty” way via Windows 10 host system mounted ISCSI drive… will look what happens…

kosuodhmwa commented at 1:08 pm on March 4, 2024: none

because of the issue, i deleted that config i described…

kosuodhmwa commented at 6:43 pm on March 4, 2024: none

So it’s 100% NOT a space problem… more a LevelDB caching mechanism problem similar the problem that some DBMS systems had ~20 years ago with some RAID configutarations (RAID5)

kosuodhmwa commented at 6:44 pm on March 4, 2024: none

is the source code from https://github.com/bitcoin/bitcoin.git not a stable one - do i need better to use some compiled release versions?

araujo88 commented at 6:54 pm on March 4, 2024: contributor

is the source code from https://github.com/bitcoin/bitcoin.git not a stable one - do i need better to use some compiled release versions?

It is usually recommended that you install a major release version, since they are more stable.

However, I don’t believe that should have any relation to your issue.

kosuodhmwa commented at 6:56 pm on March 4, 2024: none

Debian (different versions?) seem to have a problem when using CHAP authentication on Synology ISCSI targets so it seems, now just some windows Server versions as described HERE: https://www.reddit.com/r/synology/comments/19895j5/need_help_with_chap_authentication_issue_on/

Windows 10 x64 pro has NOT, because of that i try it again via the img. VirtualBox drive way via Win10 host - not with Host Cache option enabled :

kosuodhmwa commented at 7:10 pm on March 4, 2024: none

OK - so now bitcoin deamon is on VirtualBox virtual drive that is a .img file on Windows 10 x64 pro host mounted ISCSI drive.

Bitcoin data directory, which is per default on /~/.Bitcoin is now a symlink to the big (1023GB) mounted VirtualBox drive on /mount/btc-iscsi-space

kosuodhmwa commented at 7:13 pm on March 4, 2024: none

Update: NO, not a good idea i.m.o to use the 2nd big 1023GB drive for the bitcoin daemon (application) - only for bitcoin data (.Bitcoin directory)… back to home dir with bitcoin daemon…

kosuodhmwa commented at 7:17 pm on March 4, 2024: none

ok - let’s go.. will see what happens…

fanquake added the label Questions and Help on Mar 5, 2024

fanquake commented at 10:18 am on March 5, 2024: member

Reading the thread it seems that the original issue was due to a misconfiguration of your VM, and the current status is that things are syncing? If you really want to compile and run bitcoind on Linux (on Windows), is there a reason you aren’t using Windows Subsystem for Linux; that would seem to at least offer a more “native”/integrated experience with the filesystem.

kosuodhmwa commented at 10:27 am on March 5, 2024: none

Hmmm… for some things i prefer Windows, for other things Linux - mostly in a pure form and as a VM. (so i know, i can’t run M$ Linux Subsystem in a VirtualBox VM… at least not with Version 6.x when i remember right, may it works with the 7.0.14 version i’m currently running..?)

-> now i use still the same config (virtualbox .img virtual drive on Windows mounted ISCSI drive from Synology NAS ISCSI target) but with “VirtIO” adapter in VM configuration (instead of SATA).

Seems the work better, will see what happen, the process is still running, not i’m on transactions from 2019-11… before it was not able to run unteil the years 2019.

Looks better so it seems :-)

kosuodhmwa commented at 10:28 am on March 5, 2024: none

so i think i can close the GitHub issue now, because it’s 99.7% NOT a bitcoind problem… :-)

kosuodhmwa closed this on Mar 5, 2024

Blockchain sync ended with some errors #29542