Author

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

hero member
Activity: 784
Merit: 504
Now I just need to sort out this other stubborn unit!

Go with confidence and fix the other one, already guided you how to proceed.
Waiting for a repair and RMA takes time which is very precious for miners.
Any mining hardware profitability is heavenly in inverse proportion to time.
Me or someone else are always here to support as far as we can.
You may try overclocking after you gained much confidence with your S3 hardware.

Legend! I'll go have some dinner (the missus is on my back) then I'll attempt a repair on this other unit. Wish me luck!

Good Luck, my all best wishes! Smiley
legendary
Activity: 1235
Merit: 1202
Now I just need to sort out this other stubborn unit!

Go with confidence and fix the other one, already guided you how to proceed.
Waiting for a repair and RMA takes time which is very precious for miners.
Any mining hardware profitability is heavenly in inverse proportion to time.
Me or someone else are always here to support as far as we can.
You may try overclocking after you gained much confidence with your S3 hardware.

Legend! I'll go have some dinner (the missus is on my back) then I'll attempt a repair on this other unit. Wish me luck!
hero member
Activity: 784
Merit: 504
Now I just need to sort out this other stubborn unit!

Go with confidence and fix the other one, already guided you how to proceed.
Waiting for a repair and RMA takes time which is very precious for miners.
Any mining hardware profitability is heavenly in inverse proportion to time.
Me or someone else are always here to support as far as we can.
You may try overclocking after you gained much confidence with your S3 hardware.
legendary
Activity: 1235
Merit: 1202
Thanks, I've tried the PCI-E connectors and still the same problem. I've now set up the other miner and I can't get either one to mine. Under "Miner Status" it just shows all empty readings and says "This section contains no values yet" From what I've read it's a DNS issue, are you able to instruct me how to rectify this and where to place the DNS values? I'm a bit of a noob at this and would appreciate the help Smiley

Try the other steps given in my above post for the faulty miner.
For the other one go to, Network>Diagnostic Page and click on the ping button and check whether it successfully ping.
Else change DNS to 4.2.2.2 and add one more as 8.8.8.8 on the WAN page.
Then again do the ping test on your diagnostic page if again fails,
change your default gate way to the default gate way of your modem/pc.
Again try ping now it may already started working.

It could ping no problem... I added in the DNS under the Network > Interfaces page > WAN > Advanced settings page where it says "Use custom DNS servers"

It now shows DNS 1: 4.2.2.2 and DNS 2: 8.8.8.8 under the Status > Overview pages but still nothing on the Miner Status page. It's very weird, I've compared all the settings just as the one with the broken chain and it just doesn't want to start. That being said the one with the broken chain doesn't have the DNS settings on it, I just had to leave it for a while and it started. This one.... nothing. I'm at a loss Sad

DNS is set on control board not on blades.

So I'm entering in the DNS values in the wrong location? Could you please tell me exactly where they need to go?

Look at this image below.


Yep! That's exactly how I had it and still nothing. Did a factory reset, re entered all the values and guess what? Works like a charm now! ASIC status on this one is all golden and hashing at an average of 460GH/S Cheesy

Thank you so much for your help, you've been amazing. My first foray into some serious BTC mining hardware (I foiled with Block Erupters) and it was a little daunting. You gave me the help I needed Smiley

Now I just need to sort out this other stubborn unit!
hero member
Activity: 784
Merit: 504
Thanks, I've tried the PCI-E connectors and still the same problem. I've now set up the other miner and I can't get either one to mine. Under "Miner Status" it just shows all empty readings and says "This section contains no values yet" From what I've read it's a DNS issue, are you able to instruct me how to rectify this and where to place the DNS values? I'm a bit of a noob at this and would appreciate the help Smiley

Try the other steps given in my above post for the faulty miner.
For the other one go to, Network>Diagnostic Page and click on the ping button and check whether it successfully ping.
Else change DNS to 4.2.2.2 and add one more as 8.8.8.8 on the WAN page.
Then again do the ping test on your diagnostic page if again fails,
change your default gate way to the default gate way of your modem/pc.
Again try ping now it may already started working.

