Is something up with IOC? Seems we are on an unexpectedly long block.
EDIT: pool hashrate on IOC seems to be dropping steadily as well. At least according to the website.
A lot of people have had rentals on it, just seem to be expiring at the same time as it hit Bittrex and difficulty has been going up so our block finding is down as a result. Did the difficulty go through the roof or something? It just doesn't seem right that I was making more than 50 of these a day up until 5.5 hours ago and now if we ever crack another block I will only get 2.3 coins. |
|
|
|
0 0,6,12,18 * * *
or
0 */6 * * *
both will run every 6 hours
Nice. Thanks. So does this mean every 3 minutes? */3 * * * * /usr/bin/cgminer-monitor |
|
|
|
In case anyone wants it I setup a batch file to reboot my miner. This can then be setup as a scheduled task. I am supposed to go on a weeks vacation and I honestly don't trust these things to maintain a hashrate for that long. Sometimes they are good for 24 hours or longer but eventually they always crash to sub 400 hashrate and require a reboot to recover. If you installed putty to SSH to your miner then you have plink so all you need is the batch file. Just adjust the IP as necessary. If you didn't install putty then you need to install it for this to work. set PATH=C:\Program Files (x86)\PuTTY;%PATH%
plink -ssh root@192.168.1.99 -pw root reboot
Why not just add a crontab entry? 0 0 * * * reboot I don't know how. EDIT: OK did a little crash course on google. Will this reboot every 6 hours? 0 0 * * * reboot 0 6 * * * reboot 0 12 * * * reboot 0 18 * * * reboot |
|
|
|
In case anyone wants it I setup a batch file to reboot my miner. This can then be setup as a scheduled task. I am supposed to go on a weeks vacation and I honestly don't trust these things to maintain a hashrate for that long. Sometimes they are good for 24 hours or longer but eventually they always crash to sub 400 hashrate and require a reboot to recover. If you installed putty to SSH to your miner then you have plink so all you need is the batch file. Just adjust the IP as necessary. If you didn't install putty then you need to install it for this to work. set PATH=C:\Program Files (x86)\PuTTY;%PATH%
plink -ssh root@192.168.1.99 -pw root reboot
|
|
|
|
|
Is something up with IOC? Seems we are on an unexpectedly long block.
EDIT: pool hashrate on IOC seems to be dropping steadily as well. At least according to the website.
|
|
|
|
how long is an estimated life span of an antminer s3?
how can anybody know this? it's a brand new product without almost any testing prior to shipment. they tested it for a a week....max The hardware should last longer than the hashrate will make it worth using. In other words, it should become unprofitable to use long before it breaks. |
|
|
|
|
Looks like Elite and USB were both scams and possibly concealcoin as well. What does this do to the potential of this place? I agree that many new coins are most profitable at their launch but I don't really want to be involved in mining coins that are full on scams designed to profit the devs at the expense of everyone else. Thoughts?
|
|
|
|
|
IOC says disabled on the home page where it lists the direct port but I see a lot of hashrate on it. Are people mining this successfully since the multi isn't moving off of USB?
|
|
|
|
Ugh. 10 hours in and Ant1 fell to 411Gh at 218 and Ant2 fell below 400Gh as expected. I wish Bitmaintech would include an option to auto-restart in the firmware. Thinking about creating a small cronjob to do just that...
try setting them to 212.5 freq your dc to dc convertor gets too warm and your hash rate drops. Frankly anyone going above and beyond 212.5 on batches 1 to 3 is going to be sorry in about 6 weeks. If you want higher freq the 212.5 you will need a custom cooling solution for the dc to dc part. my guess would be a heat sink on it and a fan directly on it blowing air out of a hole drilled into the case. or set the freq to 212.5 still hoping to do a pencil mod with my next 2 coming in. These s-3's will be a world beater at freq 200 or 206.25 with a pencil mod under volt. maybe under .6 watts a hash say .58 watts Which part is the dc/dc converter? Can you label it in a picture? I have extra heatsinks and fans and a climate controlled server room. If there is a mod that can fix this (short of replacement) I should have the means to do it. I actually did this mod for all of my S1s and saw a 1GH inprovement across each unit. I have enough for one unit coming in on Monday so I'll go ahead and try it myself to verify. The part you are looking for are the eight grey square "blocks" above the heat sink. There were only four-per-blade on the S1  Cool. Thanks for that. I have some similar heatsinks to what you had in the pics from your other post left over from the old GPU mining days. Actually I still mine x11 with GPU's, I just don't have as many GPU's as I used to. |
|
|
|
Ugh. 10 hours in and Ant1 fell to 411Gh at 218 and Ant2 fell below 400Gh as expected. I wish Bitmaintech would include an option to auto-restart in the firmware. Thinking about creating a small cronjob to do just that...
try setting them to 212.5 freq your dc to dc convertor gets too warm and your hash rate drops. Frankly anyone going above and beyond 212.5 on batches 1 to 3 is going to be sorry in about 6 weeks. If you want higher freq the 212.5 you will need a custom cooling solution for the dc to dc part. my guess would be a heat sink on it and a fan directly on it blowing air out of a hole drilled into the case. or set the freq to 212.5 still hoping to do a pencil mod with my next 2 coming in. These s-3's will be a world beater at freq 200 or 206.25 with a pencil mod under volt. maybe under .6 watts a hash say .58 watts Which part is the dc/dc converter? Can you label it in a picture? I have extra heatsinks and fans and a climate controlled server room. If there is a mod that can fix this (short of replacement) I should have the means to do it. |
|
|
|
Ugh. 10 hours in and Ant1 fell to 411Gh at 218 and Ant2 fell below 400Gh as expected. I wish Bitmaintech would include an option to auto-restart in the firmware. Thinking about creating a small cronjob to do just that...
I am having very similar issues. Starts off ok but hashrate sinks later. What sucks is that its impossible to tell when it will sink, sometimes soon, sometimes it runs fine for hours. But once it takes a dive it never recovers. I have seen it go 7 or 8 hours after a reboot with a good rate and then tank so bad for the next 2 or 3 hours that it just kills the total average to below 400. Pool side graphs tell the same story. Something happens and it just chokes. One possibility I have been pondering is a batchfile using plink. Should be able to store credentials and insert the one command you need which is reboot. Set that as a scheduled task and you should be able to reboot whenever you like. I see the scheduled task tab in the miner but not sure how to use it which is what I guess you are talking about. |
|
|
|
I can't seem to make the darkcash payout happen. It is over my threshold and that didn't cause a payout so I tried manual and that didn't do it either.
Same problem where.. please enable withdrawal of DRKC coins...
problem solved. Yes mine paid too. |
|
|
|
|
I can't seem to make the darkcash payout happen. It is over my threshold and that didn't cause a payout so I tried manual and that didn't do it either.
|
|
|
|
looks like the load was lowered, but it is hashing slower with less accepted shares
Poolside  The hash went up poolside. Strange the way the pools are exaggerating the rates, such as BTC G is doing as well. I will work with the Queue values to get a reading on how it effects both GUI and poolside values. BTW philipma1957 I am sure you recognize the pool used here. That is quite a significant difference between what the miner says and what the pool says. |
|
|
|
Note to underperforming S3 owners:
I have one S3 that was underperforming at ~420 Gh, i tried to 'boost" it up by moving to 225mhz-no change, but no high errors either.
So, i flashed with todays firmware-and it jumped to 455-457Gh, WU 6450-6470
Conclusion: NEW firmware is beneficial to at least some underperforming ants
allright, Bitmain! Thanks
Not really helping mine. If I OC I can get a good hash rate for a while but eventually it just tanks and over time the average floats down to really pathetic levels. If I leave it at stock it hits 400-410 and that's it. These things are really temperamental and I am very underwhelmed. Especially after having dealt with the S1's which were just so solid. Reboots cause random x's and -'s in the gui and occasionally mine will come out of a reboot and think it has no blades at all and never start hashing until I reboot again. That stuff is just weird and annoying. |
|
|
|
... Seems to go down after a few hours...
I have this same issue with one of mine. Does fine for a while then tanks until I reboot, then fine again for a while. The amount of time it runs fine seems to vary A LOT. Sometimes short, sometimes for hours on end. But so far it always eventually tanks to sub 300 Ghs until I reboot it. No x's or -'s in the GUI. Not sure what to make of it. |
|
|
|
Hi, does anyone know what this means?
Is one of the chips dead?
What can I do about it?
Frequency 218.75
oooooooo oooooooo
oooooooo ooooooo-
Try a reboot or two from within the GUI. Sometimes you can get it to go away. |
|
|
|
Received my S3's today and set them up this evening. The first one has no lines in the 'ASIC status' but the second one has a single line in it's 2nd 'ASIC status':
00000000 00000000
00000000 000000-0
Both are running off an EVGA 1300 Gold PSU using two PCI-e cables each.
I took the lid off the second S3 and took the heat-sinks off and cleaned up all chips re-applied a small dot of thermal CPU paste, reassembled and the 'ASIC status' was initially all clear and then after a couple of reboots the line re-appeared in the 'ASIC status'. Any suggestions?
The first S3 has ~421 and ~420 GHs running at stock frequency of 218.75.
The second S3 has ~475 and ~419 GHs running at same stock frequency.
They've only been running for half an hour.
you can reboot the second one with the gui reboot option. if the _ sticks change the freq to 212.5 both of my miners won't mine well at 218.75 they have 1 or 2 constant _ but both are good at 212.5 I changed the second S3 to operate at freq of 212.5 and still have a '-' in the ASIC status!! I have one of those too. Or had. Yesterday when I got the miners I had it come back several times. A reboot would sometimes make it go away or change to an x but it kept coming back. First thing I did with both miners was try them at various freq but neither of them seemed to like OC very much. Hashrate was marginally better at each step but HW errors were a lot higher on both at any OC. I did try downclock also but it did not make the - go away and made the hash rate even more pathetic. Neither of my miners pull 441 Ghs at stock freq. Yesterday I took off the heat sinks for the one with the bad chip and the chips were not drenched in thermal paste as some people have seen, but actually seemed like they could have used a little more. I was pretty meticulous about putting it on the entire surface of each chip without a lot of extra (and cleaning it up on the sides where it did run off and pool a little). But even after that it was getting the -. But yesterday after having done that thermal paste cleanup I OC'd to 225 and left it for the night. What I noticed this morning was that the HW errors were much improved compared to when I first unboxed them - I thought it might be due to the cleanup of the thermal paste but it could also have been that bad chip being presumably left out of the loop (since it had a dash all night) so I thought maybe it had been the source of the HW errors before. So thinking to try and nudge it closer to the 441 advertised hash rate I bumped it up to 237.5 freq this morning. Now it is actually just getting 441 but the problematic chip has also been showing an o ever since also. I doubt it is really fixed but I am happy about the hashrate for now. But I won't be shocked if the chip shows an x after the next reboot either. As long as I get 441 out of it though I'll live with it. I also took off the heatsinks on my other miner since it also wasn't pulling 441. That one actually looked like it had a good job of thermal paste on both sides. No huge voids and not a ton dripping off the sides. But it still had a little bit pooled on one side or another of a couple chips. Again I was real meticulous about getting it just right and cleaning up the excess and lo and behold that one is suddenly working great at 250 freq with minimal HW errors. It's pulling 501 Ghs ave at 3 hours now. That one was a little weird though too, the 237.5 freq actually lowered the hash rate to about 400 so I was actually pretty surprised to see what happened at 250. I was pretty bummed with both of them yesterday but I am happier about it today with the one pulling such a high hash rate and the other at least making the advertised 441. I run them both with fans at full (blue wires disconnected) and covers off in a server room (ambient temps maintained below 70 Fahrenheit). The temps in the GUI are all mid 30's. I switched the PCI-e cables to the two rear sockets and the - in the ASIC status went. Are you using 4 PCI-e cables per S3? I am using 4 yes. |
|
|
|
Received my S3's today and set them up this evening. The first one has no lines in the 'ASIC status' but the second one has a single line in it's 2nd 'ASIC status':
00000000 00000000
00000000 000000-0
Both are running off an EVGA 1300 Gold PSU using two PCI-e cables each.
I took the lid off the second S3 and took the heat-sinks off and cleaned up all chips re-applied a small dot of thermal CPU paste, reassembled and the 'ASIC status' was initially all clear and then after a couple of reboots the line re-appeared in the 'ASIC status'. Any suggestions?
The first S3 has ~421 and ~420 GHs running at stock frequency of 218.75.
The second S3 has ~475 and ~419 GHs running at same stock frequency.
They've only been running for half an hour.
you can reboot the second one with the gui reboot option. if the _ sticks change the freq to 212.5 both of my miners won't mine well at 218.75 they have 1 or 2 constant _ but both are good at 212.5 I changed the second S3 to operate at freq of 212.5 and still have a '-' in the ASIC status!! I have one of those too. Or had. Yesterday when I got the miners I had it come back several times. A reboot would sometimes make it go away or change to an x but it kept coming back. First thing I did with both miners was try them at various freq but neither of them seemed to like OC very much. Hashrate was marginally better at each step but HW errors were a lot higher on both at any OC. I did try downclock also but it did not make the - go away and made the hash rate even more pathetic. Neither of my miners pull 441 Ghs at stock freq. Yesterday I took off the heat sinks for the one with the bad chip and the chips were not drenched in thermal paste as some people have seen, but actually seemed like they could have used a little more. I was pretty meticulous about putting it on the entire surface of each chip without a lot of extra (and cleaning it up on the sides where it did run off and pool a little). But even after that it was getting the -. But yesterday after having done that thermal paste cleanup I OC'd to 225 and left it for the night. What I noticed this morning was that the HW errors were much improved compared to when I first unboxed them - I thought it might be due to the cleanup of the thermal paste but it could also have been that bad chip being presumably left out of the loop (since it had a dash all night) so I thought maybe it had been the source of the HW errors before. So thinking to try and nudge it closer to the 441 advertised hash rate I bumped it up to 237.5 freq this morning. Now it is actually just getting 441 but the problematic chip has also been showing an o ever since also. I doubt it is really fixed but I am happy about the hashrate for now. But I won't be shocked if the chip shows an x after the next reboot either. As long as I get 441 out of it though I'll live with it. I also took off the heatsinks on my other miner since it also wasn't pulling 441. That one actually looked like it had a good job of thermal paste on both sides. No huge voids and not a ton dripping off the sides. But it still had a little bit pooled on one side or another of a couple chips. Again I was real meticulous about getting it just right and cleaning up the excess and lo and behold that one is suddenly working great at 250 freq with minimal HW errors. It's pulling 501 Ghs ave at 3 hours now. That one was a little weird though too, the 237.5 freq actually lowered the hash rate to about 400 so I was actually pretty surprised to see what happened at 250. I was pretty bummed with both of them yesterday but I am happier about it today with the one pulling such a high hash rate and the other at least making the advertised 441. I run them both with fans at full (blue wires disconnected) and covers off in a server room (ambient temps maintained below 70 Fahrenheit). The temps in the GUI are all mid 30's. |
|
|
|
Hi,
Is anyone able to help me out? I purchased 2 of the S3's and bought the Enermax Triatholor ECO 550W 80 Plus Bronze PSU (one for each S3). It says the DC output is +12V 42A 504W. I hooked one PCI-e connector to one side of the machine and hooked up another PCI-e to the opposite side using only two of the four connections. The machine never reaches over 330 - 340 GH/s. Do I need to overclock this machine to reach the 478 GH/s, or do I need to buy a bigger PSU, or both? If I need a bigger PSU which is recommended?
please post your miner status page Here are my miner stats Something is off with chain 2. I've never seen that with the -o and it should be 16 not 32. What happens if you swap the PCI-e connector? If they chains swap info I'd say you have a PSU problem. If they stay the same I would think it's the miner. The chains stayed the same. I plugged in my second miner and it actually works the way it is supposed to. I switched the PCI-e's to the other two and everything stayed the same with the ASIC. Hooked up the 2nd PSU to the broken miner and still the same problem. Open it up (5 screws on each side, total piece of cake) and reseat the connector ribbons from the blades to the control board. If you still have the issue you may have one of the blades that is swimming in thermal paste in which case you will need to take off the heatsink (4 screws, not too hard to do but you have to also disconnect the fan because the heatsink has to slide up after you pull it away from the board) and clean up the chips. Or it could just be a bad blade and you will need to talk to Bitmain about a replacement. |
|
|
|
|
Show Posts
