Search content
Sort by
Showing 3 of 3 results by bpettyfamily
Re: Official FutureBit Apollo BTC Software/Image and Support thread
~snip~
Regarding the error rate, there have been multiple reports and multiple replies in this thread. I highly recommend ninjastic search, since you can enter the topic ID and a search term. You could even filter by author and only get posts by jstefanop.https://ninjastic.space/search?content=error&topic_id=5340015
In short, as long as your hashrate in the pool's dashboard looks fine, everything's fine. It's overreported, basically - if it says 50% error rate, it doesn't mean the whole machine only has 50% of the expected hashpower, but it's just one of the cores in one of the 44 ASIC chips that has such a high error rate, which is within spec / normal error margins.
Something like that.
does anyone know why one hashboard has a lot more errors than the rest?
This is higher than normal usually its around 23%
https://i.imgur.com/NaqaDGZ.png
This is higher than normal usually its around 23%
https://i.imgur.com/NaqaDGZ.png
A few units display abnormally high error but this is mostly a display issue. If you hashrate is where it should be (which it is for your unit) you're fine.
Thank you for this information on the error rate! This is what I was hoping to hear!
Re: Official FutureBit Apollo BTC Software/Image and Support thread
Hello All (@jstefanop)
New to bitcoin mining as of last Friday when my new FutureBit Apollo BTC (from batch 4) was delivered. I managed to follow the instructions well enough and I now have the full node up and running (with the outbound 8888 port enabled on my router). The concern I have after watching this thing run for a week has to do with the occasional high hardware error % readings (I'm talking upwards of 50% at times). I haven't found where others have reported this issue in these threads. I assumed these high hardware error % readings would go away once the full node finished downloading (even though I did leave the Apollo BTC in ECO mode that whole time for the first few days). I was wrong about that. I then determined that there must be too much heat because the fan never seems to kick into high gear unless I completely shutdown the miner. I've tried elevating the miner up off of the table a little to allow for better ventilation under the device. That did help to keep the temps down.
The errors seem to go away (for a while) if I shutdown the device and let the fan cool everything back down, but my temps are in acceptable range really (no higher than ~62 degrees C). Nothing I've tried seems to keep the hardware error % in an acceptable range for very long.
What are some other troubleshooting ideas I should consider trying? I should add that these hardware errors do seem to resolve themselves eventually and it will go back to <1% hardware errors if I let it keep running long enough. Is this normal? Should I be concerned? I'd hate to allow a problem to persist for too long if it shortens the lifespan of this device in any way.
Any help would be appreciated,
Bob
New to bitcoin mining as of last Friday when my new FutureBit Apollo BTC (from batch 4) was delivered. I managed to follow the instructions well enough and I now have the full node up and running (with the outbound 8888 port enabled on my router). The concern I have after watching this thing run for a week has to do with the occasional high hardware error % readings (I'm talking upwards of 50% at times). I haven't found where others have reported this issue in these threads. I assumed these high hardware error % readings would go away once the full node finished downloading (even though I did leave the Apollo BTC in ECO mode that whole time for the first few days). I was wrong about that. I then determined that there must be too much heat because the fan never seems to kick into high gear unless I completely shutdown the miner. I've tried elevating the miner up off of the table a little to allow for better ventilation under the device. That did help to keep the temps down.
The errors seem to go away (for a while) if I shutdown the device and let the fan cool everything back down, but my temps are in acceptable range really (no higher than ~62 degrees C). Nothing I've tried seems to keep the hardware error % in an acceptable range for very long.
What are some other troubleshooting ideas I should consider trying? I should add that these hardware errors do seem to resolve themselves eventually and it will go back to <1% hardware errors if I let it keep running long enough. Is this normal? Should I be concerned? I'd hate to allow a problem to persist for too long if it shortens the lifespan of this device in any way.
Any help would be appreciated,
Bob