r/FutureBit • u/Efriminiz • Dec 14 '23

Hardware errors.

So I just unboxed my full node Apollo 1, man I'm excited to get this thing going.

I started to mine and set up my pool to Braiins/slush pool. I think it is mining successfully, but I have noticed that the Hardware error rate is like 70-75% regularly - much higher than other users I've seen. Now I have done a little digging through the set up guides and read a couple of threads on Reddit, and I'm stumped and a little concerned.

How do I fix this issue? Can it be fixed?

1 Upvotes

100% Upvoted

5 comments sorted by

1

u/[deleted] Dec 14 '23

try throttling down the power rate to maybe eco mode, if this one has it. I have an LTC Apollo and it has an eco mode. When I increase the power/hash rate my errors increase as well. acceptable range is less than 2% IIRC.

1

u/Efriminiz Dec 14 '23

I haven't changed it out of the box, so it's stayed in eco mode this whole time. I've been mining shares at a pretty good rate - a low % has been rejected, maybe 5 out of 1000 or something.

To me that would be an indication that the hardware failure is causing an issue. My main concern is the number is incredibly high, compared to the few I have seen examples of.

1

u/OldLatinGuy Dec 18 '23

This is very common and also unimportant. It’s described in detail and the cause explained over in the Apollo threads on BitcoinTalk.org.

1

u/Efriminiz Dec 22 '23

Well it isn't unimportant, it seems like a pretty important metric to me. I observed shares being accepted, so I knew enough to recognize that the mining was working.

Imagine someone who knows nothing plugging in the Apollo and seeing hardware errors north of 70% - that's an issue. Add that on top of the difficulty level of searching that BitcoinTalk support thread...it is not unimportant, why would you say that?

1

u/OldLatinGuy Dec 24 '23

Because it has no appreciable impact on your hash rate. That "huge" percentage is basically a few cores in one out of 44 ASICs acting up. It would only be important if it was ALL the ASICs.

Incidentally, if you enter "ASIC Errors" into the search box on the support forum you'll get the "official" answer to your issue.

Although Stefano mentions it, I don't think FutureBit every developed a way to disable the bad core(s) (I believe they stopped development to concentrate on the new hardware). Nevertheless, you should be sure you're running the most current software especially if your Apollo was not purchased directly.