Bitcoin Forum
May 25, 2024, 04:20:32 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Are my antminer s9s fooling me?  (Read 811 times)
DragonDog (OP)
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
January 27, 2017, 09:50:42 AM
Last edit: January 27, 2017, 12:34:03 PM by DragonDog
 #1

So I am solo mining with my two S9's.  I am hoping to find a block in two years.....lol...don't judge this...instead,please help me know whether my machines are fooling me into thinking they are operating properly.

Everything seems normal when you look at the status page of each machine (please see the images I have attached).

However, when I look in the kernel log of one of the machines I see the following:  
----------------------------------------------------------------------------------
"total valid nonce number:57450
total send work number:57456
require valid nonce number:57456
repeated_nonce_num:0
err_nonce_num:45533
last_nonce_num:21952
chain[5]: All chip cores are opened OK!
Test Patten on chain[5]: FAILED!
Try to add voltage on chain[5]...
chain[6]: All chip cores are opened OK!
Test Patten on chain[6]: FAILED!
Try to add voltage on chain[6]...
chain[7]: All chip cores are opened OK!
Test Patten on chain[7]: FAILED!
Try to add voltage on chain[7]...
restartNum = 2 , auto-reinit enabled..."
----------------------------------------------------------------------------------
Also, the machine showing the test pattern problem has the standard blinking green light as the other machine does but in addition has steady (i.e. always on) red lights coming from where the power supply cables plug into the antminer.

So, from the status page it would appear that both machines are hashing correctly....but the kernel log of the one machine with the steady red lights shows errors.

Are they both actually hashing correctly? Is this something to worry about? I have the latest auto frequency firmware installed  (dated 11-29-2016) on both machines.

ALSO, the stats from my solo mining pool show that both machines are hashing at the proper 13.5ths average hash rate.  

I am worried that the 13.5ths on the steady red light machine may not be accurate (perhaps the machine is processing data at that rate but could be performing flawed operations which could result is a block never actually being found).

Also, can someone give me tips on interpreting the data in the status page?  For example,a way to know how close I've come to solving a block?

https://postimg.org/image/mvju0iuo7/
https://postimg.org/image/hy69fesp3/
VRobb
Hero Member
*****
Offline Offline

Activity: 1610
Merit: 538

I'm in BTC XTC


View Profile
January 27, 2017, 01:26:02 PM
 #2

If the pool is saying your hashrate is correct then it is correct, don't worry about it!  As to 'how close' you've come to solving a block, in bitcoin mining the saying 'a miss is as good as a mile' is appropriate since each share when calculated is random, and either you solve it or not.  Close only counts in horseshoes, hand genades, and atom bombs!!

I don't believe in superstition because it's bad luck: 13thF1oor6CAwyzyxXPNnRvu3nhhYeqZdc
These aren't the Droids you're looking for: S5 & S7 (Sold), R4B2, R4B4 (RIP), 2x S9 obsolete, 2xS15-28, S17-56, S17-70
Pushing a whopping 1/5 PH!  Oh The SPEED!!!
unholycactus
Legendary
*
Offline Offline

Activity: 1078
Merit: 1024



View Profile WWW
January 27, 2017, 09:45:00 PM
 #3

Solo mining has the same expected value in terms of return when compared to pool mining. Nobody can really judge you for that unless you're mining a very short period of time.

Make sure everything is setup correctly for the payout.
If the solo pool is showing around 14TH/s for each of your miners, which seems to be the case, you're good to go.

Solving a block isn't cumulative work. It's just luck and the "work" resets every time a block is solved.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!