ANTMINER S3+ Discussion and Support Thread

[Mikestang]

I have taken it apart to inspect it and clean it. I did not notice anything out of the ordinary or any damage. The controller is a V1.05 if that helps at all. I do have two S3 units and I can go ahead and swap the boards to see if the problem transfers to the other S3 or if it stays with the first.

Also try a factory reset and reinstall latest firmware, just in case.  Sometimes going back to square 0 helps flush some gremlin out of the machine.

[1714909829]

1714909829

[in2tactics]

I have taken it apart to inspect it and clean it. I did not notice anything out of the ordinary or any damage. The controller is a V1.05 if that helps at all. I do have two S3 units and I can go ahead and swap the boards to see if the problem transfers to the other S3 or if it stays with the first.

Also try a factory reset and reinstall latest firmware, just in case.  Sometimes going back to square 0 helps flush some gremlin out of the machine.

I did select the option to NOT keep the settings when I flashed the FW last week. Is there a difference between that and actually using the hardware reset button after flashing the FW?

[Mikestang]

I don't know, I have always just followed the factory reset instructions in the manual, then installed the latest fw.

[in2tactics]

I don't know, I have always just followed the factory reset instructions in the manual, then installed the latest fw.

Unfortunately, the 7/18/2014 version of the manual no longer includes that information. UGH Anyway, I will definitely give your suggestion a try before anything else.

[notlist3d]

I don't know, I have always just followed the factory reset instructions in the manual, then installed the latest fw.

Unfortunately, the 7/18/2014 version of the manual no longer includes that information. UGH Anyway, I will definitely give your suggestion a try before anything else.

Are you just looking for info on reset? It's dated but still accurate - https://bitcointalk.org/index.php?topic=697474.0 .  It's a good troubleshooting thread but it shows how to reset.

[Real-Duke]

The S3 or S3+ with latest Bitmain Firmware and the actual cgminer 4.9.2 update by Kano https://github.com/kanoi/cgminer-binaries is still a good miner!
Not the fastes anymore but stable like a tank 

[notlist3d]

I don't know, I have always just followed the factory reset instructions in the manual, then installed the latest fw.

Unfortunately, the 7/18/2014 version of the manual no longer includes that information. UGH Anyway, I will definitely give your suggestion a try before anything else.

Are you just looking for info on reset? It's dated but still accurate - https://bitcointalk.org/index.php?topic=697474.0 .  It's a good troubleshooting thread but it shows how to reset.

I'm pretty sure all information on s3+s are outdated by now. It's like the s1.. Just us people with obsolete miners.

In S3 that is far from the truth.  Just look at link I posted it is still accurate info like on reset, works fine.  Hooking it up to PC to access miner and make changes when you cant access via router.  A lot of the troubleshooting.... remains the same as it was long ago.  I almost feel like you did not look at link.... but I cannot be sure on that.

They just have not pushed out changes in firmware or anything to make old guides obsolete for S3's.   I think you need to take a look at them just like one above and you will be surprised how many still work for today, and it's due to no major changes in firmware.  

[zOU]

you should have all 4 plugged in, with 4 seperate wires not the one wire with 2 ends.


kano has a binary update.. its not a complete firmware update but it really makes the s3 more stable.

https://github.com/kanoi/cgminer-binaries/tree/master/AntS3

you have to SSH into the s3 to run the commands..
i suggest putty to do that..
http://www.putty.org/

Unfortunately it is no accessible anymore

This repository has been disabled.
Access to this repository has been disabled by GitHub staff. Contact support to restore access to this repository.

[Real-Duke]

Unfortunately it is no accessible anymore

This repository has been disabled.
Access to this repository has been disabled by GitHub staff. Contact support to restore access to this repository.

Argh wtf...I can confirm its not working anymore but it does some time ago! Maybe only maintenance?

[RichBC]

Really not sure what the issue is here? The S3 is two generations old you cannot expect new information for it, however everything that has been said and released is as good Today as the Day it was released. It's a great miner, one of the best, if not the best that has been released. Just dip into the wealth of information that is available.

Rich

[notlist3d]

