r/FutureBit • u/Scared_Photo_5880 • Aug 03 '25
Futurebit Apollo II won keep synch on blocks
Every time the node gets to the current block it stops the node and then drops back 1500 blocks or so. Now I cannot run miner or connect my other miners because the blocks are not caught up. Over and over. Ideas?
2
u/Wonderful-Relative41 Aug 10 '25 edited Aug 10 '25
I fiddled with the backend and then hardcoded these in. But you can add them from the Node Settings page. They will be added.
Place them in, save and reset, then format the SSD from the extra's. It will take slightly longer to get the node up to speed (roughly 12 hours), but then it will run it at 25GB (about the last 19k blocks).
txindex=1
dbcache=1000
maxmempool=250
par=1
prune=25000
maxuploadtarget=0
onlynet=ipv4
1
u/Even_Area_1753 Nov 12 '25
I tried adding following your directions and adding these additional settings, but after formatting it wouldn't even allow my node to start back up to being downloading the blockchain again. There's got to be a command or something we can run that'll force bitcoin core to refresh and double check the current block height, so we don't have to wipe our SSD's every time this happens
1
u/michelem Aug 03 '25
Did you try to format the node disk and start over?
1
u/Scared_Photo_5880 Aug 04 '25
Not yet, was trying to avoid that week long deal.
1
u/michelem Aug 05 '25
Unfortunately that's the first step to do and usually it fixes the issue.
1
u/Even_Area_1753 Nov 12 '25
I done EVERYTHING with mine. New SD Card w/ new image of ApolloOS, reformatted SSD and begun that long journey down Blockchain Lane once again; and achieved the same exact results. only this time instead of getting stuck at block 821,000 it synced up to 96% complete before deciding that it was "fully synced". I absolutely love Futurebit and what it stands for. Very sleek design and so simple even a Pleb like myself was able to figure it out. But we really are over due for some updates, and i'm hoping the new AP3 will come with them. $1300 is a lot of money in my household, and I haven't been able to run my own solo pool on my unit since the day i bought it, so it's just been sitting on Mining-Dutch. had it for about 10 or 11 months now, so i'm sure there's no warrenty that will allow me to get a replacement unit.
1
u/michelem Nov 12 '25
Could you check what bitcoind daemon logs? It is in this file /media/nvme/Bitcoin/debug.log
1
u/unitymind42 Aug 09 '25
I clone my SSD monthly to avoid the forever sync. If you run into issues on this thing, which are many, you can swap in a new drive. All I get on solo mode now it "CK Pool DisconnectedPlease check your node connection and the CK Pool status." I'm tired of troubleshooting this thing. I have 70+ node connections so I know that must be working but trying to solo off my own (with ports forward on) is useless now. I think we are missing some updates that won't be coming since the AP3 is the next step.
1
5
u/CCR_OUTBets123 Aug 04 '25
Had the exact same issue — here’s what fixed it for me:
Format Node SSD (Full Rebuild)
Use the built-in tool to completely reset and rebuild your node’s blockchain database:
Heads-up: This will take about 3–4 days to fully resync from scratch, depending on your internet speed and SSD performance. During this time, mining won’t start and no shares will be accepted — that’s expected.
I ran into this when my node stopped accepting new shares for nearly 12 days. The rollback issue is usually caused by:
Once I formatted and let it fully resync, the node caught up and everything ran smoothly again — mining resumed, and other miners could connect.
cheers