Author

Topic: Hashrates keep dropping (Read 746 times)

full member
Activity: 130
Merit: 100
May 11, 2014, 12:00:44 AM
#4
If you have are using a Raspberry Pi proxy server for your S1s, try rebooting it.

Also swap out the router or switch.  A dying piece of network equipment can be the cause.

newbie
Activity: 4
Merit: 0
May 10, 2014, 12:00:37 PM
#3
Quote
The 5 units ran consistently between 930-950GH for weeks and now in the last few days it's been sliding. The units show that they are hashing between 170-215GH/s depending on each unit at any given point in time within the Antminer WRT software. In the BTC Guild dashboard the units are hashing a pathetic 135-195GH/s.

1) So they were at 930-950gh.  How much did they decline?  What is the total hashing at this moment?

2) Focus on the GH/S (avg) numbers from the Antminer WRT 'miner status' tab.  The website info isn't as accurate and constantly changes.  The 5 sec hashrate reading also constantly jumps around.

3) Look at and check the ASIC chip status under the 'miner status' tab.  They should read 00000000 00000000 00000000 00000000 .  If there are any x's, x0000000 00x00x00 00x0xx00 00000000, try rebooting the unit.  If there are still any x's after the reboot, or if multiple x's keep appearing after a short amount of time (hrs to overnight), try reflashing the unit with the latest .bin file from bitmain.  That solved my asic problems.  Here is my post on how to do this:

          https://bitcointalksearch.org/topic/m.6654028

4) I've only been running my four units for about a month.  In the past few days the outside temp in central PA has been in the 80's.  It has been humid and significantly hotter in the room with my S1's.  Their avg hashrate has decreased a little.  The one unit went from 200 gh/s avg to 197gh/s avg.  From my brief 1 month of experience, I conclude that heat causes them to run slower and can cause asic chip errors.  Did you try to set up extra cooling? Even a cheap box fan for some extra air flow should help cool them down.  Mine are all overclocked and usually run at a temp of 43-47, but on the hot days I've seen 49-51.  You can also try cleaning out the heat sinks with some compressed air to get the accumulated dust out of there.

Let us know if any of this helped!


newbie
Activity: 10
Merit: 0
May 09, 2014, 08:49:07 AM
#2
There could be some reasons to it:

1) The stratum difficulty set was too high. Lower the difficulty and see what happens.
2) Hash rate changes after a few minutes. Wait for like 5 minutes, then check again.
3) Your mining equipment produces / generates a lot of heat. Large cooling is needed so that it does not overheat.
4) If you bought second-hand equipment , your product might not be as efficient as the original one bought from the manufacturer and the performance can suffer from prolonged usage.

newbie
Activity: 18
Merit: 0
May 09, 2014, 04:25:57 AM
#1
Hi,

I'm running 5x Antminer S1 and the hash rates keep slipping lower and lower. I'm mining through BTC Guild with the worker difficulty set to 256 for each unit. All units were originally overclocked.

One unit began to shut off intermittently as temperatures began to increase from the winter. When I removed the overclock, that unit functioned without shutting off anymore. I determined the power supply on that particular unit was the issue as it had only 1 PCI-E power cables which I extended with an adapter to reach both plugs. Another unit also experienced intermittent shutoffs at the highest temps and subsequently had the overclock removed. The other power supplies have 2 PCI-E power cables and those units haven't experienced that problem.

The 5 units ran consistently between 930-950GH for weeks and now in the last few days it's been sliding. The units show that they are hashing between 170-215GH/s depending on each unit at any given point in time within the Antminer WRT software. In the BTC Guild dashboard the units are hashing a pathetic 135-195GH/s.

I tried redirecting all 5 units to MultiPool and didn't see any increase in hashrate.

After that I suspected I might be overloading a circuit and causing a brownout, but after turning off a computer on the same circuit, and moving 1 unit to another circuit, the hash rate is still abysmal.

Any ideas as to what I might be missing here?
Jump to: