|
what do you see on the status page when you log into the web gui? What does your pool report as far as hash rate of your Antminers goes? You can use the Antminer Monitor developed by mdude7 to get a view of all of your antminers. All the above matter much more that which LED is flashing. (on my Ants, the green LED on the ASIC boards are all flashing very rapidly).
|
|
|
|
i reset only one first, with the small button, and it still doesnt work. just slow blinking green light.
After the reset - did you try to login on the factory IP (listed on the sticker in front of the Ant)? Can you do the login with a PC or laptop which is not connected to your router, ideally with a crossover ethernet cable (or using a switch/hub, but without the router)? (this is to rule out the issue that there is some conflict with the IP range or other devices). good luck |
|
|
|
|
When you reset them, you should probably do it one at a time, if you do 2 or more, they are all reset to the same factory default IP address (usually 192.168.1.99), and you get a conflict. Reset one, connect just this device to your network and try to access its gui (now at the factory default IP address, which hopefully is within your routers address space).
When you get this fixed, perhaps you should change your default password, just in case someone hacked your miners.
Cheers
|
|
|
|
|
The Ant has a WAN and a LAN interface. These seem to use the same RJ45 connector. It looks like these cannot be both on the same subnet. The interface that I've been using is the WAN. I think that you can ignore the LAN and simply use the WAN. It would be an advantage to leave it as a fixed IP (so it won't suffer from DHCP lease expiry). If you can still connect to the gui, change the WAN to a free fixed IP in your router's range. After the change you'll need to login to the gui on the revised IP address. Make sure that all of your pool credentials are 100% correct. You need to be patient when you turn the Antminer on, until it starts mining. You can click repeatedly on the 'status' tab on the web gui to refresh the display. I hope that this fixes it for you.
|
|
|
|
Anyone else having trouble with recent S1 units? I have 1 out of 3 units giving me problems and bitmaintech is making me go through hoops to get anything resolved!!!  Your first pool is dead. To get rid of X-try to reboot by going into system and reboot without shutting the power off. it helps on mine. Your hashing speed is ~ correct with 5/64 asics not functioning (you are ~7% off in speed as expected). 7% off is still better than to send the miner back. Good luck. First pool is dead because that is how it work on betarigs to rent your rig  I agree that if I have to pay to ship it back and be down for a week with no rig it doesn't make sense but you pay for 180 ghs they should give you 180ghs. If they need to send a replacement board thats on them not my problem. It is brand new!! I did try the reboot with no power off, sometimes it give me more X's sometimes less. somtimes a whole board doesn't come online. There is no question this unit is defective! There just needs to be a solution from bitmain on what to do about it. you might consider adding some additional cooling ?? try adding heatsinks to the chips and/or adding an additional fan. you should be able to drop the temps to about 39 and 40 if you do that and maybe those chips will stop overheating . Need better PSU? i think those x's indicate chips overheating and that will cause a slowdown in hashrate .. your temps are not bad but i think u have some chips overheating. i seen same thing on some mine and that is what helped them stop getting x's .. sometimes x's are ok but when accompanied with slowdown of hashrate then i think chips are overheating. Make sure that all the screws holding the boards to the heatsinks are fully screwed in (just finger tight). I had quite a few that could use another turn or half a turn. Replace your PSU with one proven to work correctly with the Ants. If the x's persist, try to reset from the GUI. If that doesn't work, try different clock speeds (both lower and higher), each Ant has its own 'personality'.... I don't think that you are overheating, but local over temp because of poor heat conduction to some ASICS could be your enemy. Cheers |
|
|
|
One Year Later
It's been a year since I began this experiment. In that time I have spent about AUD$2500 for a current balance of 0.67 BTC plus an Antminer S1 mining at 180GH/s. Difficulty has risen from 15 million to 10 billion. The current blockchain on my PC is 20GB (didn't check when I started). Bitcoins have risen from AUD$130 each to AUD$700 each, peaking at over AUD$1200. I have invested and reinvested 5 times. I have solved at least one block. I've had a lot of fun, a lot of frustration, and gained a whole lot of knowledge. You'd have to say that as an investment this has failed completely, but as a learning experience it has been worth it. Rather than speculating, I put up the cash to find out for sure whether this was worth doing. I haven't solicited any donations -- only technical assistance running my rig.
Funnily enough, I really haven't spent my bitcoins on anything besides mining hardware! I don't plan to cash out to fiat, but rather to save the BTC for future online services.
Enjoy the journey and experience  Similar tale here, started out of curiosity with GPU's, transitioned to USB based ASICs (my BE's are still hashing!), then a variety of other miners, including a few S1's. Peaked at about 1.6 TH/sec. Can't say that there was any financial gain (to the contrary), and most of my earned BTC was spent on mining hardware too. No, did not find any blocks yet... Cheers |
|
|
|
|
Looks like Eligius is down, and we are carrying some of their backups, now at 3568178.052 Ghash/s
|
|
|
|
|
What is the address space of your router? The antminer probably needs to be within the range supported by your router, otherwise it may not be routed to due to the firewall/NAT. Check what is the address of your router (192.168.1.1 is common, and that would work with 192.168.1.99 for the Antminer). Check what is the range of addresses that it supports.
Also the IP of the Antminer should not clash with any existing device on your network (that's why the starting choice of .99 is a clever one...). The easy way to resolve this is to 'pre-alocate' an IP address in your router.
If for security you are using a MAC filter in the router, of course you need to add the Antminer mac address to the 'permitted list' if that's how you configured it.
Some lazy people try to use DHCP, without considering the pitfalls. I recommend to stay with fixed IP, so you don't run into issues of DHCP lease expiry.
Cheers
|
|
|
|
Repeating the same rant again, my confirmed reward has been above the threshold for some hours, but payment is not happening. Ticket raised with Slush support.
Payment made. All good now. Thanks Slush Support! Cheers Highly unlikely support did anything for you... If you really get this nuts over late payouts, you should def throw your miners on Eligius for a month... 4+ days of no payouts happening repeatedly will teach you how much to embrace the consistency of payouts here... At least I get the good feeling that raising a support ticket helped fix it.... As the payout process is supposed to be automated, when it doesn't happen something in the process needs to be fixed, or an alert raised for 'human intervention'. It's good to know that it could be even worse.... Cheers |
|
|
|
If you just want to monitor it locally, you could try AntMiner Monitor (see https://bitcointalk.org/index.php?topic=596178.0). This provides periodically an update of your S1 status, it is especially useful if you have a few Antminers. There have been cases of Antminers being 'hijacked' to mine for others, so you should be cautious (first and easy step is to modify the password from the default 'root'). Cheers |
|
|
|
|
I did not try the wifi on the S1, but have used one over a powerline adapter. It is probably a better solution than wifi.
Cheers
|
|
|
|
That's not what he asked. Usual terminology is W/GH, which is up to 1.2 or so if you downclock them loads.
Alrighty. I thought 393.95/470 = 0.84GH/W is what he was looking for. The '393.95' in your reply is probably the clock speed in MHz, this is not the hash rate (which is about 200 GH/s for that clock speed). So the efficiency is 470/200 W/(GH/s) which is 2.35 W/(GH/s), a rather poor value. |
|
|
|
just got my 8 miners from bitmain... super quick shipping as advertised... i did notice you can set up 3 pools on each miner would that reduce the hashing power per pool if you had 3 configured on each miner or would it be the same 1.44 TH/s for all 3 pools?
While originally the S1 pool entry is for 'fail-over' only, there is a way to make it support 'load balancing' where you divide your hash power between the pools (see https://bitcointalk.org/index.php?topic=578276.0) Cheers |
|
|
|
Repeating the same rant again, my confirmed reward has been above the threshold for some hours, but payment is not happening. Ticket raised with Slush support.
Payment made. All good now. Thanks Slush Support! Cheers |
|
|
|
|
Where in the world are you?
|
|
|
|
72GB/S BFL.....I HAVE ON AND OFF BEEN MINING SLUSHES....but it said I had shareson my account but on each block found, no shares...and nothing registered the whole time either
Log into your account at Slush, check that your worker credentials are EXACTLY what you entered into your miner. Check that the pool IP address is entered correctly into your miner. Look at your Account page, confirm that this particular miner is reported as hashing: in the Workers area check the entries for Current shares Score Last share at Mhash/s* of this particular miner. If you don't get anything there, you won't get any credit/reward for your efforts. Check your miner's display and confirm that your shares are accepted by the pool. Note also that Slush has a unique 'anti hopping' algorithm, that gives full weight to the shares contributed towards the end of the block. If you paused mining a few minutes before the end of a solved block, your reward may suffer badly (on the other hand, if you joined a block late, but stayed till the end, you'll get almost full reward based on your proportional contribution). Cheers |
|
|
|
If your pool setting is missing or incorrect, it will not hash, so the fan will not run (as it the temp will stay low, no reason for the fan to turn). Check if it's hashing through the web gui (status, Miner Status). It takes a while to start hashing from a cold start, so be patient. Read the guides such as https://bitcointalk.org/index.php?topic=355387, it's just a bit more involved than turning the power switch on:) Good luck |
|
|
|
|
Repeating the same rant again, my confirmed reward has been above the threshold for some hours, but payment is not happening. Ticket raised with Slush support.
|
|
|
|
Some of the Ants here had loose screws holding the printed circuit boards to the heatsinks. Others had excessive amounts of thermal paste (and loose screws). Get the right size Allen key, and gently check all those screws (in particular, the one at the center of the boards). If you find any that are loose, tighten it to 'finger tightness', don't over-do it. Tightening any loose screws will also 'squeeze' out some of the excessive thermal paste, which can be simply wiped away with some tissue paper. There is a single temperature sensor per blade, in the center, so if one of the printed-circuit boards that is far from the sensor was not attached properly (loose screw(s) and way too much thermal paste), the ASICS that suffer from over-heating due to poor thermal conduction may go into thermal shutdown or simply display excessive errors due to this 'local' high temperature which is not seen by the sensor that is too far from that area. If this doesn't help: Try swapping the power supply with one from the 'good' Ants - maybe there is marginal performance or current capacity. The next thing to try is a different clock speed. My impression is that every Ant is different, some 'like' higher clocks and some 'prefer' lower settings. Try changing this in small steps, with at least 10 minutes before things settle down and you get a representative reading. You should consider the hash rates, HW error % and power consumption, together with the X's. Look at the overclocking thread https://bitcointalk.org/index.php?topic=348327.40 or other guides for instructions how to change the S1's frequency settings. Good luck |
|
|
|
|
Show Posts
