I am running 3 s4's since 3 weeks and have few doubts to be clarified by any experienced users. Our machines are hosted somewhere else.
In the beginning hashrate was very unstable and after upgrading to latest firmware, they became lil stable. I use p2pool.
-what does hard reset mean? In-detail please?
-1 of our miner has lower hash rates with 1 or 2 'x' asics failing always.After running it for sometime x starts appearing. Contacted bitmain and they said to test each blade and we did all troubleshooting stuff and they worked fine when connected to separate blades. Again after connecting all, 1 'x' appeared and hashrate is slow after 10hours compared to others.
For example on p2pool with default 200mhz,725v on p2pool with pseudo,actual difficulty set to /8192+8192, hash rates are as folllows after running them for 6days :
miner 1 : 1970gh
miner 2 : 1965gh
miner 3 : 1850gh ( which has asics failing issue)
All above stats are from antminer panel and p2pool graphs shows a different story. All 3miners work with same worker.
deadhashrate overall for 3 miners on pool is 270gh. shall i set difficulty to 4096 for a lower dead hash rate or is it something to do with pool?
- I am planning to overclock the frequency to 212.5mhz on 725voltage. Will that work or any consequences? I have seen people doing 225mhz with 725volt.
comments are appreciated. Thanks
In the beginning hashrate was very unstable and after upgrading to latest firmware, they became lil stable. I use p2pool.
-what does hard reset mean? In-detail please?
-1 of our miner has lower hash rates with 1 or 2 'x' asics failing always.After running it for sometime x starts appearing. Contacted bitmain and they said to test each blade and we did all troubleshooting stuff and they worked fine when connected to separate blades. Again after connecting all, 1 'x' appeared and hashrate is slow after 10hours compared to others.
For example on p2pool with default 200mhz,725v on p2pool with pseudo,actual difficulty set to /8192+8192, hash rates are as folllows after running them for 6days :
miner 1 : 1970gh
miner 2 : 1965gh
miner 3 : 1850gh ( which has asics failing issue)
All above stats are from antminer panel and p2pool graphs shows a different story. All 3miners work with same worker.
deadhashrate overall for 3 miners on pool is 270gh. shall i set difficulty to 4096 for a lower dead hash rate or is it something to do with pool?
- I am planning to overclock the frequency to 212.5mhz on 725voltage. Will that work or any consequences? I have seen people doing 225mhz with 725volt.
comments are appreciated. Thanks
Most Bitmain hardware since S1s do not function well "out of box" with p2pool.
You should be able just add "+2050" to your user names to take care of the low work size problem.
The other thing you can do to help is lower your queue size. As far as I know the only way to do that is via SSH. One way is:
/usr/bin/cgminer-api "setconfig|queue,0"
I think you may be able to change it in a config file as well... but I'm pretty sure, regardless how you do it, it'll get lost on the next power cycle or UI change.
I'm currently using my S4 on p2pool locally, which makes it easier for me to set the queue size. Once I move it to hosted I'm not sure what I'm going to do as I won't have SSH access. I've discussed it with my host and they can set the queue size once a day. I may end up just using something else besides p2pool.
M