Hi,
My miner has been syncing the blockchain for several days and I'm unable to ever reach 100% synced blockchain. It reached over 95% synced but the following morning its dropped back to 81% synced so I guess there was some issue and it's starting re-syncing again (maybe corruption or something).
If I wanted to clear the whole BTC block database and start again in case of corruption can I do this via the web based UI or do I need to manually clear the blockchain directory ? - /media/nvme/Bitcoin
I see Format Node SSD on the Web UI but I guess this would also wipe directory structure.
Topic: Official FutureBit Apollo BTC Software/Image and Support thread - page 16. (Read 50742 times)
September 20, 2024, 07:33:31 AM
September 19, 2024, 08:07:00 PM
1 Your cable would be the determining factor, you can use either
2 USB controller limitation is 7
3 Your extra unit could be a standard with no computer
2 USB controller limitation is 7
3 Your extra unit could be a standard with no computer
3 questions
1) I'd like to connect a second unit to my V1 node using a USB hub. Do I use the USB-C on the side or the USB-A on the back?
2) Is there a limit to the number of units I can connect to a V1?
3) Whats the spec difference of the V1+2, because the V1 is running a on a pi - is the v2 also running on a pi?
Thanks!
1) I'd like to connect a second unit to my V1 node using a USB hub. Do I use the USB-C on the side or the USB-A on the back?
2) Is there a limit to the number of units I can connect to a V1?
3) Whats the spec difference of the V1+2, because the V1 is running a on a pi - is the v2 also running on a pi?
Thanks!
September 19, 2024, 05:14:57 PM
3 questions
1) I'd like to connect a second unit to my V1 node using a USB hub. Do I use the USB-C on the side or the USB-A on the back?
2) Is there a limit to the number of units I can connect to a V1?
3) Whats the spec difference of the V1+2, because the V1 is running a on a pi - is the v2 also running on a pi?
Thanks!
1) I'd like to connect a second unit to my V1 node using a USB hub. Do I use the USB-C on the side or the USB-A on the back?
2) Is there a limit to the number of units I can connect to a V1?
3) Whats the spec difference of the V1+2, because the V1 is running a on a pi - is the v2 also running on a pi?
Thanks!
September 19, 2024, 04:16:33 PM
Hi, I have been running an Apollo II on solo in ECO mode for many weeks. Recently, I see a strange behavior. The hashrate climbs to about 5TH/s then back to 0Th/s, over an over again. The temperature of the ambient is about 75F, them miner is reporting about 65C. I have tried Balanced mode as well, doesnt seem to make any difference. Any ideas on how to fix it? or is it a web interface issue and the miner is actually running stable?
To me it doesn't really sound like a web interface issue . . . and I assume you are on at least v2.0.5. That being said, I have noticed a few strange issues on v2.0.5 related to the web interface but nothing like you've described. And even if I lose internet connection the machines just mine away. When they get hot I have even seen them freeze-up and/or shut down. But I've never seen my hashrate jump up and down like you've described unless I'm on a pool and then my pool hashrate has fluctuated wildly before, but not my actual miner hashrate. The only cliché suggestion I can come up with at this point is perhaps a re-flash of the software. It may be worth a try. Wish I could offer you more.
One last thing, does your power usage (wattage) fluctuate wildly at the same time? How about the chip speed and cpu?
Cheers!
September 19, 2024, 11:09:29 AM
Hi, I have been running an Apollo II on solo in ECO mode for many weeks. Recently, I see a strange behavior. The hashrate climbs to about 5TH/s then back to 0Th/s, over an over again. The temperature of the ambient is about 75F, them miner is reporting about 65C. I have tried Balanced mode as well, doesnt seem to make any difference. Any ideas on how to fix it? or is it a web interface issue and the miner is actually running stable?
September 18, 2024, 05:00:45 AM
Oh great. This is good news!
This is normal operation. Once the controller shuts down the fan goes high speed on default. Its a hardwire pull up on the fan PWM as a safety measure (ie all if controller fails, then onboard temp sensor power kill switch fails, as a backup of the backup the fan would go high speed).
It's also an indicator that the unit is safe to shut off, since when you shutdown in menu it takes a while for the controller and node to safely save the state of the blockchain and shutdown.
Thanks it's still syncing so should be OK.
One more thing. I notice when I select System - Shutdown from the UI menu on web browser that it shuts down the node and the miner but the fans on the Apollo II are spinning at full speed and for some reason do not spin down. The system doesn't halt so I have to manually switch the box off.
Is this a known bug or any idea how to fix?
One more thing. I notice when I select System - Shutdown from the UI menu on web browser that it shuts down the node and the miner but the fans on the Apollo II are spinning at full speed and for some reason do not spin down. The system doesn't halt so I have to manually switch the box off.
Is this a known bug or any idea how to fix?
This is normal operation. Once the controller shuts down the fan goes high speed on default. Its a hardwire pull up on the fan PWM as a safety measure (ie all if controller fails, then onboard temp sensor power kill switch fails, as a backup of the backup the fan would go high speed).
It's also an indicator that the unit is safe to shut off, since when you shutdown in menu it takes a while for the controller and node to safely save the state of the blockchain and shutdown.
September 17, 2024, 06:25:00 PM
If you cannot connect remotely again, try to access the miner, with a PC on the same network, as the Futurebit. If this fails, then try to ping it and last use a IP scanner to see all the devices, within your netwok.
Tried this. When the issue happens it dissapears from the ip scanner as well. Happened again for the 4th time last night. Just turned it off at this point and emailed support. Obviously I have a faulty unit so hopefully they will come through and give me a way to send it back for a fix or replacement since its only been in my home for around 30 dayshope it
When you get this straightened out let me / us know what the cause was please. Appreciate it. Cheers!
Will do. They finally got back to me today and said it sounds like it's having an overheating issue and I'm shipping it back to them. stinks I have to pay to ship it back but hopefully gets straightened out asap. They said approx two weeks.
Yeah, I was thinking heat problems as well but since you were running ECO it didn't really add up (unless there's intermittent fan issues / malfunctions). Oh well, I hope it all works out for you. On a side note, I've still got an overdue standard unit just sitting at the FEDX hub in Memphis now 3 days late with no updates or explanations as to why or when I'll ever see it. Three cheers for PATIENCE!
UPDATE: 09/17/24
My unit finally arrived yesterday - 10 days lost but was found and delivered. A little beat up but no real damage (except the bottom cover has been knocked loose and falls out). I never got much info from FutureBit after I reported the problem and FedX was nothing more than an irritating Internet bot pretending to be a real company in a three-dimensional space- lol. In any case, patience paid off (I think).
September 17, 2024, 12:53:46 PM
Out of curiosity, right now my 3 apollo 2's have hit a best share 7,632,598,247. Will it ever hit more than that? if so, is it a time thing or a luck thing?
Time + luck.
In general your best share should trend towards total shares submitted.
On the top you will see "Accepted Shares" this is the total work submitted to the solo pool. In a perfect world this would match your "Best Share".
Since bitcoin mining is completely random your best share is a totally random number. If you're unlucky it will be lower than total work submitted, and if you are lucky it will be greater.
You can get super lucky and get a 1T share which would take years of submitted work to "catch up" too.
And then you can hit the jackpot of course!
Has anyone hit near 1T on their Apollo II yet? Would be cool for you guys to post your best shares. Think highest we have seen is about 500B.
Also thinking about gamifying the Solo Pool and anonymously submit your best share for ranking on a site (and possibly give out prizes bases on best share as a cool incentive to solo mine without finding blocks).
Of course this would be opt in to collect this data and open source(and it would all be hashed data with no wallets or any personal data other than best share and maybe hashrate collected) but if you guys are interested might start working on it for 2.2 release.
This would also be a cool way to public display the state of the "FutureBit" hashrate network and show the impact all of you are having!
This is great to know! Yes Im at 3 billion total submitted and 7 Billion best share. I've only been live on the new apollo 2 units for a little over a week. Going to be sending more hash from my compass hosted units but they are terrible and taking forever.
Gamifying would be awesome!
Also, another user mentioned this but when do you think we will have visibility of units that aren't part of the apollo units that are contributing to a users solo mining? Just trying to see if I will be able to identify units that go down (hosted by compass)
September 17, 2024, 10:34:45 AM
Thanks it's still syncing so should be OK.
One more thing. I notice when I select System - Shutdown from the UI menu on web browser that it shuts down the node and the miner but the fans on the Apollo II are spinning at full speed and for some reason do not spin down. The system doesn't halt so I have to manually switch the box off.
Is this a known bug or any idea how to fix?
One more thing. I notice when I select System - Shutdown from the UI menu on web browser that it shuts down the node and the miner but the fans on the Apollo II are spinning at full speed and for some reason do not spin down. The system doesn't halt so I have to manually switch the box off.
Is this a known bug or any idea how to fix?
This is normal operation. Once the controller shuts down the fan goes high speed on default. Its a hardwire pull up on the fan PWM as a safety measure (ie all if controller fails, then onboard temp sensor power kill switch fails, as a backup of the backup the fan would go high speed).
It's also an indicator that the unit is safe to shut off, since when you shutdown in menu it takes a while for the controller and node to safely save the state of the blockchain and shutdown.
September 17, 2024, 10:31:09 AM
Out of curiosity, right now my 3 apollo 2's have hit a best share 7,632,598,247. Will it ever hit more than that? if so, is it a time thing or a luck thing?
Time + luck.
In general your best share should trend towards total shares submitted.
On the top you will see "Accepted Shares" this is the total work submitted to the solo pool. In a perfect world this would match your "Best Share".
Since bitcoin mining is completely random your best share is a totally random number. If you're unlucky it will be lower than total work submitted, and if you are lucky it will be greater.
You can get super lucky and get a 1T share which would take years of submitted work to "catch up" too.
And then you can hit the jackpot of course!
Has anyone hit near 1T on their Apollo II yet? Would be cool for you guys to post your best shares. Think highest we have seen is about 500B.
Also thinking about gamifying the Solo Pool and anonymously submit your best share for ranking on a site (and possibly give out prizes bases on best share as a cool incentive to solo mine without finding blocks).
Of course this would be opt in to collect this data and open source(and it would all be hashed data with no wallets or any personal data other than best share and maybe hashrate collected) but if you guys are interested might start working on it for 2.2 release.
This would also be a cool way to public display the state of the "FutureBit" hashrate network and show the impact all of you are having!
September 16, 2024, 08:31:42 PM
Out of curiosity, right now my 3 apollo 2's have hit a best share 7,632,598,247. Will it ever hit more than that? if so, is it a time thing or a luck thing?
September 16, 2024, 12:12:36 PM
Thanks it's still syncing so should be OK.
One more thing. I notice when I select System - Shutdown from the UI menu on web browser that it shuts down the node and the miner but the fans on the Apollo II are spinning at full speed and for some reason do not spin down. The system doesn't halt so I have to manually switch the box off.
Is this a known bug or any idea how to fix?
One more thing. I notice when I select System - Shutdown from the UI menu on web browser that it shuts down the node and the miner but the fans on the Apollo II are spinning at full speed and for some reason do not spin down. The system doesn't halt so I have to manually switch the box off.
Is this a known bug or any idea how to fix?
September 16, 2024, 11:31:23 AM
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
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
September 16, 2024, 05:21:22 AM
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
screen -dmS node /opt/apolloapi/backend/node/bitcoind -reindex -datadir=/media/nvme/Bitcoin -conf=/opt/apolloapi/backend/node/bitcoin.conf
September 16, 2024, 05:08:09 AM
I see this in debug.log
Maybe I can restart somehow with reindex but can I do from command line. hmmm.
Code:
2024-09-16T09:39:42Z Verification error: found bad undo data at 722855, hash=000000000000000000011ce102895343402ba76a411739da20634a7797c22456
2024-09-16T09:39:42Z : Corrupted block database detected.
Please restart with -reindex or -reindex-chainstate to recover.
2024-09-16T09:39:42Z Aborted block database rebuild. Exiting.
Maybe I can restart somehow with reindex but can I do from command line. hmmm.
September 16, 2024, 04:57:18 AM
My Apollo II was syncing happily and up to almost 80% synced. After a restart of the machine however the Node now refuses to come online. The UI and miner is working fine but node gives error "warning
Connection refused. Your node is not running."
I tried to manually start and it still refuses to startup
Checking the syslog on console I get this
Any ideas on how I fix this. Is the blockchain database corrupt or something and how do I get this node to start up again? Do I need to clear the bitcoin DB and how can I do this?
I also notice when I do a shutdown from the UI the fans stay on high permanently. Seems the shutdown command on the UI does not spin the fans down, only stops the services. Not sure if its normal.
Thanks in advance!
Connection refused. Your node is not running."
I tried to manually start and it still refuses to startup
Checking the syslog on console I get this
Code:
Sep 16 05:37:05 futurebit-apollo-2 node_stop.sh[21331]: No screen session found.
Sep 16 05:37:05 futurebit-apollo-2 systemd[1]: node.service: Control process exited, code=exited, status=1/FAILURE
Sep 16 05:37:05 futurebit-apollo-2 systemd[1]: node.service: Failed with result 'exit-code'.
Sep 16 05:37:05 futurebit-apollo-2 systemd[1]: node.service: Consumed 16.034s CPU time.
Any ideas on how I fix this. Is the blockchain database corrupt or something and how do I get this node to start up again? Do I need to clear the bitcoin DB and how can I do this?
I also notice when I do a shutdown from the UI the fans stay on high permanently. Seems the shutdown command on the UI does not spin the fans down, only stops the services. Not sure if its normal.
Thanks in advance!
September 14, 2024, 09:53:26 AM
I cant seem to point my s19k pro with braiins operating software to my solo mining on my apollo unit. it says invalid url.
Is your S19K running on your LAN or is it on an external network vs. your Apollo?
If your S19K is outside the LAN you must setup port forwarding on your router to allow traffic on port 3333 to be directed to the internal IP your Apollo.
If your S19K is inside your LAN then you should be able to use the data that is listed on the solo-mining page of your Apollo GUI.
"SOLO LAN Mining
Point any Bitcoin Miner on your local network to your Solo Pool with the following URL: X.X.X.X:3333 Username:
Or try:
stratum+tcp://x.x.x.x:3333 And replace the x's with your internal IP address.
September 13, 2024, 06:23:05 PM
I cant seem to point my s19k pro with braiins operating software to my solo mining on my apollo unit. it says invalid url.
September 13, 2024, 12:55:02 PM
From this monday i got an error every 24h
[GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: 2262360428
I did change to long btc adres then put i back to short one for solo mining to the node, dint change the errror.
When error happens miner tab in UI shuts down, node continue working.
I did write to support futurebit, they ignore my messange.
Please help.
[GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: 2262360428
I did change to long btc adres then put i back to short one for solo mining to the node, dint change the errror.
When error happens miner tab in UI shuts down, node continue working.
I did write to support futurebit, they ignore my messange.
Please help.
This is a known issue, update to fix is a little late but will def be out next week.
FYI it's just a front end bug and does not affect the miner or node operation.
September 13, 2024, 10:40:35 AM
From this monday i got an error every 24h
[GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: 2262360428
I did change to long btc adres then put i back to short one for solo mining to the node, dint change the errror.
When error happens miner tab in UI shuts down, node continue working.
I did write to support futurebit, they ignore my messange.
Please help.
[GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: 2262360428
I did change to long btc adres then put i back to short one for solo mining to the node, dint change the errror.
When error happens miner tab in UI shuts down, node continue working.
I did write to support futurebit, they ignore my messange.
Please help.
Jump to: