ANTMINER S3+ Discussion and Support Thread

[heldertb]

So I have my S3+'s up and running, but I'm trying to overclock them to 237.5MHz. But they get a lot of hardware errors (sometimes up to 5%), and sometimes the chips starts showing x's.
Is there anything to solve this? I guess the S3+ from B8 are installed with latest firmware?

Also, I don't really know what pool to choose, currently mining on Eligius/Discus Fish. any suggestions?

As the product info on Bitmain's own page says, not all S3s will got to 500, so no, not really any way to solve it.
As Blizzard would say, "Working as intended".


Source:

Bitmain now announce the S3+, which is a revised version of S3 running stably at 453GH/s (frequency=225 MHz), while consumes 355 Watt power at the wall. Most of miners will be able to run up to 500GH/s but not guaranteed.

(Emphasis mine)

Okay, but what about the chips that fail? I can't restart the miner like every hour or so?...

Getting an x on chips only when you clock it up is symptomatic with the issues that caused them to clock them down to 225 MHz.  If you have issues at 225 MHz, RMA with Bitmain.  If you have no issues at 225 MHz, there's nothing wrong.

too bad, I think my miners won't hit 453GH/s at 225MHz...

[1714668704]

1714668704

[1714668704]

1714668704

[1714668704]

1714668704

[1714668704]

1714668704

[Count_Frackula]

So I have my S3+'s up and running, but I'm trying to overclock them to 237.5MHz. But they get a lot of hardware errors (sometimes up to 5%), and sometimes the chips starts showing x's.
Is there anything to solve this? I guess the S3+ from B8 are installed with latest firmware?

Also, I don't really know what pool to choose, currently mining on Eligius/Discus Fish. any suggestions?

As the product info on Bitmain's own page says, not all S3s will got to 500, so no, not really any way to solve it.
As Blizzard would say, "Working as intended".


Source:

Bitmain now announce the S3+, which is a revised version of S3 running stably at 453GH/s (frequency=225 MHz), while consumes 355 Watt power at the wall. Most of miners will be able to run up to 500GH/s but not guaranteed.

(Emphasis mine)

Okay, but what about the chips that fail? I can't restart the miner like every hour or so?...

Getting an x on chips only when you clock it up is symptomatic with the issues that caused them to clock them down to 225 MHz.  If you have issues at 225 MHz, RMA with Bitmain.  If you have no issues at 225 MHz, there's nothing wrong.

too bad, I think my miners won't hit 453GH/s at 225MHz...

They should, but if they can't, take it up with Bitmain.

[twib2]

too bad, I think my miners won't hit 453GH/s at 225MHz...

They should, but if they can't, take it up with Bitmain.

Only worthwhile if you're lacking by 5%, it would seem...

I have not had good experience with their support/RMA folks.  It took me a month to get a single S3 hashing board replaced, and that's when I had it fail, put a deposit so they could ship it before they received my return, AND they didn't send me the blade with heatsinks.

[CHAOSiTEC]

So I have my S3+'s up and running, but I'm trying to overclock them to 237.5MHz. But they get a lot of hardware errors (sometimes up to 5%), and sometimes the chips starts showing x's.
Is there anything to solve this? I guess the S3+ from B8 are installed with latest firmware?

Also, I don't really know what pool to choose, currently mining on Eligius/Discus Fish. any suggestions?

As the product info on Bitmain's own page says, not all S3s will got to 500, so no, not really any way to solve it.
As Blizzard would say, "Working as intended".


Source:

Bitmain now announce the S3+, which is a revised version of S3 running stably at 453GH/s (frequency=225 MHz), while consumes 355 Watt power at the wall. Most of miners will be able to run up to 500GH/s but not guaranteed.

(Emphasis mine)

Okay, but what about the chips that fail? I can't restart the miner like every hour or so?...

Getting an x on chips only when you clock it up is symptomatic with the issues that caused them to clock them down to 225 MHz.  If you have issues at 225 MHz, RMA with Bitmain.  If you have no issues at 225 MHz, there's nothing wrong.

