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

[garetjax]

I'm running v2.0.5.  I tried v2.0.6 but it kept crashing on my apollo.  Have you tried reverting  back to v2.0.5 and if so, is that network issue stable on the old version?  I would think it's a problem with the network adapter, initially.  My node and miner are running happy on the old version right now.  If it ain't broke, don't fix it.

I'd love to upgrade, but it should be easy.  THe download and reboot crashed on me.  flashing a new microsd got the system to boot but then crash.

Plus I hate that when you flash a new microsd, it does not remember your address and you are forced to go through that at the initial startup.  Is there a way to skip the startup page so settings could be loaded from a backup?

I upgraded my Apollo 1 a month ago to 2.0.6 and not a single issue.  I am also running an Apollo 2 standard off of my Apollo 1.  Constant 63/64 connections.  It's in my office so it is running in eco mode.  I use an ethernet cable.

[0id1d]

Guys, what could be version 2.0.6 Apollo 2 every 2-3 days the device disappears from the network, you have to turn it off and on hard. Then it works again for 2-3 days and also disappears from the network. Although Apollo itself works when you reboot it.

I get the same thing on my Apollo 2, around every 4 days for me. I plan to switch to 2.0.5 to see if that helps anything, as per eagleye's suggestion below.

I'm running v2.0.5.  I tried v2.0.6 but it kept crashing on my apollo II.  Have you tried reverting  back to v2.0.5 and if so, is that network issue stable on the old version?  I would think it's a problem with the network adapter, initially.  My node and miner are running happy on the old version right now.  If it ain't broke, don't fix it.

My Apollo 1 is doing fine on 2.0.6, lining up with what garetjax said.

I upgraded my Apollo 1 a month ago to 2.0.6 and not a single issue.  I am also running an Apollo 2 standard off of my Apollo 1.  Constant 63/64 connections.  It's in my office so it is running in eco mode.  I use an ethernet cable.

[Hamster123]

I'm running v2.0.5.  I tried v2.0.6 but it kept crashing on my apollo.  Have you tried reverting  back to v2.0.5 and if so, is that network issue stable on the old version?  I would think it's a problem with the network adapter, initially.  My node and miner are running happy on the old version right now.  If it ain't broke, don't fix it.

I'd love to upgrade, but it should be easy.  THe download and reboot crashed on me.  flashing a new microsd got the system to boot but then crash.

Plus I hate that when you flash a new microsd, it does not remember your address and you are forced to go through that at the initial startup.  Is there a way to skip the startup page so settings could be loaded from a backup?

I upgraded my Apollo 1 a month ago to 2.0.6 and not a single issue.  I am also running an Apollo 2 standard off of my Apollo 1.  Constant 63/64 connections.  It's in my office so it is running in eco mode.  I use an ethernet cable.

Wanted to add that I have upgraded my Apollo 1 and Apollo 2 units to version 2.0.6 with zero issues as well. They have been running well in all modes with not a single hiccup.

The only issue I have had since the upgrade is with my original Apollo 1 units running on wifi (my Apollo 2 units are hardwired to the network). I have very strong, fast, and reliable wifi (tested) but wanted to continue using the unit in my "back hall/mud room" where I have no Ethernet cable access. What I did to solve the issue was to set-up an "old but still good" wireless router as a wifi relay in the mud room and connected the Apollo to it with a short Ethernet cable. Zero issues since leading me to believe the new software has issues with wifi???...

To the individual with troubles getting the node synced: There are many good tips in this thread regarding start-up and getting the node synced. Again, I had no issues with this but followed others advice and had the Apollo 2 wired to my network and NOT mining during the blockchain download. Lastly, an oddball suggestion but be sure your modem and router are not set-up to auto restart during the download as this may create a minor hiccup. Mine reboot once a week as a security measure.

[Sledge0001]

I personally have 3 Apollo Full Nodes running on 2.0.6 without any issues at all.

One is an Apollo II Founders edition, one is a Apollo II Full Node and the other unit is an Apollo BTC regular full node.

All are hardwired and all are working as they should.

[heslo]

I personally have 3 Apollo Full Nodes running on 2.0.6 without any issues at all.

One is an Apollo II Founders edition, one is a Apollo II Full Node and the other unit is an Apollo BTC regular full node.

All are hardwired and all are working as they should.

Same, my Apollo II was from the first batch and absolutely zero issues and running flawlessly since day one. Hardwired yes, never used wifi but I assume that works as well

[Opazzno]

here is my debug.log new flash drive has 2 ray every 2 days loses node need to manually run node start or apollo2 disappears from the network although the device itself works

2025-01-01T21:51:15Z No valid UPnP IGDs found
2025-01-01T21:51:34Z CreateNewBlock(): block weight: 3992799 txs: 563 fees: 1985701 sigops 13949
2025-01-01T21:52:04Z CreateNewBlock(): block weight: 3992582 txs: 679 fees: 2031889 sigops 14263
2025-01-01T21:52:34Z CreateNewBlock(): block weight: 3992586 txs: 772 fees: 2086818 sigops 13033
2025-01-01T21:53:04Z CreateNewBlock(): block weight: 3992704 txs: 816 fees: 2169763 sigops 13255
2025-01-01T21:53:34Z CreateNewBlock(): block weight: 3992467 txs: 933 fees: 2226091 sigops 13469
2025-01-01T21:54:04Z CreateNewBlock(): block weight: 3992603 txs: 1036 fees: 2281130 sigops 13964
2025-01-01T21:54:34Z CreateNewBlock(): block weight: 3992804 txs: 1074 fees: 2506953 sigops 15591
2025-01-01T21:55:04Z CreateNewBlock(): block weight: 3992737 txs: 1199 fees: 2559036 sigops 16368
2025-01-01T21:55:34Z CreateNewBlock(): block weight: 3992807 txs: 1253 fees: 2625834 sigops 16595
2025-01-01T21:56:04Z CreateNewBlock(): block weight: 3992811 txs: 1405 fees: 2701461 sigops 16322
2025-01-01T21:56:17Z No valid UPnP IGDs found
2025-01-01T21:56:34Z CreateNewBlock(): block weight: 3992796 txs: 1601 fees: 2764212 sigops 16640
2025-01-01T21:57:04Z CreateNewBlock(): block weight: 3992682 txs: 1550 fees: 2813007 sigops 16785
2025-01-01T21:57:34Z CreateNewBlock(): block weight: 3992695 txs: 1708 fees: 2879384 sigops 16656
2025-01-01T21:58:04Z CreateNewBlock(): block weight: 3992444 txs: 1747 fees: 2952874 sigops 16378
2025-01-01T21:58:34Z CreateNewBlock(): block weight: 3992596 txs: 1796 fees: 3030314 sigops 16575
2025-01-01T21:59:04Z CreateNewBlock(): block weight: 3992460 txs: 1930 fees: 3077309 sigops 16451
2025-01-01T21:59:34Z CreateNewBlock(): block weight: 3992600 txs: 1993 fees: 3121150 sigops 16114
2025-01-01T22:00:04Z CreateNewBlock(): block weight: 3992777 txs: 2022 fees: 3179319 sigops 16386
2025-01-01T22:00:34Z CreateNewBlock(): block weight: 3992816 txs: 2149 fees: 3232932 sigops 16204
2025-01-01T22:01:04Z CreateNewBlock(): block weight: 3992803 txs: 2240 fees: 3292611 sigops 15943
2025-01-01T22:01:19Z No valid UPnP IGDs found
2025-01-01T22:01:34Z CreateNewBlock(): block weight: 3992664 txs: 2320 fees: 3373522 sigops 15984
2025-01-01T22:02:04Z CreateNewBlock(): block weight: 3992525 txs: 2451 fees: 3440436 sigops 15822





2025-01-02T03:05:17Z Bitcoin Core version v25.1.0 (release build)
2025-01-02T03:05:17Z Using the 'arm_shani(1way,2way)' SHA256 implementation
2025-01-02T03:05:17Z Default data directory /home/futurebit/.bitcoin
2025-01-02T03:05:17Z Using data directory /media/nvme/Bitcoin
2025-01-02T03:05:17Z Config file: /opt/apolloapi/backend/node/bitcoin.conf
2025-01-02T03:05:17Z Config file arg: daemon="0"
2025-01-02T03:05:17Z Config file arg: maxconnections="64"
2025-01-02T03:05:17Z Config file arg: rpcpassword=****
2025-01-02T03:05:17Z Config file arg: rpcuser=****
2025-01-02T03:05:17Z Config file arg: server="1"
2025-01-02T03:05:17Z Config file arg: uacomment="FutureBit-Apollo-Node"
2025-01-02T03:05:17Z Config file arg: upnp="1"
2025-01-02T03:05:17Z Config file arg: zmqpubhashblock="tcp://127.0.0.1:28332"
2025-01-02T03:05:17Z Command-line arg: conf="/opt/apolloapi/backend/node/bitcoin.conf"
2025-01-02T03:05:17Z Command-line arg: datadir="/media/nvme/Bitcoin"
2025-01-02T03:05:17Z Using at most 64 automatic connections (1024 file descriptors available)
2025-01-02T03:05:17Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2025-01-02T03:05:17Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2025-01-02T03:05:17Z Script verification uses 5 additional threads
2025-01-02T03:05:17Z scheduler thread start
2025-01-02T03:05:17Z Binding RPC on address ::1 port 8332
2025-01-02T03:05:17Z Binding RPC on address 127.0.0.1 port 8332
2025-01-02T03:05:17Z [http] creating work queue of depth 16
2025-01-02T03:05:17Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation.
2025-01-02T03:05:17Z [http] starting 4 worker threads
2025-01-02T03:05:17Z Using wallet directory /media/nvme/Bitcoin
2025-01-02T03:05:17Z init message: Verifying wallet(s)…
2025-01-02T03:05:17Z Using /16 prefix for IP bucketing
2025-01-02T03:05:17Z init message: Loading P2P addresses…
2025-01-02T03:05:17Z Loaded 64731 addresses from peers.dat  502ms
2025-01-02T03:05:17Z init message: Loading banlist…
2025-01-02T03:05:17Z SetNetworkActive: true
2025-01-02T03:05:17Z Cache configuration:
2025-01-02T03:05:17Z * Using 2.0 MiB for block index database
2025-01-02T03:05:17Z * Using 8.0 MiB for chain state database
2025-01-02T03:05:17Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2025-01-02T03:05:17Z init message: Loading block index…
2025-01-02T03:05:17Z Assuming ancestors of block 000000000000000000035c3f0d31e71a5ee24c5aaf3354689f65bd7b07dee632 have valid signatures.
2025-01-02T03:05:17Z Setting nMinimumChainWork=000000000000000000000000000000000000000044a50fe819c39ad624021859
2025-01-02T03:05:17Z Opening LevelDB in /media/nvme/Bitcoin/blocks/index
2025-01-02T03:05:17Z Opened LevelDB successfully
2025-01-02T03:05:17Z Using obfuscation key for /media/nvme/Bitcoin/blocks/index: 0000000000000000
2025-01-02T03:05:28Z LoadBlockIndexDB: last block file = 4694
2025-01-02T03:05:28Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=10, size=17434310, heights=877370...877379, time=2025-01-01...2025-01-01)
2025-01-02T03:05:28Z Checking all blk files are present...
2025-01-02T03:05:32Z Initializing chainstate Chainstate [ibd] @ height -1 (null)
2025-01-02T03:05:32Z Opening LevelDB in /media/nvme/Bitcoin/chainstate
2025-01-02T03:05:32Z Opened LevelDB successfully
2025-01-02T03:05:32Z Using obfuscation key for /media/nvme/Bitcoin/chainstate: 003ea10262d84768
2025-01-02T03:05:32Z Loaded best chain: hashBestChain=000000000000000000009821dfc899029a1c91193667078ca010c5e71308c0d8 height=877262 date=2025-01-01T00:41:29Z progress=0.999693
2025-01-02T03:05:33Z [snapshot] allocating all cache to the IBD chainstate
2025-01-02T03:05:33Z Opening LevelDB in /media/nvme/Bitcoin/chainstate
2025-01-02T03:05:33Z Opened LevelDB successfully
2025-01-02T03:05:33Z Using obfuscation key for /media/nvme/Bitcoin/chainstate: 003ea10262d84768
2025-01-02T03:05:33Z [Chainstate [ibd] @ height 877262 (000000000000000000009821dfc899029a1c91193667078ca010c5e71308c0d8)] resized coinsdb cache to 8.0 MiB
2025-01-02T03:05:33Z [Chainstate [ibd] @ height 877262 (000000000000000000009821dfc899029a1c91193667078ca010c5e71308c0d8)] resized coinstip cache to 440.0 MiB
2025-01-02T03:05:33Z init message: Verifying blocks…
2025-01-02T03:05:33Z Verifying last 6 blocks at level 3
2025-01-02T03:05:33Z Verification progress: 0%
2025-01-02T03:05:34Z Verification progress: 16%
2025-01-02T03:05:35Z Verification progress: 33%
2025-01-02T03:05:38Z Verification progress: 50%
2025-01-02T03:05:40Z Verification progress: 66%
2025-01-02T03:05:41Z Verification progress: 83%
2025-01-02T03:05:43Z Verification progress: 99%
2025-01-02T03:05:43Z Verification: No coin database inconsistencies in last 6 blocks (11516 transactions)
2025-01-02T03:05:43Z  block index           25965ms
2025-01-02T03:05:43Z Setting NODE_NETWORK on non-prune mode
2025-01-02T03:05:43Z block tree size = 877380
2025-01-02T03:05:43Z nBestHeight = 877262
2025-01-02T03:05:43Z loadblk thread start
2025-01-02T03:05:43Z mapport thread start
2025-01-02T03:05:43Z torcontrol thread start
2025-01-02T03:05:43Z Bound to 127.0.0.1:8334
2025-01-02T03:05:43Z Bound to [::]:8333
2025-01-02T03:05:43Z Bound to 0.0.0.0:8333
2025-01-02T03:05:43Z 0 block-relay-only anchors will be tried for connections.
2025-01-02T03:05:43Z init message: Starting network threads…
2025-01-02T03:05:43Z addcon thread start
2025-01-02T03:05:43Z net thread start
2025-01-02T03:05:43Z dnsseed thread start
2025-01-02T03:05:43Z Waiting 300 seconds before querying DNS seeds.
2025-01-02T03:05:43Z opencon thread start
2025-01-02T03:05:43Z msghand thread start
2025-01-02T03:05:45Z No valid UPnP IGDs found
2025-01-02T03:05:46Z UpdateTip: new best=00000000000000000001dc93c4f86ef1a622fa9b3bbf748edc98e1104d79277a height=877263 version=0x21822000 log2_work=95.360142 tx=1138153417 date='2025-01-01T00:52:36Z' progress=0.999696 cache=

[HITECH122]

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.

[bubbAJoe]

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...

[jdh3]

Are there any logs to see from the solo pool?  Any real time logs? Any way to tweak the settings on the pool side?  Just wondering if we are flying totally blind and can't really tweak anything?  Im happy with everything just hoping there was a way to see what its doing or tweak things or workers.

[eagleye]

Yup.

debug.log in the bitcoin directory tells you a lot.  every restart of bitcoind will reset the log to a 10MB file size limit.  It grows as the bitcoind runs.  until the next restart of bitcoind.
this is in the nvme/bitcoin directory.  If you open a terminator window change to the /media/nvme/Bitcoin directory. you can follow the log live with the command "tail -f debug.log."  You are looking at constant data produced.  If the log is frozen you need to check the system monitor and make sure your bitcoind program is running.

There is also a log in Ckpool directory  on microsd that you can do the same to.  It shows the miner operation and data result updates.  Not as important.  It can show if the miner is frozen or not getting blockchain data.

I leave 2 terminator windows open monitoring these files realtime. 

debug.log shows when you startup the bitcoind and if you can watch the nvme activity( with an activity LED on the nvme drive) you may notice the bitcoind write the chainstate, also in the system monitor file read/write activity.  Takes several minutes.  the debug.log proves the chainstate is written complete when it reports the transaction data recorded success/fail during this event.

[bubbAJoe]

So pulled the old switch (Apollo II with less than 30 days use) and it was burned.  See photos.

New switch is in and working so far.

Were the old switches just crap?  Why did it burn out?

https://1drv.ms/i/c/92c87459c7f0d8c8/ERd360Qv1cxIkGdmpSTr74ABDTX-kWdndqAJFEAhLTVndw?e=L4V1p4

https://1drv.ms/i/c/92c87459c7f0d8c8/EY9HPVeb0hRPp8eKWD_AFcMBC5-JnfX9--Z8xHOQJ1ykZQ?e=lq0aJ4

[jdh3]

Yup.

