[Setup & Troubleshoot] Bitmain AntMiner S1 180GH/S miner

[samsonn25]

bitcoin-cloud.me is sell mining by the TH now

We used to have a bit of a bad record and we miss treated some customers , but we are back to stay

We are now china's largest mining farm

great prices and high quality hardware

if you ordered from us in the past and never got your order just contact us

sales@bitcoin-cloud.me

Sounds like the CLOUD MINING is too good to be true.  Actually its impossible even if they can steal electricity for FREE.

The company loses -400% on 10TH deal, etc.  -600% on 50TH  -1000% on 500Th deals.

[bigbitmine]

Ok, this one is doing my head in.  How can I find the API port for the S1.  I'm using S3's as well and they were all 4028.  I've heard of some SSH wizardry to get into the miner but I'm not technical enough.  Does anyone know the easy way to see what port it uses?

[Zorg33]

1st thing in my mind.... PSU  

Please make sure you are using a PSU with 2 +12v rails and each PCI-E cable is coming from it's own rail.  (Not 2 PCI-E connectors from 1 cable)

If the above is not the case, if you feel confortable unscrewing the hashing PCB on the network port side and other hashing pcb and swap it.  Then turn on the antminer with 1 blade only.  If it still shows many XXXXX then, it's time for the RMA to get a replacement Hashing PCB

Just got an S1 in today and hooked up. I have a section of ASIC status all xxxxxxxx and only running 156 Gh/s(avg).  I switched the PCI-e cables around and still the same. Upon further inspection I noted that the RF led is not a steady flashing rate on one of the blades.  Only flashes a couple times every other second or so. Definitely not behaving like the RF led on the other blade. Anything I can take a look at?

easiest way to check is to measure the voltage with a multimeter across the two legs of the inductor (grey cube above the faulting 8 chips). You should pick up a voltage of 1.1V - If this voltage is not present it means those chips have no power. I had a similar issue with my second batch antminer but it was the first 'segment' on the board that had no voltage, thus none of the 32 chips on the side worked. Bitmain was very good at shipping me a replacement PCB

Thank you for the tip. I measured voltages at various points and these are my findings:

Red: 11.56V so juice is definitely getting into the board.
Yellow: 1.1V is present here
Green: this capacitor is supposed to be around 12V, right? Yet it measures much lower and the voltage is dropping as I measure it.



Can you recommend if this can be fixed by me: a have a mobile phone repair guy, who is very good at soldering, so if I can replace something then I'd rather fix it myself.
Or if it is not easily replaceable then I would rather have a small refund as only 50GH/s are not working, which is 28% of the miner.

My immediate impression is that your 12V DC power is far too low. Equipment will not handle well outside of a 11.7-12.4V range and it is almost certainly your PSU being a bit too weak for the job, or running long 18AWG cables that are losing voltage across the distance (partially as the cables getting warm).

I *imagine* that the all 3 capacitors should act the same way when tested - its possible that one might be poor quality and shorting/draining when tested with the meter.

2ND THOUGHT: I am not sure how the power is given from the 12V in to the 4 'segments', but if it is a chain across the the 3 capacitors in a rightward direction the capacitor could be broken and the multimeter is causing the connection to complete, but designed not to carry the required amperage through its probes -> hence voltage drops without a valid circuit. I am not an electrical engineer though, so a 2nd opinion would be a good idea before you take the soldering iron to it. If it is the capacitor, it would be a very easy fix if your friend has the tools for fire-point soldering and some experience with phones. (I personally have only a larger iron so I would not attempt a smaller component like that without buying a new tool or two)

By the way, which section is the one showing all x's? The second one I imagine?

Hi,
I know it's a bit too late, but I faced the same problem today with my S1.
Eventually a buyer came to pick up the miner from me, it's been already paid, when we noticed that only one of the blades was working.
I've given back the money and started looking for what's causing the problem.
The LED on the secondary blade was only blinking slowly and it was totally cold and it did not show up on the web UI at all.
I previously did a voltage mod on the unit, so I started to look around R3.
I also had the same measurement results as Cyper had above.
Noticed that the resistance was about twice on R3 than it should be, sth about 9.6k.
Looking at the resistance values around (R12, etc) I figured out that R3 must be fully open, like it's burnt or something.
So I took off R3 and guess what, it showed infinite resistance. Somehow it was slowly getting burnt out in the past few weeks, without any external influence to the point today when finally the blade wasn't able to work at all.
I replaced it with a 10k pot, adjusted it to match the resistance of the other seven and now it's working alright.

So, if your miner breaks down like that, start investigating around R3 and so on. If it's a second hand S1, the previous owner might have had it undervolted and damaged the resistors, that began slowly degrading.

I hope that helps someone.

[Convicted2008]

Here's the issue Im having. I have reset the miner, downloaded the ip scanner, tried the ip address listed on the miner at least 10x each now with no luck. I can't get into the properties of the miner. The green light just flashes and the red light stays it. What should I do from here?

[MrTeal]

Here's the issue Im having. I have reset the miner, downloaded the ip scanner, tried the ip address listed on the miner at least 10x each now with no luck. I can't get into the properties of the miner. The green light just flashes and the red light stays it. What should I do from here?

Is your network subnet the same as the miner?

[SammyD1st]

Hello,

Another noob here with a problem getting my S1 working.  I hope this is the right place to post.

I got my third S1 off ebay recently, and while the first two worked just fine, I can't seem to get this one to actually hash.

Here are some screenshots: http://imgur.com/a/mhioo

The top two are with a first power source, and then I swapped the PSU to one that was successfully powering one of my other S1s with no problem... but this one still didn't work.

Basically, it never shows any appreciable hashing... and the power load keeps fluctuating as shown.

I can't seem to figure it out, so any help is much appreciated!

 - Sam

[sushi]

Hi Sam,

If you could, pleaes power off the S1, then turn it back on.  Wait for about 4 minutes, then could you please copy and paste the entire SYSTEM LOG for S1?

if  you could, lets test the S1 control PCB first.  Remove the S1 control PCB and place it on the working S1 and see if it hashes.

If the control PCB is good, then remove one of the questionable hashing PCB and connect it to the known working S1, and see if it hashes. 

Repeat 1 more time with the other PCB.

If any of them shows problem, then you 'll know it is the damaged item.  Contact the seller and ask for exchange or refund. 

Hello,

Another noob here with a problem getting my S1 working.  I hope this is the right place to post.

I got my third S1 off ebay recently, and while the first two worked just fine, I can't seem to get this one to actually hash.

Here are some screenshots: http://imgur.com/a/mhioo

The top two are with a first power source, and then I swapped the PSU to one that was successfully powering one of my other S1s with no problem... but this one still didn't work.

Basically, it never shows any appreciable hashing... and the power load keeps fluctuating as shown.

I can't seem to figure it out, so any help is much appreciated!

 - Sam

[SammyD1st]

Hi Sam,

If you could, pleaes power off the S1, then turn it back on.  Wait for about 4 minutes, then could you please copy and paste the entire SYSTEM LOG for S1?

if  you could, lets test the S1 control PCB first.  Remove the S1 control PCB and place it on the working S1 and see if it hashes.

If the control PCB is good, then remove one of the questionable hashing PCB and connect it to the known working S1, and see if it hashes. 

Repeat 1 more time with the other PCB.

If any of them shows problem, then you 'll know it is the damaged item.  Contact the seller and ask for exchange or refund. 

Thank you for your help!

Here is the log, forgive me if my formatting gets messed up:

Fri Oct 31 23:42:43 2014 daemon.info sysinit: ntpd: reply from 66.96.110.10: reach 0x03 offset 14407633.443324 delay 28815266.977488 status 0x24 strat 2 refid 0x84a30466 rootdelay 0.051240
Fri Oct 31 23:42:43 2014 daemon.info sysinit: ntpd: sent query to 167.88.119.29
Fri Oct 31 23:42:43 2014 daemon.info sysinit: ntpd: sent query to 50.7.96.4
Fri Oct 31 23:42:43 2014 daemon.info sysinit: ntpd: sent query to 69.129.251.133
Fri Oct 31 23:42:43 2014 daemon.info sysinit: ntpd: reply from 167.88.119.29: reach 0x07 offset 0.037790 delay 0.143149 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.033433
Fri Oct 31 23:42:43 2014 daemon.info sysinit: ntpd: reply from 69.129.251.133: reach 0x07 offset 0.038443 delay 0.145786 status 0x1c strat 2 refid 0xd8a581f4 rootdelay 0.020783
Fri Oct 31 23:42:43 2014 daemon.info sysinit: ntpd: reply from 50.7.96.4: reach 0x07 offset 0.050167 delay 0.147852 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.033005
Fri Oct 31 23:42:44 2014 daemon.info sysinit: ntpd: sent query to 66.96.110.10
Fri Oct 31 23:42:44 2014 daemon.info sysinit: ntpd: sent query to 167.88.119.29
Fri Oct 31 23:42:44 2014 daemon.info sysinit: ntpd: sent query to 50.7.96.4
Fri Oct 31 23:42:44 2014 daemon.info sysinit: ntpd: reply from 50.7.96.4: reach 0x0f offset 0.011424 delay 0.070260 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.033005
Fri Oct 31 23:42:44 2014 daemon.info sysinit: ntpd: reply from 167.88.119.29: reach 0x0f offset 0.002501 delay 0.073467 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.033433
Fri Oct 31 23:42:44 2014 daemon.info sysinit: ntpd: reply from 66.96.110.10: reach 0x07 offset 0.020424 delay 0.131780 status 0x24 strat 2 refid 0x84a30466 rootdelay 0.051240
Fri Oct 31 23:42:45 2014 daemon.info sysinit: ntpd: sent query to 66.96.110.10
Fri Oct 31 23:42:45 2014 daemon.info sysinit: ntpd: sent query to 167.88.119.29
Fri Oct 31 23:42:45 2014 daemon.info sysinit: ntpd: sent query to 69.129.251.133
Fri Oct 31 23:42:45 2014 daemon.info sysinit: ntpd: reply from 69.129.251.133: reach 0x0f offset 0.037427 delay 0.144237 status 0x1c strat 2 refid 0xd8a581f4 rootdelay 0.020783
Fri Oct 31 23:42:45 2014 daemon.info sysinit: ntpd: reply from 167.88.119.29: reach 0x1f offset 0.038108 delay 0.145439 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.033433
Fri Oct 31 23:42:45 2014 daemon.info sysinit: ntpd: reply from 66.96.110.10: reach 0x0f offset 0.059910 delay 0.211467 status 0x24 strat 2 refid 0x84a30466 rootdelay 0.051240
Fri Oct 31 23:42:46 2014 daemon.info sysinit: ntpd: sent query to 66.96.110.10
Fri Oct 31 23:42:46 2014 daemon.info sysinit: ntpd: sent query to 50.7.96.4
Fri Oct 31 23:42:46 2014 daemon.info sysinit: ntpd: sent query to 69.129.251.133
Fri Oct 31 23:42:47 2014 daemon.info sysinit: ntpd: reply from 50.7.96.4: reach 0x1f offset 0.050978 delay 0.149475 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.033005
Fri Oct 31 23:42:47 2014 daemon.info sysinit: ntpd: reply from 69.129.251.133: reach 0x1f offset 0.041368 delay 0.151829 status 0x1c strat 2 refid 0xd8a581f4 rootdelay 0.020783
Fri Oct 31 23:42:47 2014 daemon.info sysinit: ntpd: reply from 66.96.110.10: reach 0x1f offset 0.061439 delay 0.213955 status 0x24 strat 2 refid 0x84a30466 rootdelay 0.051240
Fri Oct 31 23:42:48 2014 daemon.info sysinit: ntpd: sent query to 167.88.119.29
Fri Oct 31 23:42:48 2014 daemon.info sysinit: ntpd: reply from 167.88.119.29: reach 0x3f offset 0.000036 delay 0.067676 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.033433
Fri Oct 31 23:42:49 2014 daemon.info sysinit: ntpd: sent query to 66.96.110.10
Fri Oct 31 23:42:49 2014 daemon.info sysinit: ntpd: sent query to 50.7.96.4
Fri Oct 31 23:42:49 2014 daemon.info sysinit: ntpd: sent query to 69.129.251.133
Fri Oct 31 23:42:49 2014 daemon.info sysinit: ntpd: reply from 69.129.251.133: reach 0x3f offset 0.001520 delay 0.072516 status 0x1c strat 2 refid 0xd8a581f4 rootdelay 0.020783
Fri Oct 31 23:42:49 2014 daemon.info sysinit: ntpd: reply from 66.96.110.10: reach 0x3f offset 0.005716 delay 0.102107 status 0x24 strat 2 refid 0x84a30466 rootdelay 0.051240
Fri Oct 31 23:42:50 2014 daemon.info sysinit: ntpd: sent query to 66.96.110.10
Fri Oct 31 23:42:50 2014 daemon.info sysinit: ntpd: sent query to 167.88.119.29
Fri Oct 31 23:42:50 2014 daemon.info sysinit: ntpd: sent query to 69.129.251.133
Fri Oct 31 23:42:50 2014 daemon.info sysinit: ntpd: reply from 167.88.119.29: reach 0x7f offset -0.000187 delay 0.068080 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.033433
Fri Oct 31 23:42:50 2014 daemon.info sysinit: ntpd: reply from 69.129.251.133: reach 0x7f offset 0.000072 delay 0.069366 status 0x1c strat 2 refid 0xd8a581f4 rootdelay 0.020783
Fri Oct 31 23:42:50 2014 daemon.info sysinit: ntpd: reply from 66.96.110.10: reach 0x7f offset 0.014674 delay 0.121912 status 0x24 strat 2 refid 0x84a30466 rootdelay 0.051240
Fri Oct 31 23:42:51 2014 daemon.info sysinit: ntpd: sent query to 66.96.110.10
Fri Oct 31 23:42:51 2014 daemon.info sysinit: ntpd: sent query to 69.129.251.133
Fri Oct 31 23:42:51 2014 daemon.info sysinit: ntpd: reply from 69.129.251.133: reach 0xff offset 0.004262 delay 0.079028 status 0x1c strat 2 refid 0xd8a581f4 rootdelay 0.020783
Fri Oct 31 23:42:51 2014 daemon.info sysinit: ntpd: reply from 66.96.110.10: reach 0xff offset 0.004371 delay 0.100585 status 0x24 strat 2 refid 0x84a30466 rootdelay 0.051240
Fri Oct 31 23:42:52 2014 daemon.info sysinit: ntpd: sent query to 167.88.119.29
Fri Oct 31 23:42:52 2014 daemon.info sysinit: ntpd: sent query to 69.129.251.133
Fri Oct 31 23:42:52 2014 daemon.info sysinit: ntpd: reply from 167.88.119.29: reach 0xff offset -0.000341 delay 0.067839 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.033433
Fri Oct 31 23:42:52 2014 daemon.info sysinit: ntpd: reply from 69.129.251.133: reach 0xff offset 0.001703 delay 0.073064 status 0x1c strat 2 refid 0xd8a581f4 rootdelay 0.020783
Fri Oct 31 23:42:53 2014 daemon.info sysinit: ntpd: sent query to 66.96.110.10
Fri Oct 31 23:42:53 2014 daemon.info sysinit: ntpd: sent query to 69.129.251.133
Fri Oct 31 23:42:53 2014 daemon.info sysinit: ntpd: reply from 66.96.110.10: reach 0xff offset -0.008238 delay 0.099507 status 0x24 strat 2 refid 0x84a30466 rootdelay 0.051240
Fri Oct 31 23:42:53 2014 daemon.info sysinit: ntpd: reply from 69.129.251.133: reach 0xff offset -0.009065 delay 0.099674 status 0x1c strat 2 refid 0xd8a581f4 rootdelay 0.020783
Fri Oct 31 23:42:53 2014 daemon.info sysinit: --bitmain-options 115200:32:8:40:350:4d81 -o stratum.btcguild.com:3333 -O SammyD1st_4:123456 --api-listen --api-network
Fri Oct 31 23:42:53 2014 daemon.info sysinit: - init complete -
Fri Oct 31 23:43:27 2014 cron.err crond[575]: time disparity of 480255 minutes detected
Fri Oct 31 23:45:01 2014 cron.info crond[575]: crond: USER root pid 899 cmd /usr/bin/cgminer-monitor

