Aha this may work. Lets see, its processing.
screen -dmS node /opt/apolloapi/backend/node/bitcoind -reindex -datadir=/media/nvme/Bitcoin -conf=/opt/apolloapi/backend/node/bitcoin.conf
Yep, next release has a "Reindex node" option before the formate node drive as away to recover the node database without going to the extreme of wiping the drive in case of hard shutdowns etc
Could you please clarify the instructions for this? I'm only moderately experienced with this but I am having the same issue but only getting about 25% synced before I hit the error message.
Looking at the debug.log in the bitcoin directory is the most important item to monitor actively. An error message on the node GUI doesn't show you what's going on behind the scenes. Did the node abruptly stop? what errors? chainstate corrupt?
Do you have the browser open on the Node? I close the browser and have minimal items on the node open to monitor the logs. The node IBD performed better on my system with these closed. I stopped the miner until download complete. I monitor remotely as this only grabs basic data from the node.
with the system monitor check the operating processes. Sometimes the bitcoind process may still be running even though the system looks paused. only when this process disappears is the node completely stopped. You can get an error message in the logs that memory buffer exceeded limits and the bitcoind then writes the data to the chainstate database and continues on. There is a pause when this happens.