debug.log in the bitcoin directory tells you a lot.  every restart of bitcoind will reset the log to a 10MB file size limit.  It grows as the bitcoind runs.  until the next restart of bitcoind.
this is in the nvme/bitcoin directory.  If you open a terminator window change to the /media/nvme/Bitcoin directory. you can follow the log live with the command "tail -f debug.log."  You are looking at constant data produced.  If the log is frozen you need to check the system monitor and make sure your bitcoind program is running.

There is also a log in Ckpool directory  on microsd that you can do the same to.  It shows the miner operation and data result updates.  Not as important.  It can show if the miner is frozen or not getting blockchain data.

I leave 2 terminator windows open monitoring these files realtime. 

debug.log shows when you startup the bitcoind and if you can watch the nvme activity( with an activity LED on the nvme drive) you may notice the bitcoind write the chainstate, also in the system monitor file read/write activity.  Takes several minutes.  the debug.log proves the chainstate is written complete when it reports the transaction data recorded success/fail during this event.

Thank you!

[OlympicSSJ]

Hi, my Apollo 2 full node (without nvme) arrived yesterday and it can't detect my brand new Kingston NV3 2tb nvme drive... After multiple unsuccessful tries to start the node, I plugged it into my pc and formatted it to gpt ntfs partition, but the nvme still doesn't show up on the Apollo 2. When running Gparted or typing lsblk in the terminal only the sdcard shows up...
AND at the same time when I plug my pc's main nvme drive Kingston KC3000 1tb it shows up immediately.
Also tried 2.0.5 and 2.0.6 , no difference.
So, could some one help me how to make the Apollo 2 recognise the nv3 2tb nvme? Thanks

[eagleye]

Its not a windows file system.  It's a linux filesystem.  Check that the nvme is seated properly in the slot.  Shouldn' t need any force.  May take a few minutes for the apollo os to format the card and setup the Bitcoin database files.   Its supposed to format the card on initial boot.  After you log in and setup the apollo have you checked the system monitor?  You can see the nvme card there and read/write activity.  If it's not there then it wasn't detected on boot.   Shutdown/turn off and restart.  Does that memory card have LED lights you can see indicating read/write activity on card?   Does the red light turn on on the bottom of the unit where the NVME is connected?  That light tells you the card has been detected and is active.  It turns on during boot and stays on the whole time.  Is there another NVME card you can try, a 1TB or 512GB at least to just try it out to see if it responds the same? 

[OlympicSSJ]

Its not a windows file system.  It's a linux filesystem.  Check that the nvme is seated properly in the slot.  Shouldn' t need any force.  May take a few minutes for the apollo os to format the card and setup the Bitcoin database files.   Its supposed to format the card on initial boot.  After you log in and setup the apollo have you checked the system monitor?  You can see the nvme card there and read/write activity.  If it's not there then it wasn't detected on boot.   Shutdown/turn off and restart.  Does that memory card have LED lights you can see indicating read/write activity on card?   Does the red light turn on on the bottom of the unit where the NVME is connected?  That light tells you the card has been detected and is active.  It turns on during boot and stays on the whole time.  Is there another NVME card you can try, a 1TB or 512GB at least to just try it out to see if it responds the same?  

Yes, the apollo 2 boots and it even starts mining, I've checked it on monitor. Immediately the infamous "Connection refused... Your node is not running" msg appeared and it didn't fix by itself for few hours.
Tried reindex=1 , nothing happened.
Later I figured the problem is that the apollo 2 doesnt recognize the NV3 2TB on boot. This nvme is perfectly operational and well installed into the socket, its tested on multiple computers.
I tried another nvme KC3000 1tb and the system detects it and it is visible in the OS.
There is a constant red light on the board on which the nvme is installed (bottom of the apollo) regardless if the nvme is detected or not.
So the question (for now) is how to make the apollo detect the NV3 2TB nvme....

Here's a screenshot of what's posted during boot
https://ibb.co/fXvHB8m

[eagleye]

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.

[fvineyard]

@jstefanop

Can you please check on the status of RMA # 9514 ? My understanding is the unit has finally been diagnosed and repaired, but they were unable to get it shipped back before the New Years holiday and given an assurance to get it shipped out first thing after the 1st of the year.

It took 19 days to convince your staff that I had received a defective unit and now they have had the defective unit for 43 days. This is far too long.

Thanks for your attention to this matter.

[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

[PennyBit]

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!

[bubbAJoe]

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).