By that time in the log, the problem had already occurred (no hashing, hardware fault "XXX"s)

Otherwise, I'm not sure I want to start taking several of my S1s apart.  Whether the control board or the hashing board is broken on this one, either way I'm going to return it.  I was just hoping that maybe there was a fix.

Thank you!

 - Sam

[gaalx]

Hello. I have es1. periodically reduces the rate of almost 2 times, you can somehow programmatically overload Asik, if speed is less than a certain value, or every 3-4 hours? thanks.

[MyRig]

SSH into the S1,

then please edit /etc/init.d/cgminer file

comment out the whole IF statement near the end of the file with the last line "fi"

vi cgminer

then press "i" to enter the edit mode

Place "#" in front of each line.

then press "Escape", ":" "wq" then "Enter"

Please login to the control panel, then go to the "System" tab, and uncheck Time Sync

then hit "Save & Apply" will fix this issue

Hi Sam,

If you could, pleaes power off the S1, then turn it back on.  Wait for about 4 minutes, then could you please copy and paste the entire SYSTEM LOG for S1?

if  you could, lets test the S1 control PCB first.  Remove the S1 control PCB and place it on the working S1 and see if it hashes.

If the control PCB is good, then remove one of the questionable hashing PCB and connect it to the known working S1, and see if it hashes. 

Repeat 1 more time with the other PCB.

If any of them shows problem, then you 'll know it is the damaged item.  Contact the seller and ask for exchange or refund. 

Thank you for your help!

Here is the log, forgive me if my formatting gets messed up:

Fri Oct 31 23:42:43 2014 daemon.info sysinit: ntpd: reply from 66.96.110.10: reach 0x03 offset 14407633.443324 delay 28815266.977488 status 0x24 strat 2 refid 0x84a30466 rootdelay 0.051240
Fri Oct 31 23:42:43 2014 daemon.info sysinit: ntpd: sent query to 167.88.119.29
Fri Oct 31 23:42:43 2014 daemon.info sysinit: ntpd: sent query to 50.7.96.4
Fri Oct 31 23:42:43 2014 daemon.info sysinit: ntpd: sent query to 69.129.251.133
Fri Oct 31 23:42:43 2014 daemon.info sysinit: ntpd: reply from 167.88.119.29: reach 0x07 offset 0.037790 delay 0.143149 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.033433
Fri Oct 31 23:42:43 2014 daemon.info sysinit: ntpd: reply from 69.129.251.133: reach 0x07 offset 0.038443 delay 0.145786 status 0x1c strat 2 refid 0xd8a581f4 rootdelay 0.020783
Fri Oct 31 23:42:43 2014 daemon.info sysinit: ntpd: reply from 50.7.96.4: reach 0x07 offset 0.050167 delay 0.147852 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.033005
Fri Oct 31 23:42:44 2014 daemon.info sysinit: ntpd: sent query to 66.96.110.10
Fri Oct 31 23:42:44 2014 daemon.info sysinit: ntpd: sent query to 167.88.119.29
Fri Oct 31 23:42:44 2014 daemon.info sysinit: ntpd: sent query to 50.7.96.4
Fri Oct 31 23:42:44 2014 daemon.info sysinit: ntpd: reply from 50.7.96.4: reach 0x0f offset 0.011424 delay 0.070260 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.033005
Fri Oct 31 23:42:44 2014 daemon.info sysinit: ntpd: reply from 167.88.119.29: reach 0x0f offset 0.002501 delay 0.073467 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.033433
Fri Oct 31 23:42:44 2014 daemon.info sysinit: ntpd: reply from 66.96.110.10: reach 0x07 offset 0.020424 delay 0.131780 status 0x24 strat 2 refid 0x84a30466 rootdelay 0.051240
Fri Oct 31 23:42:45 2014 daemon.info sysinit: ntpd: sent query to 66.96.110.10
Fri Oct 31 23:42:45 2014 daemon.info sysinit: ntpd: sent query to 167.88.119.29
Fri Oct 31 23:42:45 2014 daemon.info sysinit: ntpd: sent query to 69.129.251.133
Fri Oct 31 23:42:45 2014 daemon.info sysinit: ntpd: reply from 69.129.251.133: reach 0x0f offset 0.037427 delay 0.144237 status 0x1c strat 2 refid 0xd8a581f4 rootdelay 0.020783
Fri Oct 31 23:42:45 2014 daemon.info sysinit: ntpd: reply from 167.88.119.29: reach 0x1f offset 0.038108 delay 0.145439 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.033433
Fri Oct 31 23:42:45 2014 daemon.info sysinit: ntpd: reply from 66.96.110.10: reach 0x0f offset 0.059910 delay 0.211467 status 0x24 strat 2 refid 0x84a30466 rootdelay 0.051240
Fri Oct 31 23:42:46 2014 daemon.info sysinit: ntpd: sent query to 66.96.110.10
Fri Oct 31 23:42:46 2014 daemon.info sysinit: ntpd: sent query to 50.7.96.4
Fri Oct 31 23:42:46 2014 daemon.info sysinit: ntpd: sent query to 69.129.251.133
Fri Oct 31 23:42:47 2014 daemon.info sysinit: ntpd: reply from 50.7.96.4: reach 0x1f offset 0.050978 delay 0.149475 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.033005
Fri Oct 31 23:42:47 2014 daemon.info sysinit: ntpd: reply from 69.129.251.133: reach 0x1f offset 0.041368 delay 0.151829 status 0x1c strat 2 refid 0xd8a581f4 rootdelay 0.020783
Fri Oct 31 23:42:47 2014 daemon.info sysinit: ntpd: reply from 66.96.110.10: reach 0x1f offset 0.061439 delay 0.213955 status 0x24 strat 2 refid 0x84a30466 rootdelay 0.051240
Fri Oct 31 23:42:48 2014 daemon.info sysinit: ntpd: sent query to 167.88.119.29
Fri Oct 31 23:42:48 2014 daemon.info sysinit: ntpd: reply from 167.88.119.29: reach 0x3f offset 0.000036 delay 0.067676 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.033433
Fri Oct 31 23:42:49 2014 daemon.info sysinit: ntpd: sent query to 66.96.110.10
Fri Oct 31 23:42:49 2014 daemon.info sysinit: ntpd: sent query to 50.7.96.4
Fri Oct 31 23:42:49 2014 daemon.info sysinit: ntpd: sent query to 69.129.251.133
Fri Oct 31 23:42:49 2014 daemon.info sysinit: ntpd: reply from 69.129.251.133: reach 0x3f offset 0.001520 delay 0.072516 status 0x1c strat 2 refid 0xd8a581f4 rootdelay 0.020783
Fri Oct 31 23:42:49 2014 daemon.info sysinit: ntpd: reply from 66.96.110.10: reach 0x3f offset 0.005716 delay 0.102107 status 0x24 strat 2 refid 0x84a30466 rootdelay 0.051240
Fri Oct 31 23:42:50 2014 daemon.info sysinit: ntpd: sent query to 66.96.110.10
Fri Oct 31 23:42:50 2014 daemon.info sysinit: ntpd: sent query to 167.88.119.29
Fri Oct 31 23:42:50 2014 daemon.info sysinit: ntpd: sent query to 69.129.251.133
Fri Oct 31 23:42:50 2014 daemon.info sysinit: ntpd: reply from 167.88.119.29: reach 0x7f offset -0.000187 delay 0.068080 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.033433
Fri Oct 31 23:42:50 2014 daemon.info sysinit: ntpd: reply from 69.129.251.133: reach 0x7f offset 0.000072 delay 0.069366 status 0x1c strat 2 refid 0xd8a581f4 rootdelay 0.020783
Fri Oct 31 23:42:50 2014 daemon.info sysinit: ntpd: reply from 66.96.110.10: reach 0x7f offset 0.014674 delay 0.121912 status 0x24 strat 2 refid 0x84a30466 rootdelay 0.051240
Fri Oct 31 23:42:51 2014 daemon.info sysinit: ntpd: sent query to 66.96.110.10
Fri Oct 31 23:42:51 2014 daemon.info sysinit: ntpd: sent query to 69.129.251.133
Fri Oct 31 23:42:51 2014 daemon.info sysinit: ntpd: reply from 69.129.251.133: reach 0xff offset 0.004262 delay 0.079028 status 0x1c strat 2 refid 0xd8a581f4 rootdelay 0.020783
Fri Oct 31 23:42:51 2014 daemon.info sysinit: ntpd: reply from 66.96.110.10: reach 0xff offset 0.004371 delay 0.100585 status 0x24 strat 2 refid 0x84a30466 rootdelay 0.051240
Fri Oct 31 23:42:52 2014 daemon.info sysinit: ntpd: sent query to 167.88.119.29
Fri Oct 31 23:42:52 2014 daemon.info sysinit: ntpd: sent query to 69.129.251.133
Fri Oct 31 23:42:52 2014 daemon.info sysinit: ntpd: reply from 167.88.119.29: reach 0xff offset -0.000341 delay 0.067839 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.033433
Fri Oct 31 23:42:52 2014 daemon.info sysinit: ntpd: reply from 69.129.251.133: reach 0xff offset 0.001703 delay 0.073064 status 0x1c strat 2 refid 0xd8a581f4 rootdelay 0.020783
Fri Oct 31 23:42:53 2014 daemon.info sysinit: ntpd: sent query to 66.96.110.10
Fri Oct 31 23:42:53 2014 daemon.info sysinit: ntpd: sent query to 69.129.251.133
Fri Oct 31 23:42:53 2014 daemon.info sysinit: ntpd: reply from 66.96.110.10: reach 0xff offset -0.008238 delay 0.099507 status 0x24 strat 2 refid 0x84a30466 rootdelay 0.051240
Fri Oct 31 23:42:53 2014 daemon.info sysinit: ntpd: reply from 69.129.251.133: reach 0xff offset -0.009065 delay 0.099674 status 0x1c strat 2 refid 0xd8a581f4 rootdelay 0.020783
Fri Oct 31 23:42:53 2014 daemon.info sysinit: --bitmain-options 115200:32:8:40:350:4d81 -o stratum.btcguild.com:3333 -O SammyD1st_4:123456 --api-listen --api-network
Fri Oct 31 23:42:53 2014 daemon.info sysinit: - init complete -
Fri Oct 31 23:43:27 2014 cron.err crond[575]: time disparity of 480255 minutes detected
Fri Oct 31 23:45:01 2014 cron.info crond[575]: crond: USER root pid 899 cmd /usr/bin/cgminer-monitor

