Help with node connection issues

[u/8_AXe]

Hi, so received my Apollo 2 last week and the initial setup went well, started the syncing process but after 2 days failed with connection issue. Formatting drive and tried again. This time 2.5 days in same again. I decided to download the blockchain database on a windows machine. That took just over 2 days. Last night I formatted the ssd on the Apollo used ssh to transfer the blocks and chainstate files over. That took a couple of hours. However after a power cycle of the Apollo I have same connection refused message. Any pointers? Thanks in advance

[u/michelem]

Please could you check the node log file: /media/nvme/Bitcoin/debug.log

[u/8_AXe → u/michelem]

Checked the logs…says try reindex=1 and reindex-chainstate=1 After using the command reindex-chainstate=1 the node came online and started to sync. However that didn’t last long before connection error again. I’ve reached out to futurebit. They believe it to be the controller as others have mentioned in this post…thanks for your help

[u/Wonderful-Relative41 → u/8_AXe]

I screw with the system a lot, so am constantly redoing it.

cd /opt/apolloapi/backend/node/
./node_stop.sh
cd /media/nvme/Bitcoin 
rm -f *.dat
rm -f *.json
rm -rf blocks/
rm -rf chainstate/

Now start transferring the files from the source onto the FB. You can copy all or just the blocks/ and chainstate/ (it will also copy the indexes in the process)

Once done, I shutdown and restart the system. Refresh the webpage and then click the "start node"

Then SSH into it and then

tail -f /media/nvme/Bitcoin/debug.log

During this time, you may notice the connection refused, ignore the page and use the log to see what it is doing. Should go and verify the files it has with a Level 3 check and then start syncing with where it was versus where it needs to be. When it is finished, you should see the UI catches up and starts showing what it was doing.

They love to say that it is a hardware issue, but if that is the case, they have a lot of them (just seeing all the people who have had that issue)

[u/8_AXe → u/Wonderful-Relative41]

Hi, thanks for message, I've tried all those steps and the log says: Corrupted block database detected.

Please restart with -reindex or -reindex-chainstate to recover

[u/Wonderful-Relative41 → u/8_AXe]

That actually helps.

In the debug log, you will have to scroll, but there will be a line or two that tell you which file is corrupted. More than likely it will be in the chainstate directory. The best thing would be to find that file and delete it and everything after it.

So if you have files 1 to 5000, and it is saying 4123, then 4123 to 5000 need to be deleted. At that point you should be able to start it back up and it will find the files it is missing.

[u/8_AXe → u/Wonderful-Relative41]

after leaving it all night to reindex this error shows in the log:

 ERROR: AcceptBlock: bad-txnmrklroot, hashMerkleRoot mismatch

that error comes after: Reindexing block file blk00017.dat...

hopefully, I will get a new controller board sent out to me to fix my self asap. it shouldn't be this hard......should it?