Looking for some Ideas
Gen 2 blade GREEN issues:
I am now more perplexed as to what is the issue with my blades.
I now have 2 blades, both are using power supplies with well more than the 8.3amps on 12v that is needed triple the amount needed in fact.
I pointed 1 to a bfg proxy and 1 to slush's mining proxy program but neither will exceed 7.2gh/s.
If it were network traffic issues adding the 2nd blade in "theory" should have dropped both?!
They are in the same network.
They both insist on changing proxy servers about every 40 work units requested.
You can not put a blank or the same ip for both servers or they will stop requesting work after 40 until they are rebooted.
I put a bfg proxy on a server and pointed them to 2 ip's on the server which works. but they do not exceed 7.2gh/s
I setup another proxy on another server and pointed the other blade at it. still will not exceed 7.2gh/s.
I changed one of the proxys to the slush miner and the other to bfg, still wont exceed 7.2gh/s
Neither are running hot, they have more than enough cooling on them.
in BFGMiner the first column says 10ish/7.2/7.0gh/s
What does the first column mean?
Total MHS: 07318
Received: 0000257291
Accepted: 0000203803
Per Minute: 100.00
Efficiency: 079.21%
Up Time: 1d,09h,57m,53s
Current Server: 10.1.3.144:8334
Chip: OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
Total MHS: 07217
Received: 0000259925
Accepted: 0000202522
Per Minute: 098.61
Efficiency: 077.91%
Up Time: 1d,10h,13m,39s
Current Server: 10.1.3.72:8333
Chip: OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
Same problem. I changed two things and am back up to: Total MHS: 10052 Received: 0000001024 Accepted: 0000000983 Per Minute: 139.57 Efficiency: 096.09% Up Time: 0d,00h,07m,03s 1) I stopped using a laptop for stratum-mining-proxy that was also running cgminer for a Jalapeno and possibly overworking it. 2) I took my RPi, running stratum-mining-proxy, and changed it from wifi to RJ45; it had been servicing 6 USB BEs, and addressed the Blade to the RPi. I had put the 6 BEs to the stratum on the RPi originally as addressing the cgminer running the BEs on another RPi directly to stratum.mining.eligius.st was getting difficulties in the /127. For some reason that is no long the case and the BEs are getting diffs of 15/1 or 163/1 and the like, much better. On the overloaded laptop stratum was showing for instance 1002milliseconds on accepted's for the Blade, way to slow moving the data, while the Blade is now showing [0ms] and: Total MHS: 11031 Received: 0000002592 Accepted: 0000002626 Per Minute: 150.91 Efficiency: 101.31% (oy) Up Time: 0d,00h,17m,24s soy So you r using the rpi's for your blade proxy's now? I am using 2 beefy servers for my proxy servers. Their activity is essentially nil, network utilization is .7%. Teamed nics etc etc. Both blades have creeped up to 7400 and 7300 the last 5 days from 7100ish. I could try using an RPI. both blades to 1 PI? |
|
|
|
|
luck is luck...
I am surprised u r matching daily payouts between slush and btcguild. r u sure?
Solo mining 700 gh/s... how long will that take to find a block? by saying .7 u r implying less than 2 days. I would doubt that and guess more like a week. but what do I know! well I know the diff is 510+ now
|
|
|
|
So, does anyone know the situation with the payouts?
Is all fixed now for future payouts? I have enough confirmed balance to pass my threshold, but it has not yet paid out since this morning.
Just wondering.
A watched pot never boils |
|
|
|
I need help recovering my wallet. I re-installed my Windows today and lost one of my wallets in the process because I didn't backup the private key.
However, I have private key backed up for this wallet two weeks ago. But since then I created new receiving address. Now my balance shows zero and if I create a new receiving address it is not the same as what was created before the backup.
Need help! I'm using multibit.
I'm afraid you won't be able to recover your wallet as multibit wallet is non-deterministic (AFAIK). However you could try scanning your HDD for deleted files using specialized software. Recuva is free and will scan the HD for lost files. however if u formatted the drive, it isnt going to find anything. formatted means formatted not quick format which isnt formatting its just a directory table wiping |
|
|
|
now back to staring at my blades mining at 7gh/s for no reason at all...
Still? If you were in Toronto I'd gladly get your equipment here and try it out. I'm just lazy, I could easily bring 1 home and try it but if it works that doesnt solve the problem at work. maybe wireshark will tell me something |
|
|
|
I have an unconfirmed payment from 11/7 and a negative balance with no double payment visible.  On the Slush web site https://mining.bitcoin.cz/accounts/profile/ it says " Quick updates 08.11.2013 Some recent payouts didn't go thru bitcoin network because of unsatisfied transaction fees. We're finding a soluton and all payouts will be processed soon" Hopefully they will fix this soon, or try to contact Slush support email or the Live Support. In my case the double payments were not consecutive. looking at my wallet transactions, stats (I copy and keep my Slush stats) and the payout history I managed to figure it out more or less... Newcomers to slush pool: slush's pool IS the shit. Slush's pool is a small operation. Sometimes weird stuff happens for a while, most likely because the genius is updating his site. It ALWAYS corrects itself (at least 99% of the time). Just trust the slush. My take on Slush's Pool since I have been mining on slush since January of 2013 is 1. Very Little down times (Great pool connection) 2. Payment is a little funky sometimes but corrected with given time, and for the most part every payment is right. 3. Lucky days is when you have a great day, unlucky days  but it averages out with the lucky days.  4. Forum thread for this pool is a like a family, everyone comes here to talk, complain and resolve. I have high confidence Slush will fix it. but if people are told to sit down and shut up Slush has no reason to look closer at a possible oddity. now back to staring at my blades mining at 7gh/s for no reason at all... |
|
|
|
My "confirmed reward" has gone negative.... Slush, do I owe you any bitcoins?
Confirmed reward: -0.01298504 BTC Your confirmed balance from valid blocks
I didn't even think this was possible and am myself curious as to whats up. Edit: Anyone able to help with: https://bitcointalk.org/index.php?topic=327410.0The mystery was partially solved, as my account page now contains this message: Notice: The last payment to you was sent twice by a mistake. This has caused that your confirmed reward is temporarily below 0 BTC. We're sorry for the inconvenience. Strange, but I hope that it is correct. Partially solved ? Did you confirm a two times payment to your wallet ? I found 2 identical payments, and tracing back the block confirmation to payments over the last few days, Slush's claim looks correct. Still strange that it could happen (aren't these calculations supposed to happen automatically and not 'handrolically'?!!!). So Slush is honest... but more order is needed.... Cheers I don't have 2 identical payments. with these long blocks it would be quite noticeable with only 1 payment per day. so I dont see why slush is taking btc back |
|
|
|
My "confirmed reward" has gone negative.... Slush, do I owe you any bitcoins?
Confirmed reward: -0.01298504 BTC Your confirmed balance from valid blocks
Edit: later the following message appeared on my account: "Notice: The last payment to you was sent twice by a mistake. This has caused that your confirmed reward is temporarily below 0 BTC. We're sorry for the inconvenience."
Not sure how to audit the payments (the payout history uses rounded values and UTC, but I guess that with some effort that should be possible)
mine too? how can I have gotten a double payment with 3 blocks 10 hours long.... |
|
|
|
|
Confirmed reward: -0.00508126 BTC
interesting my confirmed award declares I OWE haha...
|
|
|
|
|
what does the first number in bfg miner mean?
11.2/ 7.20/ 7.20gh/s that first one
|
|
|
|
I had similar issues with 1 Blade. After fiddling with everything, someone informed me that my Dlink router was garbage and could have been the issue. I upgraded to new Belkin Dual band, Miner has been stable for weeks now. No random disconnects or proxy changes.
these are located in a server room with all high end equipment. I can't fathom stuff that can handle mega traffic would trip up on this stuff... but its gotta be something... I have both going to the same worker, maybe slush's auto diff thing is setting the diff too high... I am gunna try changing to 2 workers |
|
|
|
are people pointing their blades to separate workers or all pooled to one worker?
I have two blades pointed at 2 workers through one proxy. separate workers makes it easy to see if there is a problem. that is with slush mining program? bfg forces a certain user? |
|
|
|
|
are people pointing their blades to separate workers or all pooled to one worker?
|
|
|
|
|
Looking for some Ideas
Gen 2 blade GREEN issues:
I am now more perplexed as to what is the issue with my blades.
I now have 2 blades, both are using power supplies with well more than the 8.3amps on 12v that is needed triple the amount needed in fact.
I pointed 1 to a bfg proxy and 1 to slush's mining proxy program but neither will exceed 7.2gh/s.
If it were network traffic issues adding the 2nd blade in "theory" should have dropped both?!
They are in the same network.
They both insist on changing proxy servers about every 40 work units requested.
You can not put a blank or the same ip for both servers or they will stop requesting work after 40 until they are rebooted.
I put a bfg proxy on a server and pointed them to 2 ip's on the server which works. but they do not exceed 7.2gh/s
I setup another proxy on another server and pointed the other blade at it. still will not exceed 7.2gh/s.
I changed one of the proxys to the slush miner and the other to bfg, still wont exceed 7.2gh/s
Neither are running hot, they have more than enough cooling on them.
in BFGMiner the first column says 10ish/7.2/7.0gh/s
What does the first column mean?
Total MHS: 07318
Received: 0000257291
Accepted: 0000203803
Per Minute: 100.00
Efficiency: 079.21%
Up Time: 1d,09h,57m,53s
Current Server: 10.1.3.144:8334
Chip: OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
Total MHS: 07217
Received: 0000259925
Accepted: 0000202522
Per Minute: 098.61
Efficiency: 077.91%
Up Time: 1d,10h,13m,39s
Current Server: 10.1.3.72:8333
Chip: OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
|
|
|
|
|
I am now more perplexed as to what is the issue with my blades.
I now have 2 blades, both are using power supplies with well more than the 8.3amps on 12v that is needed triple the amount needed in fact.
I pointed 1 to a bfg proxy and 1 to slush's mining proxy program but neither will exceed 7.2gh/s.
If it were network traffic issues adding the 2nd blade in "theory" should have dropped both?!
They are in the same network.
They both insist on changing proxy servers about every 40 requests.
You can not put a blank or the same ip for both servers or they will stop requesting work after 40 until they are rebooted.
I put a bfg proxy on a server and pointed them to 2 ip's on the server which works. but they do not exceed 7.2gh/s
I setup another server and pointed the other blade at it. still will not exceed 7.2gh/s. I changed one to the slushs miner and the other to bfg, still wont exceed 7.2gh/s
Neither are running hot, they have more than enough cooling on them.
in BFGMiner the first column says 10ish/7.2/7.0gh/s
|
|
|
|
I am running the proxy's on 2 different desktops both are new installs of windows 7 64bit ultimate that do nothing but mine Usb Eruptors. I originally had a proxy on a windows 7 32bt ultimate machine which did no better.
something else I am noticing, the blade says it is at 6100mh/s yet slush is reporting 5300mh/s over time.
These 2 new blocks that happened slush had it at 6000mh/s after an hour it settles down to 5300. 35minutes into this new block now and its down to 5800 on slush. yet the blade says 6100 over that whole time.
Total MHS: 06157
Received: 0000015854
Accepted: 0000010555
Per Minute: 084.12
Efficiency: 066.57%
Up Time: 0d,02h,05m,28s
now slush showing 5400mh/s 1 hour later.
Total MHS: 06035
Received: 0000019876
Accepted: 0000012974
Per Minute: 082.47
Efficiency: 065.27%
Up Time: 0d,02h,37m,19s
The only other thing I can think of is you network. The IP address of your proxy has me a bit perplexed...I've not seen that IP range in a consumer router before. I put all my mining equipment on a separate simple Linksys router so its all on its own network. If nothing else, you may have just gotten a bad blade and you need to get it exchanged. What are your DNS settings. I am also under a corporate network, and I had to use my main gateway (or a router gateway) as my main DNS and I used 2.2.2.2 (google) as my second. This seemed to clear up some of my problems, but the systems I have at home (Avalon mini's) are always running at 60GH 24/7. My 115GH Avalon clones fluctuate from 98GH to 120GH on Slush throughout the day, but they both seem to get the same amount of shares in proportion to what the ones at home get, so I don't understand the fluctuations .... but at least they seem to be operating properly. Internal DNS. dns shouldnt have anything to do with anything since the blade isnt being asked to resolve anything. its only task is to ask for work from an IP u gave it hash and return the results to the IP's. no where in that process is any name resolution taking place. but who knows what possible secret other stuff it may be doing. I have the blade up to 7gh/s now. I put 2 bfgminers on a server and pointed the blade to 2 ip's on the server. so now it is mining steady but maxes out at 7gh/s. and as mentioned if I point it to the same ip it will cease to work, it will get 40 work units then just sit there only rebooting it will get it to ask for more work 40units and done. it demands to have 2 working ip's. I am thinking of hard resetting the blade to see if that clears up something possibly wrong with it. |
|
|
|
|
hrmm I just noticed this in the proxy output
2013-10-28 16:25:41,467 INFO proxy jobs.submit # Submitting befd0b3a
2013-10-28 16:25:41,469 INFO proxy jobs.submit # Job not found
2013-10-28 16:25:41,470 WARNING proxy getwork_listener._on_submit # [0ms] Share
from 'nonobra.worker1' REJECTED
2013-10-28 16:25:42,334 INFO proxy jobs.submit # Submitting 0c8e9c8a
2013-10-28 16:25:42,335 INFO proxy jobs.submit # Job not found
2013-10-28 16:25:42,336 WARNING proxy getwork_listener._on_submit # [0ms] Share
from 'nonobra.worker1' REJECTED
2013-10-28 16:25:42,638 INFO proxy jobs.submit # Submitting 18a6e676
2013-10-28 16:25:42,640 INFO proxy jobs.submit # Job not found
2013-10-28 16:25:42,641 WARNING proxy getwork_listener._on_submit # [0ms] Share
from 'nonobra.worker1' REJECTED
2013-10-28 16:25:43,158 INFO proxy jobs.submit # Submitting 53458523
2013-10-28 16:25:43,160 INFO proxy jobs.submit # Job not found
2013-10-28 16:25:43,163 WARNING proxy getwork_listener._on_submit # [0ms] Share
from 'nonobra.worker1' REJECTED
2013-10-28 16:25:43,427 INFO proxy jobs.submit # Submitting 330a97aa
2013-10-28 16:25:43,430 INFO proxy jobs.submit # Job not found
2013-10-28 16:25:43,430 WARNING proxy getwork_listener._on_submit # [0ms] Share
from 'nonobra.worker1' REJECTED
2013-10-28 16:25:43,450 INFO proxy jobs.submit # Submitting aaa36a03
2013-10-28 16:25:43,450 INFO proxy jobs.submit # Job not found
2013-10-28 16:25:43,453 WARNING proxy getwork_listener._on_submit # [0ms] Share
from 'nonobra.worker1' REJECTED
2013-10-28 16:25:43,805 INFO proxy jobs.submit # Submitting 7854f9b7
2013-10-28 16:25:43,806 INFO proxy jobs.submit # Job not found
2013-10-28 16:25:43,808 WARNING proxy getwork_listener._on_submit # [0ms] Share
from 'nonobra.worker1' REJECTED
2013-10-28 16:25:43,815 INFO proxy jobs.submit # Submitting 3fd0d079
2013-10-28 16:25:43,818 INFO proxy jobs.submit # Job not found
2013-10-28 16:25:43,819 WARNING proxy getwork_listener._on_submit # [0ms] Share
from 'nonobra.worker1' REJECTED
2013-10-28 16:25:44,611 INFO proxy jobs.submit # Submitting 667f5edc
2013-10-28 16:25:44,611 WARNING proxy getwork_listener._on_submit # [0ms] Share
from 'nonobra.worker1' accepted, diff 1
2013-10-28 16:25:45,270 INFO proxy jobs.submit # Submitting 28737752
2013-10-28 16:25:45,273 INFO proxy jobs.submit # Job not found
2013-10-28 16:25:45,273 WARNING proxy getwork_listener._on_submit # [0ms] Share
from 'nonobra.worker1' REJECTED
|
|
|
|
This is a network at work. 10.x is a non public network like 192.168.x and 172.16.x
You don't use 192.168.x on work networks unless your IT Staff are buffoons. It makes it easier to type and recognize DMZ with 10.1.x 10.2.x etc isolation. I am pretty sure these are also plugged into the same switch, but I may be wrong.
If not in the morning I will get them on the same switch and then also test it with a 650watt power supply.
Ah, that explains that IP range. The way I see it, you have two possibilities: 1. A bad Blade. 2. Some wonky network setting preventing the proxy from working correctly. You have tried different proxy's, multiple proxy's, two different power supply's and I'm guessing you probably have entered all your configurations in multiple times...there just isn't much left to these blades. Before you give up and send that blade back, I'd try running off a proxy outside of where you work and have the blade connect to it and see if it make any difference. I tested my blade (that is up at my shop) and I ran it off a proxy I set up on my home PC. My blade still ran fine off the other proxy. Ok I connected this up to a 575 watt power supply. there is no difference as I already knew since the 375 supplies more than enough current. It's sitting at 72% efficiency 6800mh/s for 45minutes, I call this no difference as it varied 6100-6500 on the 375 and +300mh/s is garbage to the missing 3000+. no connectors are getting warm which is a sign of a poor connection so there is good connections, aka it is getting all the current it wants without a problem of high resistance. I have a box fan blowing on it on high in a cooled server room. the blade both sides are mildly warm, the block eruptors in the same air are hot. so this blade is not over heating, it is getting all the power it needs and more than enough air flow. I have to conclude it is shot. I changed the proxy ports to 8333 and 8334 restarted the blade. now I am sitting at 61% per usual and 5300mh/s aka the 575watt supply or a 375watt makes no difference to how well this works. I am watching the 2 proxy screens.... This will get a ton of work then sit there sit there sit there... then get a ton of work from the other proxy or sometimes the same one but mostly flips... i rebooted the blade and now its back to 6700... so odd 41minutes in and its settled to 5800 worse than when powered by 375watts |
|
|
|
I am running the proxy's on 2 different desktops both are new installs of windows 7 64bit ultimate that do nothing but mine Usb Eruptors. I originally had a proxy on a windows 7 32bt ultimate machine which did no better.
something else I am noticing, the blade says it is at 6100mh/s yet slush is reporting 5300mh/s over time.
These 2 new blocks that happened slush had it at 6000mh/s after an hour it settles down to 5300. 35minutes into this new block now and its down to 5800 on slush. yet the blade says 6100 over that whole time.
Total MHS: 06157
Received: 0000015854
Accepted: 0000010555
Per Minute: 084.12
Efficiency: 066.57%
Up Time: 0d,02h,05m,28s
now slush showing 5400mh/s 1 hour later.
Total MHS: 06035
Received: 0000019876
Accepted: 0000012974
Per Minute: 082.47
Efficiency: 065.27%
Up Time: 0d,02h,37m,19s
The only other thing I can think of is you network. The IP address of your proxy has me a bit perplexed...I've not seen that IP range in a consumer router before. I put all my mining equipment on a separate simple Linksys router so its all on its own network. If nothing else, you may have just gotten a bad blade and you need to get it exchanged. This is a network at work. 10.x is a non public network like 192.168.x and 172.16.x You don't use 192.168.x on work networks unless your IT Staff are buffoons. It makes it easier to type and recognize DMZ with 10.1.x 10.2.x etc isolation. I am pretty sure these are also plugged into the same switch, but I may be wrong. If not in the morning I will get them on the same switch and then also test it with a 650watt power supply. I tried it with an isolated Dell 375 watt power supply and that made no difference than one running a pc. It shouldn't matter if its running a pc or not, the pc's draw is essentially nil. it's specs dictate it has more than enough power. I've read the OLD Blades over clocked draw 10amps, so these new ones locked at 10gh/s cant be drawing more than 10amps. These power supplies were powering sapphire 7870xt at max for months with no issues. They pull a max of 140 watts. 140/12 =11.67amps. So this is why I can not accept this is a power issue. Output +5V ====/22A MAX -12V ====/1A MAX +5V(FP) ====/2A MAX +3.3V====/17A MAX +12VA====/18A MAX + 12VB===/18A MAX thanks for the help, really hope the 650watt fixes it but I highly doubt it will otherwise this are going back... |
|
|
|
Ugh, slushy you need a freaking "withdraw now" button...
5 hours and no pay after threshold, anyone else having this issue? I just received a pay out |
|
|
|
|
Show Posts