By that time in the log, the problem had already occurred (no hashing, hardware fault "XXX"s)

Otherwise, I'm not sure I want to start taking several of my S1s apart.  Whether the control board or the hashing board is broken on this one, either way I'm going to return it.  I was just hoping that maybe there was a fix.

Thank you!

 - Sam

[dudee]

i have little problem with one fan. it runs 100% speed ~4000rpm 24/7
normal atx psu, it worked fine ~2000rpm ~45C
3 weeks ago i replaced psu with server psu and now only this one s1 runs fan 100%, i have them 3 others working fine.
last owner cut black and red and plug to molex, i dont remember why he did it.
i tryed resistor to make 7v or 9v, but with resistor it not even start spin. even if i unplug sensor wires from mb.
what i can do to get it lower speeds temp at max rpm 23-30C depends on the weather.

[SunnyIgor]

One of my undervolted pencil modded ants.
Gets 100% rejects or discards on some / most pools..
also I did some editing to get api acces
After that I tried to reset firware and update it and nothing worked.

 

[MarcinLodz]

Hello.

I have a big problem with my s1. After a power loss in my room i was unable to login into one of mine antminers s1. When i type an adress of ant i have

Bad Gateway
The process did not produce any response.

.

I just dont have the login site because of that error and thats why i cant do anything.