Really not sure what the issue is here? The S3 is two generations old you cannot expect new information for it, however everything that has been said and released is as good Today as the Day it was released. It's a great miner, one of the best, if not the best that has been released. Just dip into the wealth of information that is available.

Rich

Only issue was someone said my all S3 info is outdated, and included my post in his quote.   But it seemed someone needed link on how to reset and thats what I gave.
https://bitcointalk.org/index.php?topic=671189.msg14186036#msg14186036 .  It's not outdated it's how to do a S3 or S3+ reset (only exception is if you have then firmware reset button did not work. but few of those come up anymore).

It made it seem as if I was passing out outdated info.   But S3's them self are dated ... so any info is old but still current as far as S3's.  They made no big changes to ever change S3 really.  So not really a problem just someone posting and quoting me without reading link (I think I can only guess).

[in2tactics]

My concern is that one of my S3 devices reboots every few hours. I have tried flashing back to the first FW, doing a hardware reset, and then flashing back to the latest FW. The unit continues to reboot after doing this. I have now swapped the control boards between the rebooting S3 and another one to see if the control board is causing the reboot. My chief concern is determining if I have a bad control board.

[zOU]

My concern is that one of my S3 devices reboots every few hours. I have tried flashing back to the first FW, doing a hardware reset, and then flashing back to the latest FW. The unit continues to reboot after doing this. I have now swapped the control boards between the rebooting S3 and another one to see if the control board is causing the reboot. My chief concern is determining if I have a bad control board.

hello,

do you have a single PSU on that S3 ?
Do you have a large PSU on multiple S3 ?

it could be the PSU restarting rather than the S3 itself ?

also you could run a putty session on that particular S3, log the output, and see what's the last lines ?

[Real-Duke]

I have tried flashing back to the first FW, doing a hardware reset, and then flashing back to the latest FW.

If you ever decide to update again to newer FW there is no need to make the reset! Just keep the settings and upgrade.
Have done this several times with some S3 and S3+ here and never had any kind of problem 

[kenshirothefist]

If anybody is looking for a few second hand AntMiner s3+'s (4x):

https://bitcointalk.org/index.php?topic=1398545.msg14199702#msg14199702

[in2tactics]

My concern is that one of my S3 devices reboots every few hours. I have tried flashing back to the first FW, doing a hardware reset, and then flashing back to the latest FW. The unit continues to reboot after doing this. I have now swapped the control boards between the rebooting S3 and another one to see if the control board is causing the reboot. My chief concern is determining if I have a bad control board.

hello,

do you have a single PSU on that S3 ?
Do you have a large PSU on multiple S3 ?

it could be the PSU restarting rather than the S3 itself ?

also you could run a putty session on that particular S3, log the output, and see what's the last lines ?

I am using a single 1000W PSU for two S3 and only the one S3 is rebooting. I have also attached that S3 by itself to two other PSUs with the same result. I think I will try running a terminal capture via PuTTY as you suggest.

[notlist3d]

My concern is that one of my S3 devices reboots every few hours. I have tried flashing back to the first FW, doing a hardware reset, and then flashing back to the latest FW. The unit continues to reboot after doing this. I have now swapped the control boards between the rebooting S3 and another one to see if the control board is causing the reboot. My chief concern is determining if I have a bad control board.

hello,

do you have a single PSU on that S3 ?
Do you have a large PSU on multiple S3 ?

it could be the PSU restarting rather than the S3 itself ?

also you could run a putty session on that particular S3, log the output, and see what's the last lines ?

I am using a single 1000W PSU for two S3 and only the one S3 is rebooting. I have also attached that S3 by itself to two other PSUs with the same result. I think I will try running a terminal capture via PuTTY as you suggest.

How many PCIE cables are plugged into each S3?   Also what brand/model is PSU?

Also are you overclocking? Have you tried a lower freq?

[in2tactics]

My concern is that one of my S3 devices reboots every few hours. I have tried flashing back to the first FW, doing a hardware reset, and then flashing back to the latest FW. The unit continues to reboot after doing this. I have now swapped the control boards between the rebooting S3 and another one to see if the control board is causing the reboot. My chief concern is determining if I have a bad control board.

