Bitcoin Forum
May 10, 2024, 04:04:39 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Block Erupter Cube hashrate  (Read 1535 times)
cclemmons (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
February 05, 2014, 04:57:01 PM
 #1

I'm having some trouble getting what I consider to be the proper hashrate out of my Cube.  I've had it up and running for a couple of weeks now, mostly on Slush's pool.  However, I've noticed that I am only getting around 24 GH/s as reported by the pool.  When I look at the configuration page on the Cube and the stats on bfgminer, I am seeing around 30-38 GH/s, which is exactly what I would expect.  I understand that the reported rate on the pool is an average of your work over the last 10 rounds and might be a little different than what I see locally, but a 10 GH/s difference?  That seems a little too wide a gap.  Also, I have a friend with the exact same setup as I have and his reports around 34 GH/s.  He is also getting a better return (obviously), and it's starting to irritate me Grin

I have noticed when I watch the stats on the Cube's config page that the 'Started Before' timer goes about 8-10 minutes and restarts then the proxy in bfgminer reports sick.  After a few seconds, it will fire back up and get going.  It almost seems like the cube is rebooting after overheating, but the thing feels completely cool to the touch and the fan is purring along just fine.  Any thoughts on what I should look at?
1715357079
Hero Member
*
Offline Offline

Posts: 1715357079

View Profile Personal Message (Offline)

Ignore
1715357079
Reply with quote  #2

1715357079
Report to moderator
In order to achieve higher forum ranks, you need both activity points and merit points.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715357079
Hero Member
*
Offline Offline

Posts: 1715357079

View Profile Personal Message (Offline)

Ignore
1715357079
Reply with quote  #2

1715357079
Report to moderator
1715357079
Hero Member
*
Offline Offline

Posts: 1715357079

View Profile Personal Message (Offline)

Ignore
1715357079
Reply with quote  #2

1715357079
Report to moderator
cclemmons (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
February 07, 2014, 08:22:49 PM
 #2

Nevermind...problem solved.  If anyone is curious, the solution (at least in my case) was to add a secondary IP address to the proxy server, then use that secondary address as the failover pool address for the Cube.  My original setup was using the proxy address as both the main and failover pool address like it said to do in all the guides I found.  Anyway, I don't know why it works, but it does, so I'm happy again.
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!