BE Blade, not working right!!

[Xelpherpolis]

Okay I have setup stratum_proxy!

The blade connects, power is provided.. but it peaks at around 5GH and starts to slowly climb down!

For example


Total MHS:   00266
Received:   0000000040
Accepted:   0000000008
Per Minute:   003.63
Efficiency:   020.00%
Up Time:   0d,00h,02m,12s


Whats wrong?

The blade is also getting very hot.

[1714912371]

1714912371

[1714912371]

1714912371

[1714912371]

1714912371

[1714912371]

1714912371

[1714912371]

1714912371

[huntsterunc]

can you give us a screeny of your setup?

Is Mining proxy running...and stuff coming down the screen?

[Xelpherpolis]

Yes but it only hashes for around 5 seconds then completely gives up.

[huntsterunc]

Pool?

[Xelpherpolis]

slush stratum.bitcoin.cz:3333 on proxy

[huntsterunc]

I'm running same pool with my blade...

You shouldn't have to run any setup for the proxy.  Just run the program and it automagically does it's thing....assuming you are using Mining Proxy downloaded from Slush's pool.  I'm no programmer, but I suspect it's hardcoded by default to aim at slush's pool...you shouldn't have to specify any params.

Maybe that's it?

The only setup you'll need is pointing the blade setup to your PC.

[Xelpherpolis]

Yes I know I have done all that, the proxy reports the blades hashing, they will reach about 3GH, hash happily for around 3 seconds. Then BAM nothing, the hashing power goes back to 0 and the blade sits there, just getting very hot. All 5 blades are doing the same thing.. Is the PSU I am using.. Antec 750W High Current Pro not good enough for 1 blade test or something?

[huntsterunc]

Check your voltage coming out of the connector from the PSU.  Should be 12v.

If it's not, that could cause it to act all wonky.

[huntsterunc]

Here's mine for good measure...


http://www.clipular.com/c?4559381588869120=phIa0rwo8zlF8OkbG2Ti9FNuD3E&f=.png

[Xelpherpolis]

Exactly the same output there apart from it ceases to hash after 5 seconds sometimes does not even try to hash at all.

[HellDiverUK]

You say it gets very hot.  You do have a fan cooling it, don't you?

I've got a 120mm fan on the front, near the heatsink, and an 80mm fan blowing across the back of the blade.

[Xelpherpolis]

Yeah I have a fan on it, mostly was trying to test without fans each unit in a single power up, but every unit does this weird behaviour of only hashing for around 10 seconds before trying to switch to another proxy. hashes again for a few seconds.. then switches back to the first proxy server.

I have no idea whats going on, its like they are not getting enough work.

[HellDiverUK]

Have you tried mining on a pool that has a getwork interface?  That'd rule out your proxy config. 

[nwoolls]

Yeah I have a fan on it, mostly was trying to test without fans each unit in a single power up, but every unit does this weird behaviour of only hashing for around 10 seconds before trying to switch to another proxy. hashes again for a few seconds.. then switches back to the first proxy server.

I have no idea whats going on, its like they are not getting enough work.

I had this exact problem. Exactly the same. It was the day the forums went down so I was unable to post anything. Basically:

• My Blade would hash against a getwork pool if I entered that into the config page, but top out at maaaaybe 4Gh/s before falling slowly down to 2Gh/s, but would stay mining getwork
• If I set the Blade to use a Stratum Proxy, it was just basically useless. It may submit some work, may hash a bit, but then nothing

I honestly thought I had somehow broken the thing directly after getting it. I tried different PSUs. I tried more or less fans. I tried doing a factory reset of the Blade. Everything I could think of.

I left the Blade hashing against a getwork pool overnight and by morning it was at 10Gh/s. I then started trying the exact same proxy setups that wouldn't work the night before and they all work flawlessly, and have since then.

I know this may not be much help but wanted to let you know others are seeing it. I've also seen it mentioned in the Blade setup thread here.

[Xelpherpolis]

I have finally found out the issue, and thanks for the response guys!

I ordered a new 16port switch with a new cisco rackmount router, and it worked fine. The home brand "BT Business Hub" that I use was throttling the getwork protocol the blades were using. Causing the blades to not get enough work, cease hashing and try a different server. With the new equipment the blades are all hashing at around 10.7 GH/s so my total is now 107 GH with 10 blades

Hope this helps if anyone else encounters this issue.

Also a side tip, have the protocol on a spare server system or pc with 2 network cards, one card used to access the net the other card specifically for the blades switch/hub.

That is how I got the blades finally hashing happily on my own pool and slushs.

[HellDiverUK]

The home brand "BT Business Hub" that I use was throttling the getwork protocol the blades were using.

Those things are a heap of shite.  Even the elcheapo DLink that TalkTalk supplies works fine.  BT's own-brand routers are the worst pile of crap ever to be called a router.

[Xelpherpolis]

Yes they are!!! Such crap