hello,

do you have a single PSU on that S3 ?
Do you have a large PSU on multiple S3 ?

it could be the PSU restarting rather than the S3 itself ?

also you could run a putty session on that particular S3, log the output, and see what's the last lines ?

I am using a single 1000W PSU for two S3 and only the one S3 is rebooting. I have also attached that S3 by itself to two other PSUs with the same result. I think I will try running a terminal capture via PuTTY as you suggest.

How many PCIE cables are plugged into each S3?   Also what brand/model is PSU?

Also are you overclocking? Have you tried a lower freq?

Each hashing board has one PCI-E cable plugged in and is set to a frequency of 218.75 MHz. The PSU is a 1000W Corsair RM1000, but I have also used a a 600W Corsair GS600 and a 750W Ultra X4 with only this S3 plugged in. Each setup exhibited the same symptom. I have also tried different frequencies, but nothing above 225 MHz. I have stuck with 218.75 MHz or less whilst attempting to discover the root of the rebooting symptom.

[aarons6]

My concern is that one of my S3 devices reboots every few hours. I have tried flashing back to the first FW, doing a hardware reset, and then flashing back to the latest FW. The unit continues to reboot after doing this. I have now swapped the control boards between the rebooting S3 and another one to see if the control board is causing the reboot. My chief concern is determining if I have a bad control board.

hello,

do you have a single PSU on that S3 ?
Do you have a large PSU on multiple S3 ?

it could be the PSU restarting rather than the S3 itself ?

also you could run a putty session on that particular S3, log the output, and see what's the last lines ?

I am using a single 1000W PSU for two S3 and only the one S3 is rebooting. I have also attached that S3 by itself to two other PSUs with the same result. I think I will try running a terminal capture via PuTTY as you suggest.

How many PCIE cables are plugged into each S3?   Also what brand/model is PSU?

Also are you overclocking? Have you tried a lower freq?

Each hashing board has one PCI-E cable plugged in and is set to a frequency of 218.75 MHz. The PSU is a 1000W Corsair RM1000, but I have also used a a 600W Corsair GS600 and a 750W Ultra X4 with only this S3 plugged in. Each setup exhibited the same symptom. I have also tried different frequencies, but nothing above 225 MHz. I have stuck with 218.75 MHz or less whilst attempting to discover the root of the rebooting symptom.

when it reboots does the whole thing shut down and reboot or just cgminer restarting?

there is a watchdog script that restarts cgminer if it doesnt send in a share for a few minutes.. perhaps its internet related?

[in2tactics]

My concern is that one of my S3 devices reboots every few hours. I have tried flashing back to the first FW, doing a hardware reset, and then flashing back to the latest FW. The unit continues to reboot after doing this. I have now swapped the control boards between the rebooting S3 and another one to see if the control board is causing the reboot. My chief concern is determining if I have a bad control board.

hello,

do you have a single PSU on that S3 ?
Do you have a large PSU on multiple S3 ?

it could be the PSU restarting rather than the S3 itself ?

also you could run a putty session on that particular S3, log the output, and see what's the last lines ?

I am using a single 1000W PSU for two S3 and only the one S3 is rebooting. I have also attached that S3 by itself to two other PSUs with the same result. I think I will try running a terminal capture via PuTTY as you suggest.

How many PCIE cables are plugged into each S3?   Also what brand/model is PSU?

Also are you overclocking? Have you tried a lower freq?

Each hashing board has one PCI-E cable plugged in and is set to a frequency of 218.75 MHz. The PSU is a 1000W Corsair RM1000, but I have also used a a 600W Corsair GS600 and a 750W Ultra X4 with only this S3 plugged in. Each setup exhibited the same symptom. I have also tried different frequencies, but nothing above 225 MHz. I have stuck with 218.75 MHz or less whilst attempting to discover the root of the rebooting symptom.

when it reboots does the whole thing shut down and reboot or just cgminer restarting?

there is a watchdog script that restarts cgminer if it doesnt send in a share for a few minutes.. perhaps its internet related?

I opened an SSH session and was able to determine via "uptime" that the actual unit rebooted. It was not just a cgminer restrart.