It could ping no problem... I added in the DNS under the Network > Interfaces page > WAN > Advanced settings page where it says "Use custom DNS servers"

It now shows DNS 1: 4.2.2.2 and DNS 2: 8.8.8.8 under the Status > Overview pages but still nothing on the Miner Status page. It's very weird, I've compared all the settings just as the one with the broken chain and it just doesn't want to start. That being said the one with the broken chain doesn't have the DNS settings on it, I just had to leave it for a while and it started. This one.... nothing. I'm at a loss Sad

DNS is set on control board not on blades.

So I'm entering in the DNS values in the wrong location? Could you please tell me exactly where they need to go?

Look at this image below. DNS setting need to be enter like in the image.
Go to Network->Interfaces->WAN
or Network -> Click Edit Button on WAN row.
hero member
Activity: 784
Merit: 504
my mine drops down to 410-415GH. I would rather keep it running and pay a deposit so he would ship a new controller out and refund me after he receives the bad one than shut the miner down for a week or two.

It may not be a controller issues as from your description.
Are you seeing any "x" or "-" in you asic status page?
Give me your Ant S3-es fans speed, temperatures of miner and ambient temperature?.
Most probably its, the heat dissipation issue and the chip are throttling to lower clocks automatically as in GPUs.
As already advised by bitmaintech support engineers, unscrew the chip side heatsink and check the condition of thermal grease.
Remove it with a cloth and apply new thermal paste grease and it will be mining back at 441.
Use a good thermal grease which provide conductivity above 3.
sorry but I can not access my interface for this miner. It's still mining and Bitmain PM that he has turned my problem over to his engineer which I am waiting to hear from. I have not tried to reboot or use the reset button yet as I am afraid the miner may not start back up. But once I get thru that problem I will give what you suggested a try. But the last time I was able to get on the miners interface ( a couple days ago) I was seeing no x's and it all looked fine. Just starting out normal speed and slowing dropping down. Thanks

If you can occasionally access your miner web interface it may be a network configuration issue than a hardware issue.
Is there any network conflict between you miners?
Have you tried changing you S3 miners IPs earlier or your all miners are at same IP?
Connect your pc to the same Ethernet Switch/Router your miners are connected and try accessing them.
You have another option to install the M's Antmonitor and do a scan.
If starts at good hashrate and further slows down leads to think about replacing thermal paste.
legendary
Activity: 1235
Merit: 1202
Thanks, I've tried the PCI-E connectors and still the same problem. I've now set up the other miner and I can't get either one to mine. Under "Miner Status" it just shows all empty readings and says "This section contains no values yet" From what I've read it's a DNS issue, are you able to instruct me how to rectify this and where to place the DNS values? I'm a bit of a noob at this and would appreciate the help Smiley

Try the other steps given in my above post for the faulty miner.
For the other one go to, Network>Diagnostic Page and click on the ping button and check whether it successfully ping.
Else change DNS to 4.2.2.2 and add one more as 8.8.8.8 on the WAN page.
Then again do the ping test on your diagnostic page if again fails,
change your default gate way to the default gate way of your modem/pc.
Again try ping now it may already started working.

It could ping no problem... I added in the DNS under the Network > Interfaces page > WAN > Advanced settings page where it says "Use custom DNS servers"

It now shows DNS 1: 4.2.2.2 and DNS 2: 8.8.8.8 under the Status > Overview pages but still nothing on the Miner Status page. It's very weird, I've compared all the settings just as the one with the broken chain and it just doesn't want to start. That being said the one with the broken chain doesn't have the DNS settings on it, I just had to leave it for a while and it started. This one.... nothing. I'm at a loss Sad

DNS is set on control board not on blades.

So I'm entering in the DNS values in the wrong location? Could you please tell me exactly where they need to go?
sr. member
Activity: 588
Merit: 269
I know this will have been asked before but for some reason I'm not getting any results back.

What is the UK VAT on Average for the 2X S3 ?

Thanks



Around GBP 110-120 IIRC (edit: including the GBP 11 brokerage fee for UPS, others may vary).

