ANTMINER S3+ Discussion and Support Thread

[jpchrist]

How can I safely power off the s3 antminer? Anyone have suggestions for the best way? Thanks.

Any object can be used to flip the switch.  I find a finger works best.

[Biodom]

How can I safely power off the s3 antminer? Anyone have suggestions for the best way? Thanks.

the safest is to ssh (using terminal or putty) into the miner, login by "root" passwd, then issue the following

Code:

poweroff -d 3

press return/enter
type <exit>
return
command line will return to Terminal/Putty

miner will power down slowly in 3 sec
wait 20-30 sec as fans decelerate before switching the PSU OFF

what other people have jokingly posted is OK too, but would result in a bit higher temperature of the chips since fans would not slowly decelerate and upon immediate restart you could get a couple of ASIC errors, but you can remedy this by restarting cgminer once or twice next 1-2 min.

[wlefever]

I got an issue with one of my S3s. It does not hash at all. I can connect to it no problem. This one appears to have an issue where the unit does not hash at all. All the settings are identical to the other ones (minus the IP addresses which are statically assigned. I can connect to it from within my lan to get to the web interface. cgminer appears to be running but not hashing. Anyone run into this? It seems like it would be a quick fix. Thanks

Did you open it up and check the cables from the blades to the controller? You could try to reseat the cables as well. If that does not fix it the next step would be to swap out controllers to determine if it is the blade/s or controller. I did not cover the power supply verification as I am sure you have already been down that road. Please let us know what you find.

I will give that a try. I checked on the IP conflict and that was not an issue. I statically assign everything in my network so I know thats not it. But just the same I checked just in case. I will open it up and check it. I  will post back if that was the problem.

Why after I statically assigned my ip address on my miner can i not pull the interface back up on the web browser?  

Did you set your subnet mask and dns settings correctly?

Yeah I matched my IPv4, subnet mask, and default gateway

10.8.201.103
255.255.255.0
10.8.201.1

But, cant seem to reach the miner again

not sure I understand. What do you mean "I matched my IPv4 address"?
IP address of the miner has to be different (after the last .) from your computer/laptop and unique for your LAN (no other piece of equipment with the same IP).
Also, you need a fourth lane-your DNS, which could be same as your router/getaway (10.8.201.1)

Sorry, let me try to explain better.  My network ip address is 10.8.201.103 so I had to temporarily change my computer to 192.168.1.99 (plugged the miner into computer and the interface ran) .  When i changed to try and get the miner to run on my network ip (10.8.201.103) I was never able to get back to the miner interface

[buy4crypto]

How can I safely power off the s3 antminer? Anyone have suggestions for the best way? Thanks.

Any object can be used to flip the switch.  I find a finger works best.

lol, fair enough. Just being safe

[Biodom]

I got an issue with one of my S3s. It does not hash at all. I can connect to it no problem. This one appears to have an issue where the unit does not hash at all. All the settings are identical to the other ones (minus the IP addresses which are statically assigned. I can connect to it from within my lan to get to the web interface. cgminer appears to be running but not hashing. Anyone run into this? It seems like it would be a quick fix. Thanks

Did you open it up and check the cables from the blades to the controller? You could try to reseat the cables as well. If that does not fix it the next step would be to swap out controllers to determine if it is the blade/s or controller. I did not cover the power supply verification as I am sure you have already been down that road. Please let us know what you find.

I will give that a try. I checked on the IP conflict and that was not an issue. I statically assign everything in my network so I know thats not it. But just the same I checked just in case. I will open it up and check it. I  will post back if that was the problem.

Why after I statically assigned my ip address on my miner can i not pull the interface back up on the web browser?  

Did you set your subnet mask and dns settings correctly?

Yeah I matched my IPv4, subnet mask, and default gateway

10.8.201.103
255.255.255.0
10.8.201.1

But, cant seem to reach the miner again

not sure I understand. What do you mean "I matched my IPv4 address"?
IP address of the miner has to be different (after the last .) from your computer/laptop and unique for your LAN (no other piece of equipment with the same IP).
Also, you need a fourth lane-your DNS, which could be same as your router/getaway (10.8.201.1)

Sorry, let me try to explain better.  My network ip address is 10.8.201.103 so I had to temporarily change my computer to 192.168.1.99 (plugged the miner into computer and the interface ran) .  When i changed to try and get the miner to run on my network ip (10.8.201.103) I was never able to get back to the miner interface

without going into too much detail, go to sushi or dogie "S1 troubleshoot and setup" threads and read carefully the setup.
What you describe has insuffient specifics, as to your PC (after changes), router, miner. Did you setup DNS? This line was completely missing from your explanation. And what is the current IP of PC and did you setup miner as DHCP or static?

[Rapturoso]

So it seems that the Batch 5's went out early as six of them arrived to me in the UK a little unexpectedly this morning.  Not that I'm complaining, I just hadn't sorted the PSU's yet as I was expecting them to take longer to get here.  Just letting others know so you can expect them soon.

Cheers,
bitK

What shipping company did you use and when did you complete payment for the order? I'm just curious as I have 4 from batch 5 ordered and I'd like some idea as to when they are likely to arrive here in the UK.

[-droid-]

S3 not hashing correctly?

I've got 4 units and only 1 hashes at 440-441 at stock freq, the others get 414-420ish.

In working with bitmain over email I tried re applying thermal paste and swapping psu's around and still nada.  Then they asked me to swap control board from the one good miner to one that is underperforming and lo and behold the underperforming one is now hashing at 440-441 with the other hashing at the lower speed.

I've swapped it on then others and it's the same result.  Since the static IP is saved on the control board it moves from swap to swap with the good control board, so it constantly thinks it's the good unit and hashes at adv. spec

so after further testing with bitmain engineer he had me test each blade individually, and individually after 15min they were hashing around 217-220.. maybe 15min was not long enough to test but after sending him the screenshots of them individually he went ahead and sent me RMA label for the 3 control boards.

just sucks having to be down 3 miners while they ship to china and wait for the replacements to ship back to me

[jpchrist]

S3 not hashing correctly?

I've got 4 units and only 1 hashes at 440-441 at stock freq, the others get 414-420ish.

In working with bitmain over email I tried re applying thermal paste and swapping psu's around and still nada.  Then they asked me to swap control board from the one good miner to one that is underperforming and lo and behold the underperforming one is now hashing at 440-441 with the other hashing at the lower speed.

I've swapped it on then others and it's the same result.  Since the static IP is saved on the control board it moves from swap to swap with the good control board, so it constantly thinks it's the good unit and hashes at adv. spec

so after further testing with bitmain engineer he had me test each blade individually, and individually after 15min they were hashing around 217-220.. maybe 15min was not long enough to test but after sending him the screenshots of them individually he went ahead and sent me RMA label for the 3 control boards.

just sucks having to be down 3 miners while they ship to china and wait for the replacements to ship back to me

Dont do it! Its really not worth sending them back. 420 gh/s is actually within the 441 +/- 5% range bitmain has advertised. That extra ~20 gh/s is only about 30 cents a day.  You will lose more having the miners not hashing than from the lower hashrate. At the very least wait for a few difficulty increases before sending them back.

[Lowell904]

And again, the return of the dreaded incessant beeping. Same errors again!

Tue Aug  5 20:38:32 2014 kern.err kernel: [53274.450000] usb 1-1: clear tt 1 (9041) error -71
Tue Aug  5 20:38:32 2014 kern.err kernel: [53274.460000] usb 1-1: clear tt 1 (9041) error -71
Tue Aug  5 20:38:32 2014 kern.err kernel: [53274.470000] usb 1-1: clear tt 1 (9041) error -71
Tue Aug  5 20:38:32 2014 kern.err kernel: [53274.480000] usb 1-1: clear tt 1 (9041) error -71
Tue Aug  5 20:38:32 2014 kern.err kernel: [53274.490000] hub 1-1:1.0: cannot reset port 1 (err = -71)
Tue Aug  5 20:38:32 2014 kern.err kernel: [53274.570000] hub 1-1:1.0: cannot reset port 1 (err = -71)
Tue Aug  5 20:38:32 2014 kern.err kernel: [53274.570000] usb 1-1: clear tt 1 (9041) error -71
Tue Aug  5 20:38:32 2014 kern.err kernel: [53274.580000] hub 1-1:1.0: cannot reset port 1 (err = -71)
Tue Aug  5 20:38:32 2014 kern.err kernel: [53274.590000] hub 1-1:1.0: cannot reset port 1 (err = -71)
Tue Aug  5 20:38:32 2014 kern.err kernel: [53274.600000] hub 1-1:1.0: cannot reset port 1 (err = -71)
Tue Aug  5 20:38:32 2014 kern.err kernel: [53274.600000] hub 1-1:1.0: Cannot enable port 1.  Maybe the USB cable is bad?

Still no word from Bitmain... Is anyone else experiencing these errors?

Some people have gotten bad control boards.  You might want to try switching boards,  if you have more than one unit and both of them don't have the issue.

[navigator]

S3 not hashing correctly?

I've got 4 units and only 1 hashes at 440-441 at stock freq, the others get 414-420ish.

In working with bitmain over email I tried re applying thermal paste and swapping psu's around and still nada.  Then they asked me to swap control board from the one good miner to one that is underperforming and lo and behold the underperforming one is now hashing at 440-441 with the other hashing at the lower speed.

I've swapped it on then others and it's the same result.  Since the static IP is saved on the control board it moves from swap to swap with the good control board, so it constantly thinks it's the good unit and hashes at adv. spec

so after further testing with bitmain engineer he had me test each blade individually, and individually after 15min they were hashing around 217-220.. maybe 15min was not long enough to test but after sending him the screenshots of them individually he went ahead and sent me RMA label for the 3 control boards.

just sucks having to be down 3 miners while they ship to china and wait for the replacements to ship back to me

Does bitmain not let you send a deposit, they send you new parts, you send old parts back, then they send deposit back?

[not.you]

I got an issue with one of my S3s. It does not hash at all. I can connect to it no problem. This one appears to have an issue where the unit does not hash at all. All the settings are identical to the other ones (minus the IP addresses which are statically assigned. I can connect to it from within my lan to get to the web interface. cgminer appears to be running but not hashing. Anyone run into this? It seems like it would be a quick fix. Thanks

Did you open it up and check the cables from the blades to the controller? You could try to reseat the cables as well. If that does not fix it the next step would be to swap out controllers to determine if it is the blade/s or controller. I did not cover the power supply verification as I am sure you have already been down that road. Please let us know what you find.

I will give that a try. I checked on the IP conflict and that was not an issue. I statically assign everything in my network so I know thats not it. But just the same I checked just in case. I will open it up and check it. I  will post back if that was the problem.

Why after I statically assigned my ip address on my miner can i not pull the interface back up on the web browser?  

Did you set your subnet mask and dns settings correctly?

Yeah I matched my IPv4, subnet mask, and default gateway

10.8.201.103
255.255.255.0
10.8.201.1

But, cant seem to reach the miner again

I would be really surprised if the subnet mask on that network was really 255.255.255.0.  That IP is a class A address which (without any fancy subnetting) would be 255.0.0.0 for the mask.

[-droid-]

S3 not hashing correctly?

I've got 4 units and only 1 hashes at 440-441 at stock freq, the others get 414-420ish.

In working with bitmain over email I tried re applying thermal paste and swapping psu's around and still nada.  Then they asked me to swap control board from the one good miner to one that is underperforming and lo and behold the underperforming one is now hashing at 440-441 with the other hashing at the lower speed.

I've swapped it on then others and it's the same result.  Since the static IP is saved on the control board it moves from swap to swap with the good control board, so it constantly thinks it's the good unit and hashes at adv. spec

so after further testing with bitmain engineer he had me test each blade individually, and individually after 15min they were hashing around 217-220.. maybe 15min was not long enough to test but after sending him the screenshots of them individually he went ahead and sent me RMA label for the 3 control boards.

just sucks having to be down 3 miners while they ship to china and wait for the replacements to ship back to me

Does bitmain not let you send a deposit, they send you new parts, you send old parts back, then they send deposit back?

no they dont unfortunately

[-droid-]

Dont do it! Its really not worth sending them back. 420 gh/s is actually within the 441 +/- 5% range bitmain has advertised. That extra ~20 gh/s is only about 30 cents a day.  You will lose more having the miners not hashing than from the lower hashrate. At the very least wait for a few difficulty increases before sending them back.

too late, just gave the package to the UPS guy

[itod]

I got an issue with one of my S3s. It does not hash at all. I can connect to it no problem. This one appears to have an issue where the unit does not hash at all. All the settings are identical to the other ones (minus the IP addresses which are statically assigned. I can connect to it from within my lan to get to the web interface. cgminer appears to be running but not hashing. Anyone run into this? It seems like it would be a quick fix. Thanks

Did you open it up and check the cables from the blades to the controller? You could try to reseat the cables as well. If that does not fix it the next step would be to swap out controllers to determine if it is the blade/s or controller. I did not cover the power supply verification as I am sure you have already been down that road. Please let us know what you find.

I will give that a try. I checked on the IP conflict and that was not an issue. I statically assign everything in my network so I know thats not it. But just the same I checked just in case. I will open it up and check it. I  will post back if that was the problem.

Why after I statically assigned my ip address on my miner can i not pull the interface back up on the web browser?  

Did you set your subnet mask and dns settings correctly?

Yeah I matched my IPv4, subnet mask, and default gateway

10.8.201.103
255.255.255.0
10.8.201.1

But, cant seem to reach the miner again

I would be really surprised if the subnet mask on that network was really 255.255.255.0.  That IP is a class A address which (without any fancy subnetting) would be 255.0.0.0 for the mask.

You are right, 255.0.0.0 is probbably the right netmask, but that shouldn't be an issue since they are almost certanly within the same C class (first three dot separated numbers in IP address are the same), so machines would see each other even with the wrong netmask. The issue may be that he has collison on the network since he gave the same IP (10.8.201.103) to both his computer and the miner. If that's the case ask your network admin to give you another IP for the miner.

It's interesting to notice that people are avoiding to use DHCP with the S3s because they often run into problems not following proper DHCP network administration. Proper procedure would be to find your miners MAC address, and then reserving fixed IP address for that MAC address in your DHCP server settings. Your DHCP server is almost always on your router, find those settings through web interface of your router. This way you won't have to monkey around with DNS and other settings, and your S3 will have non-changing IP which you will always be able to find.

[jpchrist]

Dont do it! Its really not worth sending them back. 420 gh/s is actually within the 441 +/- 5% range bitmain has advertised. That extra ~20 gh/s is only about 30 cents a day.  You will lose more having the miners not hashing than from the lower hashrate. At the very least wait for a few difficulty increases before sending them back.

too late, just gave the package to the UPS guy

Did you have to pay for shipping at all?

[wlefever]

I got an issue with one of my S3s. It does not hash at all. I can connect to it no problem. This one appears to have an issue where the unit does not hash at all. All the settings are identical to the other ones (minus the IP addresses which are statically assigned. I can connect to it from within my lan to get to the web interface. cgminer appears to be running but not hashing. Anyone run into this? It seems like it would be a quick fix. Thanks

Did you open it up and check the cables from the blades to the controller? You could try to reseat the cables as well. If that does not fix it the next step would be to swap out controllers to determine if it is the blade/s or controller. I did not cover the power supply verification as I am sure you have already been down that road. Please let us know what you find.

I will give that a try. I checked on the IP conflict and that was not an issue. I statically assign everything in my network so I know thats not it. But just the same I checked just in case. I will open it up and check it. I  will post back if that was the problem.

Why after I statically assigned my ip address on my miner can i not pull the interface back up on the web browser?  

Did you set your subnet mask and dns settings correctly?

Yeah I matched my IPv4, subnet mask, and default gateway

10.8.201.103
255.255.255.0
10.8.201.1

But, cant seem to reach the miner again

not sure I understand. What do you mean "I matched my IPv4 address"?
IP address of the miner has to be different (after the last .) from your computer/laptop and unique for your LAN (no other piece of equipment with the same IP).
Also, you need a fourth lane-your DNS, which could be same as your router/getaway (10.8.201.1)

Sorry, let me try to explain better.  My network ip address is 10.8.201.103 so I had to temporarily change my computer to 192.168.1.99 (plugged the miner into computer and the interface ran) .  When i changed to try and get the miner to run on my network ip (10.8.201.103) I was never able to get back to the miner interface

without going into too much detail, go to sushi or dogie "S1 troubleshoot and setup" threads and read carefully the setup.
What you describe has insuffient specifics, as to your PC (after changes), router, miner. Did you setup DNS? This line was completely missing from your explanation. And what is the current IP of PC and did you setup miner as DHCP or static?

Static address on this one, I think i found my error. I applied the same ip as my computer. What can I do now to essentially start over?

[BennyTheBall]

Has anyone tried to use avahi (bonjour or Zeroconf) on either the S1 or the S3 miners? This would be very convenient as it would allow using dhcp and never have to worry about the ip address. You could just address the miner by <name>.local . Since this is basically OpenWRT, there is an avahi-daemon package available. I installed it on an S3 and it worked for a couple of minutes but then it stops resolving the .local name. I saw nothing in the logs to indicate a failure. When I restart the avahi-daemon service it's all good again for several minutes. Played with config files, nothing worked. Ideas?

BTW, this has zero effect on the hashing.

[-droid-]

Dont do it! Its really not worth sending them back. 420 gh/s is actually within the 441 +/- 5% range bitmain has advertised. That extra ~20 gh/s is only about 30 cents a day.  You will lose more having the miners not hashing than from the lower hashrate. At the very least wait for a few difficulty increases before sending them back.

too late, just gave the package to the UPS guy

Did you have to pay for shipping at all?

no, bitmain provided return label

[Phosphorous]

Bitmain,

Could you let us know about the upgrade kits for S1s and S2s? When will these be available? I'd like to upgrade all of my S1s. Also, will the DC/DC component be fixed in these?

Why bother? What cost savings are you expecting to realize from reusing an aluminum frame and maybe the controller? $40?

[SolidStateSurvivor]

I have a question concerning the controller, I don't know if this has been address before. The S3 has a TP-Link TL-WR743N/ND with a MIPS 24Kc CPU in it right, which is a single core?

Why is the Load Average over 2.00 all the time? Shouldn't it be under 0.7 - 0.9 to work properly?

http://blog.scoutapp.com/articles/2009/07/31/understanding-load-averages

It should be under 1.0 for a single core. Can you disable some logging?

What does your Load Average say, or some of you other guys, what are you getting?

Cryptocoinsnews are getting Load Average of 3.09 2.56 1.66 in their review. (top left of the pic) Newer ran a linux system with this high load.