too bad, I think my miners won't hit 453GH/s at 225MHz...

S3+ Specifications:


Hash Rate: 453 GH/s±5% with great OC potential
Power Consumption: 355 Watt at the wall
Power Efficiency: 0.78J/GH on wall
Power Supply: 12V DC
Size:  331 mm x 137 mm x 160 mm
Fans: Two 14038 fans mounted on both front and back ends
Operating Temperature: 0 °C to 35 °C
Complied with: FCC / CE
Network Connection: Ethernet

please note the +/- 5%

[lordmykl]

Batch 10 just showed up on Bitmain's site...at least the price is right for ROI.

https://i.imgur.com/SPOSNBA.png

[soy]

Sorry about the off topic but:  Perplexed rather than paranoid, something odd has occurred since checking the UPS shipping status of my S3+'s from China.  I have two drives in this system both new this year, a 2TB main drive and a 3TB backup.  Upon getting notification that the units were shipped I checked the UPS tracking and saw the status but about that time one of my hard drives started making sounds as if moving data to the inner area of the drive and that read arm was loud in its snapping movement.  It's been happening every once in a while since.  Meanwhile I've downloaded SeaTools and fast check the drives and both are okay and now doing a long drive test.  So, NSA or China screwing with my system?

[Count_Frackula]

Sorry about the off topic but:  Perplexed rather than paranoid, something odd has occurred since checking the UPS shipping status of my S3+'s from China.  I have two drives in this system both new this year, a 2TB main drive and a 3TB backup.  Upon getting notification that the units were shipped I checked the UPS tracking and saw the status but about that time one of my hard drives started making sounds as if moving data to the inner area of the drive and that read arm was loud in its snapping movement.  It's been happening every once in a while since.  Meanwhile I've downloaded SeaTools and fast check the drives and both are okay and now doing a long drive test.  So, NSA or China screwing with my system?

I'd have to hear the noise to be sure, but usually when a drive makes any loud snapping noises, it's having trouble reading and is failing.  You can monitor it real-time though using Task Manager > Performance > Resource Monitor.

[jelin1984]

I mean how I can put in and which menu of bitmain
I must use for
Updated the cgminer to 4.6

[Biodom]

I mean how I can put in and which menu of bitmain
I must use for
Updated the cgminer to 4.6

you do not use the bitmain menu
you ssh into miner, then use commands on page 317 of this board.
...if i correctly understood what you asked

[davecoin]

Hey all, I was updating my batch 1 S3 units to the latest firmware and one of them is having troubles booting now.  I cannot access it via the webui or via ssh.  I attempted a hard reset using the button on the front so I know the address of the miner should be 192.168.1.99.  Red light is blinking. I'm familiar with how to talk to the miners as I've had around 10 S1, a couple S2, and 10 S3.  This is the only one giving me issues.  

I swapped control boards with another S3 and it's working fine, so the hashing boards are okay.  I sent an email requesting an RMA for the control board.  

Does anybody have anything else I can try?

Thanks,
Dave

[MoreBloodWine]

Ok, so since I formatted my hdd in my laptop like two weeks ago. I lost some of my favorite links.

Can someone post me a ink on the new firmware I have with the stuff to edit so I can get 243.75 added back in. I think it was removed when this (the S3) got reset.

Ty.

[lordmykl]

So....long story short, I have a total of Eighteen S3+ Antminers that are in a building that for most of the time is not used.  Every once in a while, however, it is used, so I want to be able to easily drop the fan noise down via a scripted approach. I have Teamviewer access to a live system there and I've used Putty to SSH into individual miners to change frequency on individual units. What would be a good scripted approach to change them en masses from say 250M to 212.5M and back?  Sequential IPs and all same username/PW...

Thanks in advance!

[jimmyoh]

Hey all, I was updating my batch 1 S3 units to the latest firmware and one of them is having troubles booting now.  I cannot access it via the webui or via ssh.  I attempted a hard reset using the button on the front so I know the address of the miner should be 192.168.1.99.  Red light is blinking. I'm familiar with how to talk to the miners as I've had around 10 S1, a couple S2, and 10 S3.  This is the only one giving me issues. 

