Official FutureBit Apollo II/BTC Software/Image and Support thread

[OlympicSSJ]

Sounds like a compatibility issue.   I'd go with the 1TB for now that works.  After the full blockchain is downloaded you can copy the nvme later.
Would a USB to NVME be detected and compatible with the 2TB installed into the USB?  This could allow you to copy the data.  If you could mirror the 1TB to 2TB after full download would the mirroring solve the compatibility issue?  Good catch on startup error message.

Does the raspberry Pi onboard the Apollo 2 have an Eeprom? And is it possible the fix the incompatibility issue I'm having with my 2TB nvme by installing the latest official raspberry eeprom?
And if I do that are there any settings I'll mess up which will result in the apollo OS not working as it should? Thanks in advance

(Btw the 1tb older nvme is syncing the blockchain is at 80% at the moment)

[eagleye]

You have time probably at least a year before you need to upgrade to 2tb.

To clarify, it's ARMBIAN OS that Futurebit software modified to add ckpool, node and bitcoind in the futurebit format and connect the miner.  I think there should be a software download only really needed.   So there should be an update.  Check with the memory manufacturer too.  It is an Orange Pi running in the system?  Ubuntu 22 Linux.  They also say up to 2TB.  Maybe if futurebit has a list of compatible 2TB nvme or what does the ARM core work with?

[OlympicSSJ]

You have time probably at least a year before you need to upgrade to 2tb.

To clarify, it's ARMBIAN OS that Futurebit software modified to add ckpool, node and bitcoind in the futurebit format and connect the miner.  I think there should be a software download only really needed.   So there should be an update.  Check with the memory manufacturer too.  It is an Orange Pi running in the system?  Ubuntu 22 Linux.  They also say up to 2TB.  Maybe if futurebit has a list of compatible 2TB nvme or what does the ARM core work with?

Yes, you are right, now that I checked its Orange Pi 4 LTS 4gb, checked on their website and the only thing I found was this in the user manual :

"When purchasing, be sure to choose an M.2 NGFF SSD that supports the NVMe
protocol. The corresponding M.2 interface is of the M key type. SSDs that meet this
requirement should be able to support it. If it is an M.2 NGFF SSD of the SATA
protocol, it is not supported. Yes, you can check this link for information on the M.2
interface:"

Anyway, I think my Kingston NV3 complies with this. I also asked in the Orange Pi reddit subsection, but for some reason they deleted my thread...
It would be nice if futurebit fix the incompatibility issue in a future update. Thanks for answering.

Actually, when you mentioned ckpool, once the node syncs completely I can mine to my node directly, right? Or do I still need ckpool in anyway? Thanks!

[eagleye]

ckpool is the software your apollo runs on to mine with the node.  You become your own bitcoin pool mining site.  you can direct other bitcoin miners you have to this pool.  On your local network.  You are your own pool.

This is not the solo.ckpool on the web that you can point your bitcoin miners to.  Yep a little confusing.

You say you formatted it in the windows PC ntfs.  could that have set any bitlocker on the nvme which is preventing it from being formatted or read linux?  . Have you tried deleting the NTFS partition in windows so nothing exists on the nvme.

I have a USB to pcie and I am able to plug into the usb 3.0 port and the NVME is recognized.  there are also nvme clone devices that can clone one card to another.  After the blockchain downloads you could try cloning the 1 TB card.  nvme cloners will copy the database much faster than the USB I use to backup the database.

OR what about another brand of 2TB NVME card.  We can never have enough memory cards.

I had a problem with the microsd system memory card provided with the Apollo II.  My system kept crashing.  I bought a newer bigger faster microsd and my problems went away. 

[Knotbush]

quick question...

Currently running an Apollo 2 SOLO. I ordered a Apollo Standard to plug into the Apollo 2. When I plug this in, will it show as a separate worker or add it's hashing power to the main system?

Will it show up in the FutureBit OS in a way that allows me to change it's settings etc. like the onboard miner?

Thanks!

[Golddustpeak]

I just received an older Apollo BTC  Batch1 - batch3. and flashed it  to 2.0.6.

It is up running hashing to a pool and loading the node.

Looking over the comments in this link I begin to wonder if I should be looking for a 2Tb NVME to replace my 1Tb in the near future..

If so should I worry about brands and speeds?
And is it just a simple swap-out?

TNX

I just answered my own question.
From a fresh format of the 1Tb NMVE in my Apollo BTC I ran out of disc room after loading just over 85% of the chain.

So the question now is will the Apollo BTC support a 2Tb NMVE or will I just not be able to support a node?

Where do I go from here?

[bubbAJoe]

I just received an older Apollo BTC  Batch1 - batch3. and flashed it  to 2.0.6.

It is up running hashing to a pool and loading the node.

Looking over the comments in this link I begin to wonder if I should be looking for a 2Tb NVME to replace my 1Tb in the near future..

If so should I worry about brands and speeds?
And is it just a simple swap-out?

TNX

I just answered my own question.
From a fresh format of the 1Tb NMVE in my Apollo BTC I ran out of disc room after loading just over 85% of the chain.

So the question now is will the Apollo BTC support a 2Tb NMVE or will I just not be able to support a node?

Where do I go from here?

Hmmm. For reference, I show 25.66% remaining on my 1 TB NVME that came with my Apollo II (as of today with a blockchain size of 665.74GB).

[heslo]

I just received an older Apollo BTC  Batch1 - batch3. and flashed it  to 2.0.6.

It is up running hashing to a pool and loading the node.

Looking over the comments in this link I begin to wonder if I should be looking for a 2Tb NVME to replace my 1Tb in the near future..

If so should I worry about brands and speeds?
And is it just a simple swap-out?

TNX

I just answered my own question.
From a fresh format of the 1Tb NMVE in my Apollo BTC I ran out of disc room after loading just over 85% of the chain.

So the question now is will the Apollo BTC support a 2Tb NMVE or will I just not be able to support a node?

Where do I go from here?

Hmmm. For reference, I show 25.66% remaining on my 1 TB NVME that came with my Apollo II (as of today with a blockchain size of 665.74GB).

Same here, still plenty of space left on my 1TB

[Golddustpeak]

I'll reformat and try again.
When it said it was full at the mid 80s% it was reporting 445Gb +.

[jstefanop]

I am running V2.06. I purchased a Full node and a standard weeks ago.  From day 1, the full node has not worked. The box disconnects, locks up, and hasn't moved past 15%; numerous connections have been refused.  I've reflashed the SD card, performed a format on the SSD drive innumerable times, and even placed two node configuration lines provided by Futurebit support (dbcache=128 and maxmempool=128); both did nothing.  I went through all my firewall settings, as I have a Firewall router, and placed the full node IP address in emergency mode, which essentially opens all ports and disables all existing rules and policies that did not work.  I connected it directly to my ISP via WIFI, that did not work.  At this point, I feel like I'm doing FutureBit's job, and I didn't pay $1,700 to play helpdesk support on my own.  I also tried to reflash the SD card to version 2.05, as some stated that the version was much more stable, but that did not work.

The most disappointing experience was that I purchased over $1,700 of equipment and have not received one response from Future Bit for days, except one email, which took almost 4 days to respond.  I am incredibly frustrated with the equipment and lack of support.

Yeah, FB support response time is pathetic.  Not sure what the issue is...

