Since I last posted. I upgraded my power supplies. Added a new Antminer S1. Now that I have done that. The new one is running fine. The old one was running fine until I added the new one. I changed the address on them both so there would not be a conflict. I will call it antminer2 I can log in I can do everything. I have eth1 connected and and I have a wifi connection. But when I run a diagnostic. It times out. Any ideas?
It happend me once with 3 devices. I had to clear cookies of browser or use different browser to ssh. Iam not sure if it helps you but give it a shot
I tried that. Like I said. I can login and look at all the settings. I can run the graphs. I can change settings. It just will not mine. I ran the diagnostic. Ping return loss data. Route trace returns the address to my avalon miner and nslookup returns 78.24.191.177 openwrt.org It will let me go local on the network, just not on the internet.
Something else I have learned. I have two Avalon2 miners. One is running the other I am working on. When I shut down the Avalon2 miner. The last antminer s1 comes up and mines no problem. Not sure as to why. Anyone?
The blades seem to dropping like flies, lots of people are reporting similar problems. Web gui/ssh all fine, full interface access, but blades just stop firing up. Mine has died, and it was very well looked after. I thought it must be a faulty controller as both blades stopped at once, but I tried another controller and its definitely the blades. I've ask people to add posts here so we can keep track:
https://bitcointalk.org/index.php?topic=677110.0;topicseenI've asked Bitmain to chime in, but they haven't yet. Do we know anyone else with any electrical engineering knowledge of the S1 who could help us work out which component on the blades is failing? Any suggestions anyone?
Something I discovered this morning. Yesterday I got all 3 miners running. Sometime during the night I lost power. One miner came back up the other two didn't. They were running but not mining. I ran system log. Looked at the difference between the 3 miners. The one difference between the one running and the other two was this. /tmp/resolr.config.auto. The one running had an address of 192.168.1.1 the other two had an address of 192.168.1.101. The miners with the192.168.1.101 address will not mine. I did a reset not a reboot, on one miner. It can up and I did a system log and the address was 192.168.1.1 and it has started to mine. The last mine is not mining at the moment. It's system log is 192.168.1.101. Any idea? Is the resolr.config.auto corrupted? How to I see this file and or edit it? Any ideas?
Here is what I normally do when that happens....
Start from scratch, with a clear conscience and a clear mind.
1- Turn everything off - PSU, Internet, Your Computer (which you use to config your miners) and switch if you use one and/or router if you use one, then wait 3 minutes.
2- Turn on your internet and let it fully boot itself; if you have a router, turn it on next or your switch and finally your computer.
3- Wait about 1 minute (You want to take your time restarting during the day) for the network to get to idle (finish start up process)
4- Turn on one (or two) machines at a time; waiting until both are connected and mining before continuing.
5- If one machine don't mine and the rest do, perform a hard reset (button) on it - reconfigure as you know it. Make sure it's not an internet problem before!!
6- If a machine doesn't turn back on after a network-wide hard reset, you may need a new ECB, which are about $50, simply message Bitmain Tech. If none turn on, it's likely a network or internet issue.
I use a rather low subnet range (1.11,12,13,14,15) than most because no personal devices you buy in stores use that range and I have a few dozen internet connected devices in my lab aside from bitcoin miners. Some network experts around would recommend against using 192.168.1.1 as some router/modem manufacturers use 192.168.1.1 as default IP and they don't tell you often times. It's probably something stupid conflicting with your network. That's why many would say to start at .254 and work your way down. It could also be the ECB which isn't TOO bad, not as bad as changing a whole blade.
I had that same problem over a month ago.
I found adding a 24 port switch and changing my subnet/IP starting at 192.168.1.11 worked wonderfully.
If you screw around too much with the reset button, it will increase the risk of needing a new ECB which sucks when you need one.
That said the S3 upgrade kits should come out by moose hunting season I'd assume.
If the machine seems to mine but light always flashing, no matter what you do, order a new ECB, always handy to have a spare anyways.
Waiting a week for a replacement is agonizing