I swapped control boards with another S3 and it's working fine, so the hashing boards are okay.  I sent an email requesting an RMA for the control board. 

Does anybody have anything else I can try?

Thanks,
Dave

If I remember correctly when updating the FW you're not able to retain your old settings so you'll need to start from scratch and match your computer to the original S3 IP address and input all of your settings again.

[soy]

Hey all, I was updating my batch 1 S3 units to the latest firmware and one of them is having troubles booting now.  I cannot access it via the webui or via ssh.  I attempted a hard reset using the button on the front so I know the address of the miner should be 192.168.1.99.  Red light is blinking. I'm familiar with how to talk to the miners as I've had around 10 S1, a couple S2, and 10 S3.  This is the only one giving me issues.  

I swapped control boards with another S3 and it's working fine, so the hashing boards are okay.  I sent an email requesting an RMA for the control board.  

Does anybody have anything else I can try?

Thanks,
Dave

Use tcpdump to monitor the traffic on the subnet.  Once I thought I had changed to DHCP and moved the device to another subnet but couldn't find it with nmap.  I ran tcpdump on another machine on that subnet and most of the traffic had the correct subnet but some packets had the .1.99 address so I knew the problem was that it didn't take the protocol change to DHCP.

[davecoin]

Hey all, I was updating my batch 1 S3 units to the latest firmware and one of them is having troubles booting now.  I cannot access it via the webui or via ssh.  I attempted a hard reset using the button on the front so I know the address of the miner should be 192.168.1.99.  Red light is blinking. I'm familiar with how to talk to the miners as I've had around 10 S1, a couple S2, and 10 S3.  This is the only one giving me issues.  

I swapped control boards with another S3 and it's working fine, so the hashing boards are okay.  I sent an email requesting an RMA for the control board.  

Does anybody have anything else I can try?

Thanks,
Dave

Use tcpdump to monitor the traffic on the subnet.  Once I thought I had changed to DHCP and moved the device to another subnet but couldn't find it with nmap.  I ran tcpdump on another machine on that subnet and most of the traffic had the correct subnet but some packets had the .1.99 address so I knew the problem was that it didn't take the protocol change to DHCP.

Why would the address be anything other than 192.168.1.99 though? I did a hard reset.

[bspurloc]

Sorry about the off topic but:  Perplexed rather than paranoid, something odd has occurred since checking the UPS shipping status of my S3+'s from China.  I have two drives in this system both new this year, a 2TB main drive and a 3TB backup.  Upon getting notification that the units were shipped I checked the UPS tracking and saw the status but about that time one of my hard drives started making sounds as if moving data to the inner area of the drive and that read arm was loud in its snapping movement.  It's been happening every once in a while since.  Meanwhile I've downloaded SeaTools and fast check the drives and both are okay and now doing a long drive test.  So, NSA or China screwing with my system?

heads slamming in and out is a READ FAILURE. the heads try to realign then back to the platter area its trying to read. FAILS again and then try to align again, repeat repeat repeat. the drive a DOA. 
 The nsa accusation is a tad crazy bra.

[bspurloc]

So....long story short, I have a total of Eighteen S3+ Antminers that are in a building that for most of the time is not used.  Every once in a while, however, it is used, so I want to be able to easily drop the fan noise down via a scripted approach. I have Teamviewer access to a live system there and I've used Putty to SSH into individual miners to change frequency on individual units. What would be a good scripted approach to change them en masses from say 250M to 212.5M and back?  Sequential IPs and all same username/PW...

Thanks in advance!

I would setup a script on each one and then modify the web interfaces adding another page like 192.168.1.99/slowdown and 192.168.99/speedup that runt he scripts
then you could just do it all over port 80 via lynx.

assuming you know how to code etc...
web interfaces root is /www  by the way...

[bspurloc]

on the Antminers is /rom the actual hardcoded rom?
yeah prob since its RO

[grn]

B9 shipping already

[tripppn]

B9 shipping already

You get a tracking number?