Official FutureBit Apollo LTC Image and Support thread

[whiteogre]

Also I am having (small) problems with SD cards. Too often I need to reflash SD card. Sometimes they run OK for weeks, sometimes only a couple of days.

I use now Kingston 16 GB SD cards. ¿Any other "high quality" SD card brand?. ¿Maybe SanDisk, Samsung...?

Samsung EVO Plus cards at least are supposed to be high quality and I haven't had any issue with those in any devices. However, I haven't seen this frequent need for reflashing the SD card in the Apollo either (114 days uptime currently). At least in Raspberry Pis, the eventual failure mode of a SD card is such that it can no longer be written and also reads result in failures nor is reflashing it anymore possible. That's why I suspect there's something else going on if the usability can be recovered by reflashing the same SD card.

Regarding the current firmware, this is one change that I've done after installing it that may have some improving effect. You'll need ssh access and root to execute the commands:

Code:

systemctl stop "serial-getty@ttyS0.service"
systemctl disable "serial-getty@ttyS0.service"

This only disables a service that is constantly trying to start and will always fail to do so due to such serial port not being available (not that you'd need that terminal anyway). Every start is likely to get written to the systemd bookkeeping which may also result in card write operations.

[1715288743]

1715288743

[1715288743]

1715288743

[1715288743]

1715288743

[psycodad]

Regarding SD card lifespan: I started to use fstrim on the rootfs weekly from cron, but it is too early to judge if that has any beneficial effects on SD card reliability in the Apollo.
Will post again, once I have a record of 2-3 months using it.

[VictorGT]

Also I am having (small) problems with SD cards. Too often I need to reflash SD card. Sometimes they run OK for weeks, sometimes only a couple of days.

I use now Kingston 16 GB SD cards. ¿Any other "high quality" SD card brand?. ¿Maybe SanDisk, Samsung...?

Samsung EVO Plus cards at least are supposed to be high quality and I haven't had any issue with those in any devices. However, I haven't seen this frequent need for reflashing the SD card in the Apollo either (114 days uptime currently). At least in Raspberry Pis, the eventual failure mode of a SD card is such that it can no longer be written and also reads result in failures nor is reflashing it anymore possible. That's why I suspect there's something else going on if the usability can be recovered by reflashing the same SD card.

Regarding the current firmware, this is one change that I've done after installing it that may have some improving effect. You'll need ssh access and root to execute the commands:

Code:

systemctl stop "serial-getty@ttyS0.service"
systemctl disable "serial-getty@ttyS0.service"

This only disables a service that is constantly trying to start and will always fail to do so due to such serial port not being available (not that you'd need that terminal anyway). Every start is likely to get written to the systemd bookkeeping which may also result in card write operations.

Regarding SD card lifespan: I started to use fstrim on the rootfs weekly from cron, but it is too early to judge if that has any beneficial effects on SD card reliability in the Apollo.
Will post again, once I have a record of 2-3 months using it.

Thanks for the info.

Last problems I had did not requiere reflash. Only "Restart" miner was needed. Humm...
Also it happens more often with Apollo batch 2 units (I have two batch 1 and two batch 2).
I will wait for new software in order to do a few more tests.

[estacionsj]

Also I am having (small) problems with SD cards. Too often I need to reflash SD card. Sometimes they run OK for weeks, sometimes only a couple of days.

I use now Kingston 16 GB SD cards. ¿Any other "high quality" SD card brand?. ¿Maybe SanDisk, Samsung...?

Samsung EVO Plus cards at least are supposed to be high quality and I haven't had any issue with those in any devices. However, I haven't seen this frequent need for reflashing the SD card in the Apollo either (114 days uptime currently). At least in Raspberry Pis, the eventual failure mode of a SD card is such that it can no longer be written and also reads result in failures nor is reflashing it anymore possible. That's why I suspect there's something else going on if the usability can be recovered by reflashing the same SD card.

Regarding the current firmware, this is one change that I've done after installing it that may have some improving effect. You'll need ssh access and root to execute the commands:

Code:

systemctl stop "serial-getty@ttyS0.service"
systemctl disable "serial-getty@ttyS0.service"

This only disables a service that is constantly trying to start and will always fail to do so due to such serial port not being available (not that you'd need that terminal anyway). Every start is likely to get written to the systemd bookkeeping which may also result in card write operations.

I think jstefanop said u just need a 32gb card for full node. When is the Full node update gong to come out, jstefanop

OOps sorry its being tested

[estacionsj]

Regarding SD card lifespan: I started to use fstrim on the rootfs weekly from cron, but it is too early to judge if that has any beneficial effects on SD card reliability in the Apollo.
Will post again, once I have a record of 2-3 months using it.

i have been using a 32gb card for 2 1/2 months with no problems

[kaotic818]

I just got my batch 2 today. Is this normal to see so many HW errors?


15.5 percent hardware errors and 1115 in the first hour of turning on the apollo

[jstefanop]

I just got my batch 2 today. Is this normal to see so many HW errors?


15.5 percent hardware errors and 1115 in the first hour of turning on the apollo

Try rebooting it and see if you still see that many errors. Sounds like a pool issue caused a high initial error count, causing the average to shoot higher than normal.

[kaotic818]

I did reboot several times just using litecoinpool.org default and switched to us2.litecoinpool pool. Both are showing errors. Todays numbers are 14.6 percent Hardware errors and 18700 hw errors running for 5 hours today so far.

[jstefanop]

I did reboot several times just using litecoinpool.org default and switched to us2.litecoinpool pool. Both are showing errors. Todays numbers are 14.6 percent Hardware errors and 18700 hw errors running for 5 hours today so far.

Can you post a screenshot of your dashboard?

[kaotic818]

https://imgur.com/gallery/kkhatkI

[intothebreak]

I am having trouble getting the Apollo to connect. I am getting error econnrefused. I read that it has to do with pool credentials. I am putting the user name and password for the litecoinpool.org account correctly but it is a new account. I put my lite coin wallet address in the payment address space on the lite coin pool account. Is there a way to reset the device to go through initial setup again.

[estacionsj]

I am having trouble getting the Apollo to connect. I am getting error econnrefused. I read that it has to do with pool credentials. I am putting the user name and password for the litecoinpool.org account correctly but it is a new account. I put my lite coin wallet address in the payment address space on the lite coin pool account. Is there a way to reset the device to go through initial setup again.

I think u need to reflash The SD CArd. It would bring it all back like new when u bought it.

[intothebreak]

I am having trouble getting the Apollo to connect. I am getting error econnrefused. I read that it has to do with pool credentials. I am putting the user name and password for the litecoinpool.org account correctly but it is a new account. I put my lite coin wallet address in the payment address space on the lite coin pool account. Is there a way to reset the device to go through initial setup again.

I think u need to reflash The SD CArd. It would bring it all back like new when u bought it.

Thank you for some direction

I reflashed and am at the initial setup again. What do I put for the username and password? Is it My login for the litecoinpool.org account or is it my lite coin ledger wallet information key? Or the key at the bottom of my litecoinpool my account page?

[estacionsj]

I am having trouble getting the Apollo to connect. I am getting error econnrefused. I read that it has to do with pool credentials. I am putting the user name and password for the litecoinpool.org account correctly but it is a new account. I put my lite coin wallet address in the payment address space on the lite coin pool account. Is there a way to reset the device to go through initial setup again.

I think u need to reflash The SD CArd. It would bring it all back like new when u bought it.

Thank you for some direction

I reflashed and am at the initial setup again. What do I put for the username and password? Is it My login for the litecoinpool.org account or is it my lite coin ledger wallet information key? Or the key at the bottom of my litecoinpool my account page?

litecoinpool account info, go to first page of this thread also, it has info

[intothebreak]

I put my litecoinpool account username and password that I use to log in to that account with in the initial setup with no proxy in the Apollo web dashboard. I set a password for futurebit. It then let’s me log in with that password. On the home dashboard It shows a dead status that jumps between active and inactive for my main litecoinpool.  the contribution pool is active and alive. I am not sure what’s wrong. The first page doesn’t have this info and I have sifted through the pages and haven’t found it  straightforward. Thanks for the assistance

[intothebreak]

Could it be an error with my main pool  due to payouts being Frozen on my litecoinpool account because I just added a new lite coin wallet address and the account says that anytime payout address is modified all payouts are suspended for 24hr?

[MoparMiningLLC]

Could it be an error with my main pool  due to payouts being Frozen on my litecoinpool account because I just added a new lite coin wallet address and the account says that anytime payout address is modified all payouts are suspended for 24hr?

no - that would affect payouts not your miner working.

the password it wants is for the miner not the password you use to log into the pool with - if you do not have a pool password you will still need to put something like x or 123 as a default one. This miner software does not seem to like it if you leave it blank.

you are using litecoinpool.org, correct?

direct from their page

Getting Started
Understand how mining works. If you are new to mining, read our Beginner's Guide. Make sure you understand that you will never make a profit out of CPU or GPU mining, and that ASIC hardware is required.
Create a pool account. Register here.
Configure your miners. Connect your miners to the server(s) closest to you (most miners allows you to specify more than one URL for failover):
stratum+tcp://litecoinpool.org:3333   (Europe)
stratum+tcp://us.litecoinpool.org:3333   (US East Coast)
stratum+tcp://us2.litecoinpool.org:3333   (US West Coast)
stratum+tcp://ltcpool5brio2gaj.onion:3333   (Tor hidden service)
If connecting from East Asia, the US West Coast address should be preferred.
If you are behind a firewall, you can also access Stratum on port 8080.
Mind that some software (notably some versions of the web interface of Antminers) requires you to omit the protocol prefix (stratum+tcp://) when entering URLs.
The default worker credentials are:
Username:   your_username.1
Password:   1
If you want, you can create additional workers on your account page, with names and passwords of your choice. Both the username and the password are case-sensitive. Never use your account password for any of your workers.

so the default miner password is "1" and that is what you would need to put in the Apollo gui

[intothebreak]

so the default miner password is "1" and that is what you would need to put in the Apollo gui

Thank you so much!!! Needed to put the .1 behind my username And that password. Wow.

[MoparMiningLLC]

so the default miner password is "1" and that is what you would need to put in the Apollo gui

Thank you so much!!! Needed to put the .1 behind my username And that password. Wow.

so you are up and running?

[intothebreak]

so the default miner password is "1" and that is what you would need to put in the Apollo gui

Thank you so much!!! Needed to put the .1 behind my username And that password. Wow.

so you are up and running?

Yes thank you. Active and alive. Hashing. On the home dashboard it does say there is some hardware error percentage tho