Topic: Official FutureBit Apollo BTC Software/Image and Support thread - page 5. (Read 50685 times)

Update completed successfully from the beta, no issues here!

Update completed, all seems well with Futurebit other than inop HDMI port. The newest Etcher version works fine for flashing the new MCU2 v2.0.6. Old Etcher (v1.18.11) fails to load on my Mac now, advises to immediately dismount or will cause damage.

Up and running v2.0.6!! Flawless and quick update. Running great. Thank you so much for the update.

New release is finally out...apologize once again for this being over a month late but this should have squashed a large number of bugs and should be super stable before we start working on a big 2.1 feature release.

As always if you do an OTA update please wait at least half an hour or simply close the tab out and start a new one and wait for the UI to come up (if UI shows 0% update has finishes and you can refresh)

2.1 will also include a new update mechanism that will eliminate update failure and make process way smoother

Apollo OS v2.0.6 - 11/26/24

https://github.com/jstefanop/apolloapi-v2/releases/tag/v2.0.6

New Changes in v2.0.6:

- Redesigned Solo Miner Page making it easy to keep track of multiple miners/wallets mining on the solo pool! Stats are organized by individual wallet addresses, and each wallet address can have multiple workers  (ie address.worker1 address.worker2 etc).
- Node connection count has been upped to 64 connections by default for more robust peering especially during solo mining
- Pesky 32bit and graphQL errors have finally been squashed...small number of users that were affected by this should not see this again
- UI improvements, especially for small format screens and mobile UI
- Improved reliability of node startup during boot, which should reduce "Connection Refused" Node errors for some users
- Multiple UI bug fixes, and backend improvements

Dont see any open tickets from those dates...DM me your email

I have sent 2 separate emails to your support team and have received zero replies. Sent the first one on 11/19/24 and the second one on 11/21/24....

Finishing the image build today before we push the update...want to make sure images are out in case of OTA update failures.

The reformat option in the UI will give me the "success" message and states the node will restart. But it will not start and sync.

The computer does not detect the NVME SSD at all it seems. To further explore this I restarted the system without any NVME connected at all. The machine restarts and when I pass the -reindex command, the location /media/nvme/bitcoin will populate with the correct default files and the node will start and begin to sync. With no SSD attached, I guess I conclude this is going onto the microSD. I've done this with the current Apollo OS and the original OS.

With an adapter, the NVME SSD can be detected on the Apollo and on another linux laptop.

Seems like it could be an internal NVME connector hardware problem in the Apollo. But if anything else comes to mind please advise.

Do you have an idea of approximately when 2.06 will be ready for prime time?

Thank you so very much!!

Please see the ssh instructions on how to update below:


Then all you need to do is point your bitaxe to the IP address listed at the top of your solomining page on your apollo...

"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: "

So your stratum URL in the BitAxe will be the IP address of your Apollo. 
Port will be 3333
stratum user will be your bitcoinaddress.workername

Save the settings on your bitaxe and restart.

And that should do it!

Two questions: Any eta on this error being fixed?

Logo Overview Miner SOLO Mining Node System Settings [GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: 4193135690

Any good instructions on pointing my bitaxe to my Apollo2 solo node?

Thanks very much for the reply.  I'm still waiting for your support team to reply to my support request (via your support page widget). I would like to replace the switch myself.

Of course we will warranty, all Apollo II units have at least 6 months of warranty left. If you have a bad switch we can either setup an RMA or send you the replacement if you feel like swapping it out yourself to save downtime. It's a pretty easy snap in module, but you need to cut off the tabs or take both top and bottom covers off to squeeze the old one through the case.

If you have access to media/nvme/Bitcoin, then you have access to your nvme drive, that is your nvme drive.  You may have to reformat the nvme card within the Apollo GUI.  Wait for the message, completed as it takes some time to format with no indicator its working on it.  The microsd is the main drive for system files.  Please clarify which drive you are talking about.  SD card to me is microsd and no bitcoin data is stored there other than apollo program files.

I had a corrupted chainstate file recently.  My best solution was to delete the chainstate files, which is done by reindex-chainstate anyway, and copy the old chainstate files from my backup from a month ago.  My database files were ok.  the node updated the chainstate and caught up to the current blocks.  I then backed up the nvme with the newest block set.
my node and miner have been running non-stop for 7 days with no errors.

RE: other miners
The solo apolllo node is a pool miner.  Apollo node bitcoind sends the information the other miners who request the data from the node.  The miner within the apollo is a program like any othe miner requesting data from a pool it just so happens the pool is the apollo node itself.  You can see this in the logs.  just like any other pool on the bitcoin network, but it's your own private pool.  Each miner has its own success rate.  no prioirty or privilage.   Each miner on your node will receive updated live transaction blocks used to mine the next successful block.  The pool doesn't know what equipment is trying to connect.  it will only see the difficulty of the miner that requests the data and adjust difficulty for performance.

Success?  I had a small futurebit moonlander running for over a year and it hit best shares upwards of 1 billion and once hit over 1 trillion(still not enough to solve a block). 

Still waiting to hear from Futurebit to see if they will warranty my unit.  I don't want to open it up before I hear from them, but what are the steps to get to the switch?

I have 2 Avalon Nano3 miners mining thru my Apollo and so far the Avalon's have hit higher best shares, they are all mining independently of each other.

An unexpected issue occurring upon system startup.

The NVME SSD is not mounting. It's not detected in Disks, or GParted, or command line prompts like -lsblk.

The node will start upon -reindex with the data-dir at /media/nvme/bitcoin, but that data is existing on the SD card. The NVME SSD remains unreachable.

Might this be something to address in BIOS settings?

The SSD itself is in working order and will mount via USB in another Ubuntu laptop.

I should have clarified that I am SOLO mining. I am just wondering whether hooking up a different miner (from a different manufacturer like BitAxe) to the Apollo 2 node/miners will result in a proper distribution of work assigned to each of the Apollo and non-Apollo miners. I want to make sure that the BitAxe doesn't replicate the same hashes as the Apollo miners but hashes on a different set of nonces (or extra nonces).

@jstefanop, can you please confirm?

The way I understand it is, all miners are working to solve the same next block, and it's more of a race to see you cracks it first. There are some advantages some have, a few are due to internet connections and some pools/miners are thought to hold back, so they can start on the next one before anybody else. I tend to think this is a possibility when you see a pool/large miner hit 2 blocks minutes apart.