Quote from: NeuroticFish on Today at 05:04:29 PM

Quote from: fairmuffin on Today at 04:44:30 PM

Block not found on disk

I didn't encounter this error, but I've looked up on the internet.
The answer from here ( https://bitcoin.stackexchange.com/a/79749 ) tells that you probably need a reindex in your bitcoind.

Thanks, I found it too but I found it was weird and maybe not specific for my case? Cause it only does it for the latest block each time (so for example just right now 880,375, it is doing it for it). But I'll reindex and report back here.

Quote from: apogio on Today at 05:06:14 PM

Quote from: fairmuffin on Today at 04:44:30 PM

My Bitcoin node is now fully synced; however, I keep getting errors on Fulcrum, related to the latest block (while it was syncing at just 5%):

<...>

Can someone please advise? I have txindex enabled, and pruning is disabled, and I do have enough diskspace where Bitcoin data and Fulcrum data is stored. I am not sure what's wrong.

Probably your databasei is broken and you need a rescan.

Before you do it, can you post your fulcrum.conf please? Omit anything you don't wanna share.

I had deleted the data dir for Fulcrum and still the same issue. Here's my Fulcrum.conf:

Code:

datadir = G:\FulcrumData_MainNet
bitcoind = 127.0.0.1:8332
rpcuser = randomuser
rpcpassword = randompass
tcp = 127.0.0.1:50001
peering = false
announce = false
public_tcp_port = 50001
admin = 8000
stats = 8080
db_max_open_files = 80
fast-sync = 8000