I tried restarting settings via button on mainboard to factory default and nothing chaNGED. I can connect via putty. I find that i should try /etc/init.d/uhttpd restart/start or other combination. Nothing works for me. Is there a way which i can try to do via putty to reset or upgrade the machine or to make it works once again ?

[hennessyhemp]

Anybody interested in my old S1 blades?  PM me.  We upgraded a few so we have blades minus fans, heatsinks, and controllers.  I'd let them go cheap...mostly just the shipping costs.

[gupik65]

Anybody interested in my old S1 blades?  PM me.  We upgraded a few so we have blades minus fans, heatsinks, and controllers.  I'd let them go cheap...mostly just the shipping costs.

You are all good to find out good

[ToQcHista]

jumper wire It is necessary?

[dsa0214]

Hello all, I've got my antminer s1 set up with a 700 watt server power supply. It powers up and appears to run fine. I've got my pool info set up in the miner configuration tab.

The problem is on the miner status tab, it's not showing any figures, just says 'no information to display yet' or something. Also, on my mining pool dashboard, I can see my little 2 ghs usb miner which is working fine, and a couple of times upon powering up the antminer, I'm seeing a spike in my hashrate, indicating that the antminer is connecting to the pool momentarily, just long enough to spike my hashrate way up.  This tells me I obviously have my pool info set up correctly in the antminer control panel.

