What batch s7 is that? running at 731 with low err rates and avg 4.8+? What PSU you using? I have not had much luck OC'ing the newer batches. I am only OC'ing batch 1-6 with pretty good results.
Batch 8 using an EVGA 1600. |
|
|
|
I just noticed that one of my Avalon 6s mined a 40,381,314,690 share here today. Nice, but not nice enough!
I just noticed I hit a nearly 4 trillion share. Wish the contest was based on share difficulty I think I would have a shot. https://i.imgur.com/2LmgYQ4.jpgYou can calculate from the share diff which block it was  (I did a post with php how to do it a few years ago in a hardware thread) That's interesting. I didn't know that. I guess I am not as incognito as I thought.  |
|
|
|
I just noticed that one of my Avalon 6s mined a 40,381,314,690 share here today. Nice, but not nice enough!
I just noticed I hit a nearly 4 trillion share. Wish the contest was based on share difficulty I think I would have a shot.  |
|
|
|
ROI looks pretty good and with the $100 coupon and quick shipping even better.
no way that they will be giving out $100 coupons if profitability was good. They are turning inventory and volume sales. Bitmain is also clearing out the inventory that has already produced a profit for them. In turn, they are incentivising their product to move it out the door quicker. Check out their business model: 1) Their own mining operation 2) Their own pool and 3) product for sale. All three working in concert. Looking from our perspective: ROI in 2.5 months and 1 month profitability plus the sale of the S7 in future months. I don't necessarily disagree, but difficulty could go up 60% in one mo if 14-16nm machines will go on sale or THEY start mining with them. What would be the price of such resale be in 2.5 mo, $200? Money better spent just buying (or not buying) btc here, IMO. You kinda hit one thing on the head this is killing resale value of S7's. And the interesting thing is it likely will effect all other miner's prices to.... which becomes interesting. So really good for someone buying a bunch of new S7's (assuming difficulty does not shot up insane). But difficulty has become hard to predict. They will sell though inventory though I predict at this price with coupons. I did not see this coming personally. I ordered several S7 batch 12. Some of them came in with firmware dated March 4, 2016 and some of them came in with firmware dated December 3, 2015. I have more Batch 15 coming in this week and will be interested to see what date of firmware is on them. That highly suggests used hardware. It seems unlikely they would have installed Dec firmware on a miner built more recently. |
|
|
|
I am having an issue with 3 of my s7 batch 2. They are running but not mining and I am not sure what do there seems to be no CG Miner after my last reset.
Miner Type Antminer S7
Hostname antMiner
Model GNU/Linux
Hardware Version x.x.x.x
Kernel Version Linux 3.8.13 #22 SMP Tue Dec 2 15:26:11 CST 2014
File System Version Fri Oct 23 17:00:53 CST 2015
Cgminer Version
Uptime 0
Load Average 0.18, 0.04, 0.01
That hardware version reporting as X.X.X.X with no hashing was discussed a page or two ago in this thread. The person who reported it was able to fix it by reflashing the firmware. I mentioned also that I had seen this behavior on previous antminer models (but not my S7's) and was able to fix it by doing the reset to default button. |
|
|
|
|
The biggest problem I see with these cheaper and cheaper batches is that ROI on the older batches just keeps looking worse. I have S7 miners from 3 different batches and ROI is closer on the most recent one than the oldest ones. The price on the newer batches drops faster than the income on the previous ones which means that sitting on BTC all along would actually have been more profitable than buying. Another thing that is bugging me about these is the ROI time, due to the huge difficulty jump, is much longer than with some of the previous antminers. And trusting a machine to stay working for 6 months to make ROI is risky. I have two different miners that each cost more than 1k at purchase that are mining at less than full capacity due to blade failures and without warranty there is nothing I can do. The odds of them making a break even return are basically zero already.
|
|
|
|
Well, now that's quite a stretch. Sounds like you are a bit pissed off. Sorry if you were a bagholder, so were many of us
Maybe your reading comprehension is poor, so I will explain it to you again: I never touched paycoin nor hashlets, because the scam was obvious and it would have been stupid and/or unethical to participate in it.
- There is nothing wrong with getting our money back
Wrong. The fact that you fell for an obvious scam does not mean you get to steal from others. Stay away from scammers and shitcoins, and if you made money by trading in a shitcoin and participating in a scam, then don't fucking brag about it. I am inclined to agree with Franz_Huber. It was obvious to anyone with a couple of brain cells that something wasn't quite right at the very beginning of the hashlet thing. suchmoon started the very first thread asking questions right out of the gate and was pointing out red flags to anyone who bothered to think at all about it. I had purchased hardware from gaw before that but I also never touched the hashlets. Even in the very beginning of the hashlet craze when there was so much hype it looked to me like someone could probably jump in and make some money as long as they got out quick but I agree with Franz, only an asshole would have done so (if they believed it to be a scam, as I did). So I think it is actually fair to say that idiots and assholes were the biggest population of investors. Because generalizations are, generally speaking, bound to have exceptions, I will allow for some few investors who may not fully qualify as either but probably that group is pretty small (I know some people had hosted hardware that wound up going down the hashlet rabbit hole so they obviously didn't choose to be involved for example). |
|
|
|
|
I had balance of something like .02 or .03 and it was not paid or transferred.
EDIT: oh but now when I go look I see it was zeroed so I guess that makes it official that I won't get it. Not that I thought I would. It was stuck for months.
|
|
|
|
One of my miners stopped hashing. I can get to the web UI, everything seems normal but hardware is x.x.x.x and hashrate is 0, showing no board information at all, not even x or - http://pastebin.com/bZBhnA6sIf you are saying the hardware version is listed as X.X.X.X in the overview tab, this exact issue on earlier antminer models is fixed by using the reset to defaults button. I haven't seen it on my S7's but I have seen it on an S2 and an S5 and that was the fix. |
|
|
|
So this is supposed to be using the new bitfury chips? Wouldn't that make this the first publicly available miner that does so? EDIT: Oh I see on the website they are only claiming the high-end one uses the new chips. So they all have the same electricity usage but hashrate varies by chip used. http://en.hotmine.io/#pricingThat hashrate to kilowatt ratio is in the range of what bitfury claims for the new chip according to my back of the napkin calculations but according to bitfury claims on efficiency that would put it at the very bottom end of that range (or maybe slightly under it actually). EDIT AGAIN: Oh now I notice where it is a pre-order. They all are, but the 16nm one has the furthest out date with Sept of 2016. So maybe or maybe not the first publicly available device with the new bitfury chips. |
|
|
|
I need to pick someone's brain about solo mining PEERCOIN with S7's
For whatever reason I just cannot get it going and yes, I'm running a full node with plenty of incoming connections. The router is configured properly. It a matter of getting the miners to talk to the node/wallet. and yes again, I'm running the latest version v0.5.2
If someone is mining PEERCOIN with their S5 or S7, please post your ppcoin.conf file, and what you use for the URL to talk to the wallet.
Thanks
BTW.... My head hurts from beating it on the keyboard....
i run Peercoin solo mining every weekend, about 30$ USD per block, sometimes I hit 3-4 blocks per weekend on a good day stratum+tcp://ppcoin.securepayment.cc:3357 Username: P------------------------- Password: x You need to insert your peercoin address -- its starts with a capital "P" Password, just put "x" - and let the pool auto adjust the diff level for you. Checkout holytransaction.com, its a funky web multi-coin wallet, and it also gives you a Peercoin wallet and address. How much hashrate are you talking about for those 3-4 blocks? |
|
|
|
Quoting Slush's facebook post on Feb 6. about it:
"Dear miners, we would like to inform you that we have detected and resolved an unintentional block withholding
The issue has been discovered a week ago and we have immediately taken an action by contacting the particular miner. The cause turned out to be a bug in a custom mining firmware, which has been promptly fixed by the miner. We have no indication that there was any bad intention. The fixed firmware solved two blocks since then so we can consider this issue as resolved.
A recent time period of worse luck can be at least partly attributed to this incident.
Block withholding attack is a well-known weakness of the whole pool mining principle and no public pool is immune against it.
As a by-product of the bad luck investigation, we have implemented a new method how to mathematically prove that the pool does not cheat on miners. This feature will be released after the public interface has been tweaked. The release is planned towards the end of next week."
End Quote
He said it was a week, but people had been asking about poor luck at the pool since early December. The end result was that the miner did not repay the pool, and the "bad luck" still to continued. With no further comment from him on it. The only "news" was the pool's new interface.
I've sat through bad luck streaks before and kept silent, cuz hey, they happen. I worked in the casino business for 20 years. But with no answers/comments coming from slush and combine it with orphan block debacle that seemed to just drag on, I started looking for a new place to mine.
I landed here at Kano.is and have been very happy with the transparency of the pool operator and the community overall.
That's interesting. That EXACT same thing happened on Bitminter some time ago. Big miner, not hitting blocks, custom software was blamed. I don't believe it went on for as long though. |
|
|
|
Remember when there was an anomalous miner on slush's pool, he allowed 10PH of worthless mining for over a month and kept paying them for it and then proudly announced he had developed 'provably fair mining' to prevent it ever happening again, but had already been paying 10Ph worth of payouts to them for a month, and never returned the rewards paid to that miner to compensate the rest of the miners. Let's just say we don't want to see that happening here before you complain about a block payout being delayed.
I agree! let Kano do what he does That is REALLY ff'ed up, 10PH for a month. That, combined with a total lack of communication from "The Captain", was the final straw for me at slush. I had been mining there since January 2014. I joined kano.is about 3 weeks ago and haven't looked back. I really appreciate the constant communication and updates Kano and -ck provide. I missed this. I do recall hearing about some extraordinary bad luck at slush not that long ago so I am guessing this is the same thing. So was it a block withholding attack or did someone figure out another way to game the pool? |
|
|
|
|
I can't believe you guys are still buying. I have buyers remorse on these things. According to my calculations I need Kano's pool to hit about 686 more blocks without my per block payout going down just to break even. Without a doubt I would have been better off holding BTC than buying these.
|
|
|
|
|
I tried swapping the entire cable at one point too. The problem definitely went with the hashboard at that point. I got tired of messing with it for today.
The setting in the GUI to stop mining if it goes above 80 degrees is always on, unchecking the box in the GUI does not seem to turn that off. I am going to see if I can find it in the filesystem and disable it. The boards hash fine, the only issue is the temp reporting is unreliable and erroneous and when it pops up with a temp above 80 the whole thing stops hashing. I can live with bad temp reporting if it still hashes.
EDIT:Something really curious about this machine's behavior, the original issue where the temps all went to zero started when Kano's pool had a brief downtime and the miner failed over. The issue today where the zero temp blade went to 127 coincided with Kano's pool finding a block. Immediately after the 79% diff block is when this miner stopped hashing. It's almost like what cgminer is doing on the box is affecting how that temp reporting is working somehow.
EDIT2:I SSH'd into the machine and I see that unchecking the 80 degree box in the GUI makes a corresponding change to the cgminer.conf file so right now I have my doubts that I can figure out why that isn't working and change it.
|
|
|
|
Well hell. My batch 8 has developed a problem. It started beeping and I happened to be nearby so I checked out the GUI and the hashrate was slowly dropping to zero. I noticed that one hashboard said the temp was 96 and two of them said temp 0. So I rebooted through the GUI, it came up and started mining but the temps all say 0 now. I did a power cycle and same thing, all zeros. At least it is hashing though so that's good. It didn't overheat, it is sitting next to a couple other S7's and the temp where they are didn't get up past room temperature and the other machines are fine. When I powercycled it I did gently move it around to check for a loose heatsink but there wasn't anything detectable, plus I think those were mostly in earlier batches. But now all zeros on the temps. Lame.
i`ve add the same issus happens to me on a S4 and a S5, reflashing the machine ( even if it;s the same revision ) cured my problems both times, actually the s5 i had to flash 3 times. let it sit for a day than came back to life the next flashing. try it out. I ended up having to do this. After working fine for a couple days with all zeros for the temps the sensors did wig out and one reported 96 and another reported 32 so it stopped hashing again. The weird thing is, after reflashing it, only those two boards are reporting a temp (a normal one now) but the third board is still showing zero. Something tells me a reset to default would cure this but I'll wait until the machine gives me no other option. Now the last board that was stuck at zero is reporting an erroneous temp of 127 and miner won't hash. I tried multiple reflashings, a couple of resets to default. No love. POS. It mines if I disconnect that board but 2/3 hashrate is never going to get near ROI on this thing. I tried swapping the control cables and the problem goes with the hashboard. I have a hard time believing it is a hashboard problem though because all 3 hashboards have done this at some point. It's just that two of them stopped doing it when I reflashed the first time. EDIT: Well holy crap a bit of luck! After running it for 20 minutes or so with just two boards (the bad board was disconnected from the controller board and the PSU), I figured what the heck I'll connect it all back up and give it another shot. All boards working and reporting correct temps. Looks like the hashboard needed to be left off and unpowered for a period of time. EDIT2: Spoke too soon. No sooner did I have that board working then the other two started reporting weird temps. After letting the whole thing sit I am back where I started with the original board reporting zero and the other two reporting normally. |
|
|
|
Well hell. My batch 8 has developed a problem. It started beeping and I happened to be nearby so I checked out the GUI and the hashrate was slowly dropping to zero. I noticed that one hashboard said the temp was 96 and two of them said temp 0. So I rebooted through the GUI, it came up and started mining but the temps all say 0 now. I did a power cycle and same thing, all zeros. At least it is hashing though so that's good. It didn't overheat, it is sitting next to a couple other S7's and the temp where they are didn't get up past room temperature and the other machines are fine. When I powercycled it I did gently move it around to check for a loose heatsink but there wasn't anything detectable, plus I think those were mostly in earlier batches. But now all zeros on the temps. Lame.
i`ve add the same issus happens to me on a S4 and a S5, reflashing the machine ( even if it;s the same revision ) cured my problems both times, actually the s5 i had to flash 3 times. let it sit for a day than came back to life the next flashing. try it out. I ended up having to do this. After working fine for a couple days with all zeros for the temps the sensors did wig out and one reported 96 and another reported 32 so it stopped hashing again. The weird thing is, after reflashing it, only those two boards are reporting a temp (a normal one now) but the third board is still showing zero. Something tells me a reset to default would cure this but I'll wait until the machine gives me no other option. |
|
|
|
Well hell. My batch 8 has developed a problem. It started beeping and I happened to be nearby so I checked out the GUI and the hashrate was slowly dropping to zero. I noticed that one hashboard said the temp was 96 and two of them said temp 0. So I rebooted through the GUI, it came up and started mining but the temps all say 0 now. I did a power cycle and same thing, all zeros. At least it is hashing though so that's good. It didn't overheat, it is sitting next to a couple other S7's and the temp where they are didn't get up past room temperature and the other machines are fine. When I power cycled it I did gently move it around to check for a loose heatsink but there wasn't anything detectable, plus I think those were mostly in earlier batches. But now all zeros on the temps. Lame.
EDIT: Looks like this was actually precipitated by a brief failover on the pool. I have seen these things get messed up on failover before but this is the first time I saw an issue develop that didn't get cured by a power cycle.
What are your fans set at? Do you set them at manual? 50%. To 55 % is pretty good setting Yeah I did that when I got them. Sixty percent. |
|
|
|
Well hell. My batch 8 has developed a problem. It started beeping and I happened to be nearby so I checked out the GUI and the hashrate was slowly dropping to zero. I noticed that one hashboard said the temp was 96 and two of them said temp 0. So I rebooted through the GUI, it came up and started mining but the temps all say 0 now. I did a power cycle and same thing, all zeros. At least it is hashing though so that's good. It didn't overheat, it is sitting next to a couple other S7's and the temp where they are didn't get up past room temperature and the other machines are fine. When I powercycled it I did gently move it around to check for a loose heatsink but there wasn't anything detectable, plus I think those were mostly in earlier batches. But now all zeros on the temps. Lame.
i`ve add the same issus happens to me on a S4 and a S5, reflashing the machine ( even if it;s the same revision ) cured my problems both times, actually the s5 i had to flash 3 times. let it sit for a day than came back to life the next flashing. try it out. Thanks for letting me know. I am a bit leary of flashing these machines actually based on previous posts on the matter where people bricked them. But that is good info and I will keep it in mind. Since it is mining ok and since I have other machines nearby that can give me an idea if the ambient temps in there are a problem I guess I will just live with it. I did take off the tick box to have it stop mining if temps go above 80 just in case the temp sensors start reporting something crazy again. |
|
|
|
|
Well hell. My batch 8 has developed a problem. It started beeping and I happened to be nearby so I checked out the GUI and the hashrate was slowly dropping to zero. I noticed that one hashboard said the temp was 96 and two of them said temp 0. So I rebooted through the GUI, it came up and started mining but the temps all say 0 now. I did a power cycle and same thing, all zeros. At least it is hashing though so that's good. It didn't overheat, it is sitting next to a couple other S7's and the temp where they are didn't get up past room temperature and the other machines are fine. When I power cycled it I did gently move it around to check for a loose heatsink but there wasn't anything detectable, plus I think those were mostly in earlier batches. But now all zeros on the temps. Lame.
EDIT: Looks like this was actually precipitated by a brief failover on the pool. I have seen these things get messed up on failover before but this is the first time I saw an issue develop that didn't get cured by a power cycle.
|
|
|
|
|
Show Posts
