Topic: ANTMINER S3+ Discussion and Support Thread - page 61. (Read 710164 times)

My antminer shows in the miner status page that its hashing at 474GH/S, although in Multipool it only shows 381,16GH/s. Any ideas why?

Hi everyone - I really could do with some help.

I have quite a few S3 machines, and i recently flashed 2 machines i had some issues with to a previous firmware.

Now both machines show 0GH/s and show no hashing boards are present.

It does show that its connected to the pool but doesnt do anything else.

I have been looking through almost every thread to find a solution and have tried reinstalling the firmware again and also tried resetting the machines to default settings.

I still get 0GH/s showing and no hashing boards present, I would really appreciate any help or advise as i have tried everything i can think of to fix this issue.

I have put a screenshot of what im getting below, I have left the bitmain pool details for now, Also the cpu usage is also at 100%.

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

That was the first thing i try to do.....no success at all. I cant connect to the miner.....
Is there any other way for hard reset ? I try everything what i found on the net but nothing, maybe the miner is with bad FW that not support reset.

I have a similar problem on a current batch S3. Mine displays xooooooo oooooooo on the first chain. on the plus side, now that the asic is dead the S3 runs abou 3 degrees cooler on that chain. I suspect the asic was overheating and eventually went dead.

If the subnet is the issue you can connect to it directly from your computer with an ethernet cable (bypass the router) and set your ethernet cards subnet to the same as the antminer with a fixed IP address of your choice (different than what you set for the antminer). Then try to connect to it.

you sure you got your IP correct for your network..
the gateway should have no effect on being able to reach your s3, its so your s3 can reach the internet..
the subnet of your network has to be the same on all devices.. so if you put 192.168.0.100 for your router your whole network as to be 192.168.0.###
if your network is 192.168.1.### that is why you cant connect to it. also some routers default to 10.0.0.1 and you have to use that network IP rage then.

Hi there. I have a question.
Today i change the WAN protocol of my antS3 from DHCP to STATIC IP i enter IP(192.168.0.100) but i forgot to add default getaway, dns and etc (I enter only the IP). Now i cant connect to this ANT. I can see it's working with IP Scan but i cant connect (my pc is in the same ip range -192.168.0.195). My reset button doesn't work. I try every method i found here - nothing seems to happen.


I try to ssh - timed out





What can i do ? Is there any other way for hard reset (i try to push the reset button while booting and all other ways like pushing the button for 10 seconds - wait 3 minutes - push the button again - restart  - NOTHING).


Thanks

It looks like a good deal for the S3's as at the very minimum you'll get 2Th/s whereas the S5 is, at a push, 1.3Th/s.
Power consumption wise, you can not beat the S5, so if your electricity costs are high its a no brainer, S5. The other considerations include the space .... you'll need at least 5 times the space for the S3's than the S5 AND the noise as you'll get more noise from a single stock S5 than you will from your 4 S3's put together, and that is not exaggerating.

If I had the option to buy (used from a truster source) 3 S3 and 1 S3+ for $500 as a package complete w/2 psu's and a router or put together an S5, what would the better option be?  They were never overclocked.  Pretty excited to discover mining and excited to get started.

any other links or advice would be appreciated.  Thanks!

If powering the rig off for a few minutes results in the same result, then you may have to browse to the Miner Configuration -> Advanced Settings tab and if the voltage is set to 0000, change it to 0725 if you are running at 250 or less frequency then press Save & Apply.

When you re-check the Miner Status page, it will take a few moments before the chips reset and show o's, they may eventually turn to x's though. The trick is to find a stable voltage setting at the frequency you are running at that results in less HW errors, so you may have to increment the voltage. It is an involved process but will surely yield results if you have the patience.

Have you tried powering it off for ten or fifteen minutes? How are the temps? I have had one asic go straight line and even has hashing board two go zombie twice, but leaving it off for a rest and rebooting it has always fixed the problem for me.

Thanks for the info, but I'm past 90 days on it.

please create a ticket at http://bitmain.zendesk.com  (top right)

or email a support request to support @ bitmain . zendesk . com

If support staffs are online, you may request to chat, too.

https://v2.zopim.com/widget/livechat.html?key=2ZaJsbRPVUUFCqOE8MmgXgbFFdNYxOBP

warranty is 90 days from purchase date. (Bitmaintech.com or Amazon seller "Bitmain")  If you purchased it from else where, please email the proof of purchase in the ticket.

you can try updating the firmware to the most recent January one but before you do that, please power off your S3+ and let it sit for 10-15 minutes and power it back on.  If the xx goes away.  Often time, a few X's on the ASIC status comes from teh firmware bugs.  But your hashing speed is low, too, so the problems could be on the hashing PCB.

so tell us your secret again, please. 

90 days from the day it shipped from Bitmain. If you bought it from a reseller that means when Bitmain shipped it to the reseller.

What is the warranty on the S3+. I have one showing:

oooooooo oooooooo
---ooooo oooooooo

And only getting speeds of about 400.

if you read the forum you know what firmware to use, and its linked several times.

Attn Bittman warranty, please release a new firmware for s3 +, because the last release dates back to 09/01/2015 and is definitely sucks.
thanks sorry for my outburst

Hi all!

Is there any update or setting for this miner not to be a pain in the assssssssssss?
Had the november update and i had regular disconects.
I now have last update and beside a hell lot more disconects!!! (being woken up at 5 in the morning....) my miners get stuck not hashing! few restarts/reboots are needed for this pieces of shit to finally start mining!!!
Is there any update or setting for this miner not to be a pain in the assssssssssss?

Thx!

The temps stay stable 38-39 C and in the beginning had a few x's on one blade but a hard reset vis PSU fixed that and have not seen them since. I dont think it is a lemon just seems after a cpl days to settle in on about 900GHS , and i check no x's no -'s etc. typical HW rate and all so I do a hard reboot via PSU and it goes back to normal 1TH/s =/-  
as of right now

2h44m30s  1,051.52 5s  1,002.39 AVG
8h4m1s 1,000.91 5s 1,001.35 AVG  


1 16 250 38 oooooooo oooooooo
2 16 250 39 oooooooo oooooooo
3 16 250 38 oooooooo oooooooo
4 16 250 40 oooooooo oooooooo

but like i said this wanders 30 secs ago it was 950GHS on the 5s reading (its funny because none of my S3+'s do this just my C1's
I run them all on evga G2 1300W PSU's 1 unit per PSU 2 units per 30amp dedicated breaker (line)
* have spent a small fortune upgrading my electrical service to 200amps and running wiring and such

I run all my S3+'s on 750w-1000w PSU some off the shelf and some server grade and once again run 1 unit per 1 psu I run the S3+'s (3 per dedicated line 30amp breaker)
point being none of the units are starved for power so its definately not a power draw issue or PSU supplying enough power. Ruled that out already.

Honestly i suspect its a firmware issue. Still checking for another version release I am running the second release and all my C1's are Batch2
 What are the boards inside the C1 are they a version of the S3 or S3+?

Think i have caught a cpl C1's down to 880-GHS at one point once again no X's etc. They are still under warranty but unless they light up with a bunch of X's i just can not see sending them in on a assumption we all know miners no mining is not profitable