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

Yea you might have a bricked board. Check this out see if it works for you. https://bitcointalksearch.org/topic/m.9902302

When you say work like normal were you able to access the miner via IP?   Normally with the usb-serial you have to upload something to fix it, just plugging it in normally would not fix a boot problem.

As far ground problem can you go into a little more detail?  Are you talking about a electrical ground problem? Or what type of ground problem?

Hi together,
I have already written this in the german section but hopefully somebody here can help me further with my little problem?
I got an used Antminer S3+ wich only comes up with a red flashing LED in front + shining red LED on the Board + 1 second spinning fans after powering on the PSU.
Inspired that this could be only a software/bootloader Problem I bought a USB-Serial adapter that arrives yesterday.

I plugged the rx/tx into the serial connection on the board from the antminer and the usb plug into my PC. After opening putty and power on the PSU I saw nothing but an empty putty window but the antminer started to work like normal  

I unplugged the usb-serial cable and the miner still works like usual but after powering down the PSU and restart it the miner comes up again only with the flashing red LED....
OK, plug again the rx/tx cables into the board and the usb into my PC = The miner starts like before to work!

Long story...but after all it seems to me that I have a ground problem and this little connection between the miner and my PC during start up of the miner solves it!
Have double check this with my Netbook and a second PSU: If I have only the connection between miner and Netbook nothing comes up but if I plug my netbook thru the wall the miner starts as usual.
Powered on this way the miner just works since yesterday evening
Can somebody give me a hint to solve this maybe little problem?
Thanks in advance!

Hopefully that will fix it.  The good news is there is not a lot of moving parts so limit's it.   Hopefully lubricant will fix it.

Worst case should be new fan.  But since it sounds like it's still spinning I have a feeling lubricant chances are will do the trick.

You need to clean it (the fan's bearing) and put some lubricant

my router that the s3s are connected to has ddr-wt on it.. i can setup a dhcp server with a static hostname..
but now i can see you can also do the same thing ON the s3.. in the hostname tab.

both works the same on my s3.

i just tried with my comcast xfinity router, and even tho it has a name, it wont resolve.


instead of using internal names, let me try what you are doing and try to dns a web address.


i think i might have found your problem.

the s3 has a built in dhcp server. in the s3 it is set to ignore outside dhcp. i turned mine off.. so it just uses the lan network dhcp server, but you having 100s of miners dont want to do that to each one lol.


to be honest, i would just use the IP and then static route it to your proxy computer.. skip names all together.. its not like you dont know 192.168.1.133 is your ip.

then just use the IP:PORT as your pool url.

Mine makes a similar noise during certain speeds, I think its one of the bearings on the fans that's going out soon.

You configured the hostname that you tested on your router or on your miner?

I just tested from the WebGUI instead of the CLI, and interesting I do an error from the S3 seems it is aware of the IP address but its not completing the process. See below.

dunno.. just tried it, no issues..

I tried everything you suggested even though I know it would not work. DNS is part of my job for the past 14 years.

Put a private DNS server like you said same issue.

Named the 192.168.1.133 proxy1 locally like you said same issue.

Same things Windows PC and all other resolve proxy and the DNS but not the S3's.

And it is not trouble to configure a public DNS server took me all of 10 minutes.  What would take a while is reconfiguring over 200 miners if I have to change pools, or change an IP in the pool configs when all you would have to do is change a proxy entry or a dns entry so much easier.


Here is a S3 and PC directly connected to my labs Uverse modem, same DNS from the router, same router, same DHCP server from the router.  S3 fails.

S3:
root@antMiner:~# ping proxy1
ping: bad address 'proxy1'

PC:
C:\>ping proxy1

Pinging proxy1.gateway.pace.com [192.168.1.133] with 32 bytes of data:
Reply from 192.168.1.133: bytes=32 time<1ms TTL=64
Reply from 192.168.1.133: bytes=32 time<1ms TTL=64
Reply from 192.168.1.133: bytes=32 time<1ms TTL=64
Reply from 192.168.1.133: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.133:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

DNS resolves fine on Windows, Linux, Mac and other brands of miners, but not on Bitmains S3 wether using my private or public DNS serves.

Even SSH to the S3's to resolve it fails to resolve in nslookup and ping.

It is now a private DNS server same issue. My local DNS server is now on 192.168.1.10.

But I knew that would not fix it.  DNS an local proxies make configuring 100s of miners a lot easier.

Clicking could be something even slightly brushing against a fan blade. Probably worth opening the case up and taking a look (while it is off).

Have 2 S3+'s and one of them is making a clicking noise. Also on the inside of the miner just behind the exhaust fan a red light is on. I think it's on its way out.

he is trying to set a public dns to his 192.168.1.X IP.. for some reason so he can use a PC on his network as a pool proxy..

and he says the IP works just fine.. but he doesnt want to use an ip, he wants to use a public url.. 

LOL you come on here.. asking for help.. yet IGNORE all help....


seriously...

you just posting to here yourself?

why are you going through ALL THE TROUBLE to PUBLICLY DNS YOUR LAN IP..

go into the pc and set the IP as static.
then just go into the router.. find the LAN IP you want and name it.
then use "computername" as your host.

Does the name resolve OK on your usual PC? Maybe a minor mis-spelling of the name?

With a proper DNS it should work fine. I use 8.8.8.8 .

But if truly for some reason your network is not resolving it, have you tried using the IP address instead of web address?

Ok I built a BIND DNS server running on Ubuntu 15.04 as the internal put the same DNS entries.

Same problem with the S3+, it just refuses to resolve that DNS entry.

All other manufacturers I have work with the internal DNS as well as the external providing a private IP.

Any other ideas?

Once the S3 is on wifi I have no problem accessing it through any browser.

There is no problem to access it also through LAN when the S3 is connected to my router or my laptop (except I have to set up my ip address manually to 192.168.1.x)

The thing is as soon as I plug it into router or laptop, the S3 tries to go through LAN to hash, so when I disconnect it, it keeps trying via LAN even though there is no connection...

WAN / LAN what's the difference for the S3 ?