Thanks for confirming
hero member
Activity: 784
Merit: 504
Thanks, I've tried the PCI-E connectors and still the same problem. I've now set up the other miner and I can't get either one to mine. Under "Miner Status" it just shows all empty readings and says "This section contains no values yet" From what I've read it's a DNS issue, are you able to instruct me how to rectify this and where to place the DNS values? I'm a bit of a noob at this and would appreciate the help Smiley

Try the other steps given in my above post for the faulty miner.
For the other one go to, Network>Diagnostic Page and click on the ping button and check whether it successfully ping.
Else change DNS to 4.2.2.2 and add one more as 8.8.8.8 on the WAN page.
Then again do the ping test on your diagnostic page if again fails,
change your default gate way to the default gate way of your modem/pc.
Again try ping now it may already started working.

It could ping no problem... I added in the DNS under the Network > Interfaces page > WAN > Advanced settings page where it says "Use custom DNS servers"

It now shows DNS 1: 4.2.2.2 and DNS 2: 8.8.8.8 under the Status > Overview pages but still nothing on the Miner Status page. It's very weird, I've compared all the settings just as the one with the broken chain and it just doesn't want to start. That being said the one with the broken chain doesn't have the DNS settings on it, I just had to leave it for a while and it started. This one.... nothing. I'm at a loss Sad

DNS is set on control board not on blades.
newbie
Activity: 49
Merit: 0
I know this will have been asked before but for some reason I'm not getting any results back.

What is the UK VAT on Average for the 2X S3 ?

Thanks



Around GBP 110-120 IIRC (edit: including the GBP 11 brokerage fee for UPS, others may vary).
sr. member
Activity: 588
Merit: 269
I know this will have been asked before but for some reason I'm not getting any results back.

What is the UK VAT on Average for the 2X S3 ?

Thanks

legendary
Activity: 1232
Merit: 1000
my mine drops down to 410-415GH. I would rather keep it running and pay a deposit so he would ship a new controller out and refund me after he receives the bad one than shut the miner down for a week or two.

It may not be a controller issues as from your description.
Are you seeing any "x" or "-" in you asic status page?
Give me your Ant S3-es fans speed, temperatures of miner and ambient temperature?.
Most probably its, the heat dissipation issue and the chip are throttling to lower clocks automatically as in GPUs.
As already advised by bitmaintech support engineers, unscrew the chip side heatsink and check the condition of thermal grease.
Remove it with a cloth and apply new thermal paste grease and it will be mining back at 441.
Use a good thermal grease which provide conductivity above 3.
sorry but I can not access my interface for this miner. It's still mining and Bitmain PM that he has turned my problem over to his engineer which I am waiting to hear from. I have not tried to reboot or use the reset button yet as I am afraid the miner may not start back up. But once I get thru that problem I will give what you suggested a try. But the last time I was able to get on the miners interface ( a couple days ago) I was seeing no x's and it all looked fine. Just starting out normal speed and slowing dropping down. Thanks
full member
Activity: 238
Merit: 100
Kia ora!
my mine drops down to 410-415GH. I would rather keep it running and pay a deposit so he would ship a new controller out and refund me after he receives the bad one than shut the miner down for a week or two.

I have sent the same request away as well. Ive asked for a cost of a replacement controller.
legendary
Activity: 1235
Merit: 1202
Thanks, I've tried the PCI-E connectors and still the same problem. I've now set up the other miner and I can't get either one to mine. Under "Miner Status" it just shows all empty readings and says "This section contains no values yet" From what I've read it's a DNS issue, are you able to instruct me how to rectify this and where to place the DNS values? I'm a bit of a noob at this and would appreciate the help Smiley

Try the other steps given in my above post for the faulty miner.
For the other one go to, Network>Diagnostic Page and click on the ping button and check whether it successfully ping.
Else change DNS to 4.2.2.2 and add one more as 8.8.8.8 on the WAN page.
Then again do the ping test on your diagnostic page if again fails,
change your default gate way to the default gate way of your modem/pc.
Again try ping now it may already started working.

