 Show Posts
|
|
Pages: [1] 2 3
|
|
Можно расписать подробности? Заранее спасибо.
|
|
|
|
Running 10 S5 on f2pool now and no reboot needed so far. The others on nicehash keep crashing, seems really pool related.
Nicehash was working great for all S3 for months, never had an issue. Only the S5 have problems.
I'm running 6 S5s on kano main and extranonce with p=0125 on westhash and I've only had one issue in the last month, all 6 s5s were about 100g/h less than they usually were after a series of rapid switches over a day, I rebooted them and moved my p= amount up a bit to stop switching. I'm running smit's firmware with cgminer 4.9.0 Can you post a link to that firmware please? I want to try that |
|
|
|
|
For me the opposite. nicehash gibes nearly no errors, discusfish gives as many hw errors as accepted shares.
Something is not right here.
|
|
|
|
|
Running 10 S5 on f2pool now and no reboot needed so far. The others on nicehash keep crashing, seems really pool related.
Nicehash was working great for all S3 for months, never had an issue. Only the S5 have problems.
|
|
|
|
|
Router and everything is definetly not the problem.
IP adresses work 100% and other miners than S5 have no issues at all.
Nicehash might be an option, i will switch 10 to another pool and see if it changes.
Any idea why nicehash crashes them?
|
|
|
|
They all run static ip  |
|
|
|
|
I have 20 S5 running since one week.
ALL of them freqently (within 12-24 hours) get "lost.
I cannot acces them through webinterface and not trhough putty.
They are mining (all lights show normal operation and they are hot), but NOT at my pools. No hashrate there.
I have restart them by pulling power, then they work again normal for a few hours.
Running different firmwares, happens with all of them. None of the other miners (S2s, S3s) is doing this.
Makes me think if i bought 20 pieces of crap or if somebody guilt in a backdoor to have them mining for somebody else frequently.
I cant watch the miners 24 hours a day and then drive over to trhe place to pull power twice a day.
No answer from bitmain.
Anybody with similar problems or a solution?
|
|
|
|
|
Hi,
i got a few new S5 set up today and get some trouble with nearly half of them.
After a while hasrate drops 50%. Temps of 1 board drop down so it looks inactive, but the Asic status shows no x at all.
I rebbot and get it running for a while, but then it happens again. For one rebbot does not work, i have to do a complete power cycle to get it back running.
Definetly no powersupply issue and not overclocked.
Any idea what to look for?
|
|
|
|
|
Like topic says, selling all 72 together for 0.5 BTC
Complete value is 2.52 BTC.
I just have no more space for more miners so dont need them and i am too lazy for selling the coupans single, so all together for low price.
You can use them or sell them for more in lower quantity.
|
|
|
|
anybody tried to use more than 1 coupon per each S3?
Does not work |
|
|
|
|
Simply set the password to "p=0.02"
Done
|
|
|
|
So the problem S3 was down around 430GH/s this morning and I decided to go over its probably reworked board, the board that had grossly over-tightened screws, but would try frequency change first.
It had been down to 430 so I tried changing the frequency to check out its effect on hashrate. In /etc/config/asic-freq I changed to f=225, rebooted and restarted cgminer to get a fresh time duration. I gave it some time but it came up very slowly only to 420 or so. And it was a cool morning! All the other machines were hashing perfectly. So, I tried again, this time with f=212.5 but again it came up slow and only to 417GH/s. So, I ripped it apart again.
I was going to concentrate on its ASICs at the hot end of the reworked board, but ended up getting distracted. What distracted me was that the board had marking in black ink at the far right under the top ASIC (on this board that would be near the intake fan). Might have been Chinese or a code of some kind. So, I cleaned that ACIC and the one under it with a spray of automobile brake cleaner such that all thermal paste was removed. Must be careful with the stuff as it will mar many plastics. I sprayed those ASICs cleaning around the pins, reapplied thermal compound to both sides of the blade and reassembled. The brake cleaner removed the notation marks on that blade. When I reassembled, for a change, I put the bad board on the right side facing the RJ45 connector.
I started it up then ran to the store and back. Right now the 'difficult' S3, at a frequency of 218.75, after 1hr 20min, has an average hashrate of 443.74GH/s. The temps are both 40° with fan speeds of 2040/1800. Time will tell.
Bummer. Up now over 6hrs and the hashrate has started to drop off. Could be to an increase in humidity and that the first S3 hasn't seen a similar tailing off of hashrate because its average is over a 12hr period but probably not as it's at 442.24GH/s utility 17 while the problem S3 has tailed off to 437.63, utility 15. Experience tells me it will continue to fall and tomorrow morning may be down around 420GH/s. Temps are 40/39 and fans 1920/1620. The good S3 has 40/38 3180/1920 and the good and questionable S3's are side by side. What jumps out are the higher fan speeds of the good S3. Too bad. 1:30AM, checking the problem S3 and its hashrate has dropped to 429.01GH/s after 9hr 55min. Since I have two S3's, I could take what I think is the bad board and swap it into the other S3 and see if the good S3 then has a falling hashrate - just to make sure which board is bad. What's wrong with that is that the other S3, purchased from a reseller in the mid-west, runs fine (presently 441.67GH/s) while the problem S3 is from Florida (and that guy wants me to remove the 1 star Amazon rating, screw him, opened the bottom of a box from a good one and put the probably returned problem in and sent it out as new). By morning the problem S3 will likely be down to 420GH/s. Wonder if it's accumulating errors in an ASIC that then shuts down engines over time. Wonder if China sends more problem S3's to Florida than elsewhere given that Florida is a problem state like Shanghai crime before 1949. I'm not a happy camper. soy You are where many others have been 2 months ago. There are simply units like that and you probably wont be able to change it. And with 429 you cant complain, they were advertised with 441 +/- 5% if i remember correct. |
|
|
|
u need the price to hit 900 at least to sell and gtfo of here. If bitcoin is gonna go down, or stabilise, I am totally fucked. Lost half of my entire money. Help me please. But not like the guy who sent me 3 cents euro on my btc address. Send at least 2 euro.
YOU are seriously asking for donnations and even complain about small ones?  : I am. single my parents pay for every thing I need. I had some money from presents of my grandma. About 8k euros. All invested in btc almost. Now I have half of them at current price. I did not need those money to live but I thought it could be the bet of my life...
|
|
|
|
|
I have changed the API access on 2 of my S3 from restricted to privileged like posted here 2 pages back.
I thought it did not work, because i still see "restricted" in the summary.
Now i found that exactly these 2 where i tried show with the new update the clock and asic status, while the others dont.
On the other hand i still cant switch pools on them through awesome miner.
So are they now restriced or privileged? I must be missing something
|
|
|
|
|
Sounds more like the power supply does not handle it. 750 watt is hard on the limit.
|
|
|
|
|