Unfortunately, service has always been the first area within an organization to suffer the short-sighted and unprepared policies of any company rushing to meet marketing and profit demands. It's repeated time and again, over & over with large and small companies alike. Sometimes it's simply a matter of the "flood & run" approach whereas a company will intentionally start with a few quality pieces and when sales shoot up they switch to inferior pieces and then jump ship and disappear after enough complaints and a huge drop in sales. This is common on AMZ. Now, sometimes it's not as devious or the intention is/was honorable and they simply didn't start out prepared or misunderstand the market base. They get inundated with the service costs related to their misguided, unfortunate, and hopeful outlook. Service time and parts always costs money and NEVER makes a profit. And sometimes, a company is as sincere as professing your feelings to your first love but still can't seem to get it right. But I like to believe there are at least a few companies out there really trying to make a quality product at a fair price and stand behind it after the money has been gathered. However, if they didn't set aside enough for service . . . well, it could be a repeat of a very old story. I, for one, still have a positive outlook on Futurebit.

Cheers!

Most people seem misguided on what FutureBit is. We are not a "company" nor do we have VC money, any profits or marketing department or any of that nonsense. It's literally half a dozen engineers making cool products for home miners.

We do the best with what we have, and that includes not responding to support email for a week during the holidays. Sorry but not sorry.

You get what you pay for, you either get a corporate VC backed shitshow that collects and steals your data and sells all your activity to the highest bidder, or a device that costs double what it costs now to sell in order to have some guy sitting in chat 24/7.

I decided to go the middle ground...keep my independence and mission to decentralize bitcoin, sell hardware at nearly at cost to you guys, with the drawback of not instant support, or cool marketing, or other fancy things that dont move the needle of what we are here for.

Sure if we end up selling a million devices we will need more support, but we are not there yet and we are one of the longest surviving hardware companies in bitcoin because of it.

I am running V2.06. I purchased a Full node and a standard weeks ago.  From day 1, the full node has not worked. The box disconnects, locks up, and hasn't moved past 15%; numerous connections have been refused.  I've reflashed the SD card, performed a format on the SSD drive innumerable times, and even placed two node configuration lines provided by Futurebit support (dbcache=128 and maxmempool=128); both did nothing.  I went through all my firewall settings, as I have a Firewall router, and placed the full node IP address in emergency mode, which essentially opens all ports and disables all existing rules and policies that did not work.  I connected it directly to my ISP via WIFI, that did not work.  At this point, I feel like I'm doing FutureBit's job, and I didn't pay $1,700 to play helpdesk support on my own.  I also tried to reflash the SD card to version 2.05, as some stated that the version was much more stable, but that did not work.

The most disappointing experience was that I purchased over $1,700 of equipment and have not received one response from Future Bit for days, except one email, which took almost 4 days to respond.  I am incredibly frustrated with the equipment and lack of support.

Yeah, FB support response time is pathetic.  Not sure what the issue is...

Unfortunately, service has always been the first area within an organization to suffer the short-sighted and unprepared policies of any company rushing to meet marketing and profit demands. It's repeated time and again, over & over with large and small companies alike. Sometimes it's simply a matter of the "flood & run" approach whereas a company will intentionally start with a few quality pieces and when sales shoot up they switch to inferior pieces and then jump ship and disappear after enough complaints and a huge drop in sales. This is common on AMZ. Now, sometimes it's not as devious or the intention is/was honorable and they simply didn't start out prepared or misunderstand the market base. They get inundated with the service costs related to their misguided, unfortunate, and hopeful outlook. Service time and parts always costs money and NEVER makes a profit. And sometimes, a company is as sincere as professing your feelings to your first love but still can't seem to get it right. But I like to believe there are at least a few companies out there really trying to make a quality product at a fair price and stand behind it after the money has been gathered. However, if they didn't set aside enough for service . . . well, it could be a repeat of a very old story. I, for one, still have a positive outlook on Futurebit.

Cheers!

I am a bit concerned about burning switch/es for devices that are running in most buyers' houses...

I recommend everyone pull the bottom off (3x phillips screws and 1x torx security screw under the black pads) and then punch out the top from below with a screw driver (just held in with light glue) and look at your switch leads.