It could ping no problem... I added in the DNS under the Network > Interfaces page > WAN > Advanced settings page where it says "Use custom DNS servers"

It now shows DNS 1: 4.2.2.2 and DNS 2: 8.8.8.8 under the Status > Overview pages but still nothing on the Miner Status page. It's very weird, I've compared all the settings just as the one with the broken chain and it just doesn't want to start. That being said the one with the broken chain doesn't have the DNS settings on it, I just had to leave it for a while and it started. This one.... nothing. I'm at a loss Sad
hero member
Activity: 784
Merit: 504
my mine drops down to 410-415GH. I would rather keep it running and pay a deposit so he would ship a new controller out and refund me after he receives the bad one than shut the miner down for a week or two.

It may not be a controller issues as from your description.
Are you seeing any "x" or "-" in you asic status page?
Give me your Ant S3-es fans speed, temperatures of miner and ambient temperature?.
Most probably its, the heat dissipation issue and the chip are throttling to lower clocks automatically as in GPUs.
As already advised by bitmaintech support engineers, unscrew the chip side heatsink and check the condition of thermal grease.
Remove it with a cloth and apply new thermal paste grease and it will be mining back at 441.
Use a good thermal grease which provide conductivity above 3.
hero member
Activity: 784
Merit: 504
Thanks, I've tried the PCI-E connectors and still the same problem. I've now set up the other miner and I can't get either one to mine. Under "Miner Status" it just shows all empty readings and says "This section contains no values yet" From what I've read it's a DNS issue, are you able to instruct me how to rectify this and where to place the DNS values? I'm a bit of a noob at this and would appreciate the help Smiley

Try the other steps given in my above post for the faulty miner.
For the other one go to, Network>Diagnostic Page and click on the ping button and check whether it successfully ping.
Else change DNS to 4.2.2.2 and add one more as 8.8.8.8 on the WAN page.
Then again do the ping test on your diagnostic page if again fails,
change your default gate way to the default gate way of your modem/pc.
Again try ping now it may already started working.
legendary
Activity: 1232
Merit: 1000
Since mine has the same probs as yours, what solution did Bitmain offer to you to rectify the faulty control board.

Nothing yet , waiting to hear back
Makes ya wonder why they constantly ship f'n lemons, also makes me wonder what I'll end up with out of the 4 units I ordered.
my miner drops down to 410-415GH. I would rather keep it running and pay a deposit so he would ship a new controller out and refund me after he receives the bad one than shut the miner down for a week or two.
legendary
Activity: 1235
Merit: 1202
Thanks, I've tried the PCI-E connectors and still the same problem. I've now set up the other miner and I can't get either one to mine. Under "Miner Status" it just shows all empty readings and says "This section contains no values yet" From what I've read it's a DNS issue, are you able to instruct me how to rectify this and where to place the DNS values? I'm a bit of a noob at this and would appreciate the help Smiley
hero member
Activity: 784
Merit: 504
Just got my two S3's today! Setting up one however and ran into a problem, one chain is hashing away fine with oooooooo oooooooo but the other comes back with -------- -------- -------- -------o

What the hell does this mean?!? It worked ok on first run, restarted the machine and it's been doing it since. Any ideas?

Have you tried swapping PCI power connectors? Hope you have done it.
Then if not working, Open your faulty antminer S3 and swap the cables from blades to control panel.
You can also swap the control board of another working S3 for testing as a second option.
If now the other blades are working its a control panel or cable problem.

Now, open the front side (ASIC Chip side)heatsink and check for thermal paste lease or absence.
If its so, just buy some good thermal grease and apply, the blade will be ok.
Else its a clear case of RMA. Contact bitmaintech as soon as possible via email.
I assumed you are using a proper power supply.
legendary
Activity: 1235
Merit: 1202
Just got my two S3's today! Setting up one however and ran into a problem, one chain is hashing away fine with oooooooo oooooooo but the other comes back with -------- -------- -------- -------o

What the hell does this mean?!? It worked ok on first run, restarted the machine and it's been doing it since. Any ideas?
Jump to: