So, I'm running a regular btc node and I've hit a snag kinda similar to this issue I found. I tried to reindex using './bitcoind reindex', but now it seems like the daemon can’t download the whole blockchain. I kicked off the command about a week ago, and for the last few days, it’s been stuck around 90.8%. The daemon keeps trying, but the download percentage just goes back and forth between about 90.65 and 90.90%.
I checked out some related posts on stackexchange suggesting this could be linked to bad peers or maybe even a storage problem, but nothing jumps out at me. Plus, I saw that some folks mentioned you can't cancel the reindexing, so I'm kinda lost on how to fix this. Is my node done for? Is there any way to adjust my 'dbcache' while it's still downloading? I found a suggestion that it might help out, but it didn't say where to change the dbcache setting.
Any help would be super appreciated while I try to get my node back up and running.
Can you add more details about your nodes your current hard drive space, ram, and OS?
Have you tried to upgrade the Bitcoin core? There was a new release last month Bitcoin Core version 27.0 it might fix your issue if you upgraded it to the latest version if the drive is not the issue.
About dbcache you can stop the node and edit the Bitcoin.conf file and add this "dbcache=(Value)" The value depends on your current RAM size.
Do you see any errors in your debug.log file? If yes, can you post portions of those here (sanitize private data before)?
Your first linked thread is about issues with content of settings.json file. Are you sure you have a similar problem?
If your Bitcoin Core is stuck or slow with syncing but doesn't spit out some errors, I don't see an immediate reason for a reindex run, unless you killed bitcoind by force and corrupted some of its databases or indices.
Remember to always shutdown bitcoind gracefully via bitcoin-cli stop and monitor the tail of debug.log to finally say:
yyyy-mm-ddThh:mm:ssZ Shutdown: done
It should continue where you left it.
Probably, those reports have restarted Bitcoin Core without removing --reindex arg, doing so will restart the reindex process from start.
If you closed Core properly (./bitcoin-cli stop) and considering that there's no other issue, then, your node should resume the progress when you shutdown your node.
But it should be SOP to check the logs before using commands like --reindex since it may not be the best solution that you need.
And now, there should be an indication why it's stalled or at least tell that there's no issue but slow sync progress.