I posted links to pictures of the burned leads from my original switch (post #2813).

This has been addressed multiple times. The core issue is a rare failure mode of the switch when the AC plug is not in the socket all the way, causing a slight heat buildup that eventual fails the switch.

We fixed the issue switch side with recent builds even if users dont plug the AC socket in all the way, and have sent multiple emails out to all Apollo users alerting of the issue. We are covering all switch replacements under warranty either way by either mailing in a replacement switch (its pretty easy too swap out) or sending it via RMA to have it repaired here.

You have time probably at least a year before you need to upgrade to 2tb.

To clarify, it's ARMBIAN OS that Futurebit software modified to add ckpool, node and bitcoind in the futurebit format and connect the miner.  I think there should be a software download only really needed.   So there should be an update.  Check with the memory manufacturer too.  It is an Orange Pi running in the system?  Ubuntu 22 Linux.  They also say up to 2TB.  Maybe if futurebit has a list of compatible 2TB nvme or what does the ARM core work with?

The only officially supported NVMe drives are Kingston NV2s and Curcial P2/P3s.

We have also noticed some newer Gen4 drives are not compatible and this is a hardware issue. Our custom SSD drive adapter for this board is only designed for 2x PCIe Gen 2 lanes.

There is no need to buy higher end NVMe drives for this system as its a waste, they will either fail because they draw to much power, or newer Gen4 pcie protocol is incompatible with our hardware.

We are currently sourcing Kingston NV3 drives, but only one type with a certain controller works with our system, they have two types with a different controller that does not work.

Also I know 660GB/1TB seems like the drive is almost full, but bitcoin is growing at about 100GB/Y even in its current maxed out full blocks state. 1TB drives have at least 2-3 years of life left, and 2TB drives will literally last the life of the system at over 10 years.

2TB is boarderline overkill, 1TB will last enough where you can get a 2TB for half the cost in 2 years.

[moderator's note: consecutive posts merged]

[Opazzno]

It turns out that if I have a non-recommended NVME disk, for example, a 2TB pioneer, the system may not work stably? How can I, for example, rewrite the BTC database to a new NVME disk? Can I connect a new disk to the Apollo 2 node via a USB adapter and how can I rewrite the database?

[Golddustpeak]

I just received an older Apollo BTC  Batch1 - batch3. and flashed it  to 2.0.6.

It is up running hashing to a pool and loading the node.

Looking over the comments in this link I begin to wonder if I should be looking for a 2Tb NVME to replace my 1Tb in the near future..

If so should I worry about brands and speeds?
And is it just a simple swap-out?

TNX

I just answered my own question.
From a fresh format of the 1Tb NMVE in my Apollo BTC I ran out of disc room after loading just over 85% of the chain.

So the question now is will the Apollo BTC support a 2Tb NMVE or will I just not be able to support a node?

Where do I go from here?

Hmmm. For reference, I show 25.66% remaining on my 1 TB NVME that came with my Apollo II (as of today with a blockchain size of 665.74GB).

Same here, still plenty of space left on my 1TB

Third time and it is full in the mid 80% again
The first time I ran it out of the box and the next two times I used the Apollo BTC format function.
Each time the used % and free % look great up till it gets into the 70% used and then all of a sudden it is clear that there is no longer enough space remaining.

Where do I go from here?

[rayday11]

I just received an older Apollo BTC  Batch1 - batch3. and flashed it  to 2.0.6.

It is up running hashing to a pool and loading the node.

Looking over the comments in this link I begin to wonder if I should be looking for a 2Tb NVME to replace my 1Tb in the near future..

If so should I worry about brands and speeds?
And is it just a simple swap-out?

TNX

I just answered my own question.
From a fresh format of the 1Tb NMVE in my Apollo BTC I ran out of disc room after loading just over 85% of the chain.

So the question now is will the Apollo BTC support a 2Tb NMVE or will I just not be able to support a node?

Where do I go from here?

Hmmm. For reference, I show 25.66% remaining on my 1 TB NVME that came with my Apollo II (as of today with a blockchain size of 665.74GB).

Same here, still plenty of space left on my 1TB

Third time and it is full in the mid 80% again
The first time I ran it out of the box and the next two times I used the Apollo BTC format function.
Each time the used % and free % look great up till it gets into the 70% used and then all of a sudden it is clear that there is no longer enough space remaining.

Where do I go from here?

I always remove and recreate, all disk partitions, prior to reformatting any storage devices.

[Golddustpeak]

I just received an older Apollo BTC  Batch1 - batch3. and flashed it  to 2.0.6.

It is up running hashing to a pool and loading the node.

Looking over the comments in this link I begin to wonder if I should be looking for a 2Tb NVME to replace my 1Tb in the near future..

If so should I worry about brands and speeds?
And is it just a simple swap-out?

TNX

I just answered my own question.
From a fresh format of the 1Tb NMVE in my Apollo BTC I ran out of disc room after loading just over 85% of the chain.

So the question now is will the Apollo BTC support a 2Tb NMVE or will I just not be able to support a node?

Where do I go from here?

Hmmm. For reference, I show 25.66% remaining on my 1 TB NVME that came with my Apollo II (as of today with a blockchain size of 665.74GB).

Same here, still plenty of space left on my 1TB

Third time and it is full in the mid 80% again
The first time I ran it out of the box and the next two times I used the Apollo BTC format function.
Each time the used % and free % look great up till it gets into the 70% used and then all of a sudden it is clear that there is no longer enough space remaining.

Where do I go from here?

I always remove and recreate, all disk partitions, prior to reformatting any storage devices.

Not an option in the Apollo BTS Settings..Extra..Format

[eagleye]

It turns out that if I have a non-recommended NVME disk, for example, a 2TB pioneer, the system may not work stably? How can I, for example, rewrite the BTC database to a new NVME disk? Can I connect a new disk to the Apollo 2 node via a USB adapter and how can I rewrite the database?

As described earlier, you can copy the bitcoin database to a USB connected nvme drive interface.  Takes under 1 hour these days on my Apollo II.  Make sure your node is stopped and your miner is stopped.  You all should do this every 2 to 4 weeks anyway so you have a bitcoin backup.  any sort of power outage can corrupt the memory.

You could also purchase a nvme clone device that will copy the data NVME to NVME pretty fast.

The format command in apollo wipes the drive.  

jstefanop has answered the question about what nvme 2TB is compatible with these systems.  Hardware compatibility. These cards will be cheaper than the newer faster cards.  read write speeds are only in the 100-200MB / sec range. USB 3.0 speed.  This is a simple system designed for running a node and a miner.  nothing fancy.

Look around the system monitor.  Watch the activity of the bitcoind program and the node program and the ckpool program if mining.  You can see read/write activity of the bitcoind being the most active.

Regarding the nvme running out of space, what does the system monitor say is left on the nvme?  Do you get an error message?  the system monitor will tell you space used vs space available.  So you say at 80% complete, you have 0% nvme disk space remaining?

how much space used is reported by apollo on the bitcoin database?  percentage is a relative number.  What is the actual GB number used vs free

[PZ]

I am running V2.06. I purchased a Full node and a standard weeks ago.  From day 1, the full node has not worked. The box disconnects, locks up, and hasn't moved past 15%; numerous connections have been refused.  I've reflashed the SD card, performed a format on the SSD drive innumerable times, and even placed two node configuration lines provided by Futurebit support (dbcache=128 and maxmempool=128); both did nothing.  I went through all my firewall settings, as I have a Firewall router, and placed the full node IP address in emergency mode, which essentially opens all ports and disables all existing rules and policies that did not work.  I connected it directly to my ISP via WIFI, that did not work.  At this point, I feel like I'm doing FutureBit's job, and I didn't pay $1,700 to play helpdesk support on my own.  I also tried to reflash the SD card to version 2.05, as some stated that the version was much more stable, but that did not work.

The most disappointing experience was that I purchased over $1,700 of equipment and have not received one response from Future Bit for days, except one email, which took almost 4 days to respond.  I am incredibly frustrated with the equipment and lack of support.

Another one with a similar problem. I bought it new and it gives an error when synchronizing the node. It always stays on the same block. It fails on wifi and lan. The error always occurs in the same place, regardless of whether the miner is on or not. Does anyone who has solved it already have a way to solve this problem?

[Franck68]

Hi guys,
Just bought a full node. It's updating pretty quickly...almost done in 3 days. As soon as it's 100%, I'll start mining solo.
I'd like to also run a Lighnting node and provide liquidity. Any solution you recommend?

Thanks,
Franck

[eagleye]

I am running V2.06. I purchased a Full node and a standard weeks ago.  From day 1, the full node has not worked. The box disconnects, locks up, and hasn't moved past 15%; numerous connections have been refused.  I've reflashed the SD card, performed a format on the SSD drive innumerable times, and even placed two node configuration lines provided by Futurebit support (dbcache=128 and maxmempool=128); both did nothing.  I went through all my firewall settings, as I have a Firewall router, and placed the full node IP address in emergency mode, which essentially opens all ports and disables all existing rules and policies that did not work.  I connected it directly to my ISP via WIFI, that did not work.  At this point, I feel like I'm doing FutureBit's job, and I didn't pay $1,700 to play helpdesk support on my own.  I also tried to reflash the SD card to version 2.05, as some stated that the version was much more stable, but that did not work.

The most disappointing experience was that I purchased over $1,700 of equipment and have not received one response from Future Bit for days, except one email, which took almost 4 days to respond.  I am incredibly frustrated with the equipment and lack of support.

Another one with a similar problem. I bought it new and it gives an error when synchronizing the node. It always stays on the same block. It fails on wifi and lan. The error always occurs in the same place, regardless of whether the miner is on or not. Does anyone who has solved it already have a way to solve this problem?

Have you reflashed the microsd system card?  Replaced the Microsd system card and flashed a new card.  Also checked the issues with placement of the microsd card in the slot?  There was tape on mine to secure the card in transportation, which makes sense, but I think it could cause issues with card operation.

My system had a defective microsd card.  These cards seem old.  The new card worked fine and many problems I had went away.
I've had a 128GB microsd running v2.0.5 for several months without issue.  This card is new and ran 180MB/sec read  pretty well.
I felt it would take too long to claim a warranty and these cards are so cheap it would be faster to just get one to try out.

I just picked up a cheap ONN 32GB microsd at a cheap worldwide supermarket.  IT's speed is slower.  100 MBsec read / 11MBsec write.  flashed v2.0.6.  It's up and running.

The difference between the new fast 128GB card and 32GB card is there.  Here's the report: booting 128GB card and the system boots within 15 seconds main screen is up in 60 seconds.  The 32GB card took longer to boot   30 seconds boot and 90 seconds main screen.  As system is running no noticeable difference.
  Maybe slightly slower response when you click on a program.

[eagleye]

Software Bug Found:  Changing system time zone will cause miner data to reset to 0 while miner and node programs are running.  Stopping and restarting the miner did not fix the problem.
v2.0.6  apollo II

I changed the time zone on the Apollo II.  This caused all miner data to reset to 0 and not report any data.  I waited an hour and no update.  It did not affect node data and solo mining data.  Miner operated as normal and fan speed is working.  But you can't see temp data for the miner nor fan speed.

A reboot after setting the time zone did fix the problem.

[PZ]

Hi guys,
Just bought a full node. It's updating pretty quickly...almost done in 3 days. As soon as it's 100%, I'll start mining solo.
I'd like to also run a Lighnting node and provide liquidity. Any solution you recommend?

Thanks,
Franck

+1 (when finish the updating)