Any ideas why it might be doing this, and how to tell if it's disconnecting from the pool, or just ceasing to hash? Kind of a noob here. Ok, MAJOR noob.

Thanks

[MyRig]

Please check the System Log and see if you don't have anything saying "NTPD"

Hello all, I've got my antminer s1 set up with a 700 watt server power supply. It powers up and appears to run fine. I've got my pool info set up in the miner configuration tab.

The problem is on the miner status tab, it's not showing any figures, just says 'no information to display yet' or something. Also, on my mining pool dashboard, I can see my little 2 ghs usb miner which is working fine, and a couple of times upon powering up the antminer, I'm seeing a spike in my hashrate, indicating that the antminer is connecting to the pool momentarily, just long enough to spike my hashrate way up.  This tells me I obviously have my pool info set up correctly in the antminer control panel.

Any ideas why it might be doing this, and how to tell if it's disconnecting from the pool, or just ceasing to hash? Kind of a noob here. Ok, MAJOR noob.

Thanks

[Vene]

Just to point one thing, maybe it was already written.
Pencilmoded Antminer S1 if connected to power meter or in the timer switch in 80% of the time it will show lots of xxxx on ASIC chips.
If connected directly to power source all ASICS will be fully working.
Tested with few S1 as well as few power supplies (high quality server power supplies).
Didn't try without pencil mod, maybe it works fine...

[CHILA]

hi, Someone pass me the latest update (cgminer) for the s1?, i have cgminer 3.8.5-1
Or anything else you can upgrade to improve performance?

TY