Topic: ANTMINER S2 Discussion and Support Thread (Read 355820 times)

Also if you have some other Antminers, you could save the BeagleBone Black board for a spare part.

The PSU was the only part of value. There are also the 4 fans which are good for a computer.

The rest is scrap metal.

S2 PSU finally died.  What should I do?  Sell the parts or replace the psu....

Thinking about selling it for parts....

I understand this is late, but I've been really busy with the farm lately and not keeping up. I bought a used S2, and it has been running on my wire shelving rack for about three months. HOWEVER, I also have several S3s. If I had a choice, I would buy two S3s rather than an S2. Here's why:
     1. The S2 puts out about 1.1Th/s consistently. Not bad. However, two S3s will put out 0.9Th/s on less power, and they don't overheat if not overclocked. Two S3s are run off the same capacity power supply as one S2.
     2. If you're concerned about reliability (every minute you're down you're losing money), then more smaller units (to a certain degree) producing nearly the same volume is better.
     3. I live on Kaua'i Island in Hawai'i. My average indoor temp in winter is 80F. The S2 began to overheat immediately upon firing it up on its arrival. See following for how we had to handle it. Bottom line...S2s are notorious for overheating.

We had to (1) remove the cover, (2) add two case fans blowing into the case from the psu side; we removed the virtually useless magnetic drive fan on the internal psu, placing the case fan over the opening where it used to be; the other is at the front side of the frame, blowing into the blade cavity (Blade 10 side), and (3) add a floor fan blowing into the case from the other (Board 1) side. The case fans run off the psu. It is now stable...although fairly noisy (also more so than two S3s).

My feeling is that the psu should never be in the same case as the blades. It's just too much heat energy radiating back and forth between the psu cavity and the blade cavity at #10, and the thin sheet metal barrier isn't sufficient to shield one from the other. Once we fixed the blades overheating (by removing the case and adding the floor fan), the psu would then fail after a few minutes, but this was fixed by the case fan mods.

Dunno if that's any help.

I need a little help. I have two Antminer S2's and they both have a 0 acceptance rate and very high stale rate over 10,000 and counting for one day. I had this problem with my S3's as well but they started working correctly.
Any ideas or solutions would be greatly appreciated.

I'm looking for information on how to tell what batch number S2 are. Wether it be design features or board numbers....

Design features - It seems that batch 1 had a plain cover and the hash boards had 2 piece heatsinks per the pictures I'm finding...

I have an S2 that has a plain cover, foam strips to hold the hash boards in place and the hashboards have a 1 piece heatsink that covers the whole board. No hole in the chassis for a PSU fan.

I also have several S2's that have ANTMINER pressed into the cover, a metal plate that holds the hashboards in place, and a hole in the chassis for a PSU fan.

Again, I'm looking for how to identify the batch numbers....

thanks

It works now with latest beta of MMinerMonitor53b1:

Then you need to get him to update his monitoring code.
He probably looks for the non-standard API.

He had to change his code for S3.
No idea why that doesn't mean it's fixed for S2/everything else also.

cgminer has the same API format for all devices everywhere for summary,pools,devs,etc,etc
The main part that varies per device (has different fields) is 'stats' and I also state that in the API-README back when I wrote it:
https://github.com/ckolivas/cgminer/blob/master/API-README#L295

Bitmain's forked cgminer screwed with summary, devs and pools, and I guess the people who wrote monitors ignored allowing the standard API
Why? No idea. Foresight - I see little of it in the bitcoin world.

Still ZERO.



I tried to write there "W:127.0.0.1,192.168.1.0/24", "W:127.0.0.1,W:192.168.1/24" - still ZERO. Even with R:0/0. 

Well if your home network is 192.168.X.Y
W:127.0.0.1,W:192.168.X/24
https://github.com/ckolivas/cgminer/blob/master/API-README#L18

If you want to give the world read access also
W:127.0.0.1,W:192.168.X/24,R:0/0

There are (as can be seen) no spaces in any of that.

DON'T use W:0/0
That's what Bitmain puts in there for everyone ... and means ANYONE who has network access can change anything including the pools and usernames and setting and ... and ...

I have just flashed my S2 with this FW. Thanx kano!  

But what should I input in "API Allow" field for M's Miner Monitor to display the hashing speed of this S2?  

Now it says that Speed(5s) and Speed(avg) are ZERO.

I'm trying to understand it reading API-README, but I doubt I'll find it by myself...

Looks like you'll need to take the SD out and fsck or reformat /dev/mmcblk0p3 on a computer.

If you don't have linux on a PC, you get get a linux live distribution and boot that on any PC (choose the try/trial option, not the install option) and use fsck or mke2fs from that live distro e.g. ubuntu

I'll look into adding what's needed into my firmware so it can be fixed in the S2 directly.

Is the same. How would I fix it?

Thanks for your help btw.

[/code]

That's the writeable /config partition
So yeah without that mounted, it can't save any settings that survive a power off.

The command to see the SD card setup is:
fdisk -l

This will explain what's wrong.
In should be:

If it's not the same, then it will needs correcting.

If it is the same then that means the /config (/dev/mmcblk0p3) partition is corrupt and needs fixing with fsck or reformatting.

I'm missing this but everything else matches yours.

Check the /config/cgminer.conf
That is where the settings are saved and that directory /config/ and everything below it is a write enabled partition on the SD card.
If it has the wrong file privs not allowing the web interface to write to it that may stop it saving them.
I added changes in some places to override the file privs to attempt to fix that.

To see the SD setup when you login with putty or ssh:
df -h
On my SD it looks like this:

My settings won't save if I reboot or turn off since I updated the firmware with Kano's.. Any suggestions?

One of my antminers s2 has a steady hashrate of about 1015 Gh/s for a couple of days and then the hashrate falls to 900 GH/s. When I check the temperature it is always around 40-43 Celsuis. If I power it off and on it goes back to 1015GH/s. A remote restart doesn't do it, I have to physicaly disconnect it from the power outlet. Do you think I need to change the thermal paste on the blades?  

Thank you for your work on S2s! 

Many times we have discussed here on the forum the results of S2s overcklocking. Personally I would like you to add my maximum stable result of OCing. It was:

    option 'freq_value'     '5102'  #219M
    option 'chip_freq'      '218.75'
    option 'timeout'        '38'

Probably values for 225 MHz could be OK too since I have 1200 Wt Corsair PSU inside my S2. But I'm not sure about exact values for this frequency.

Probably all mindtrip's values can be included too: https://bitcointalksearch.org/topic/m.7012357

Pre-flashing is good. More details will say after a long work nicehash.