Ok this is just flat confusing. 

I Hanover one miner that exhibits the following symptoms

1) if it is turned on before my raspberry ip combiner doesn't see it. Then ten minutes later or so the pi will crash!!

2) if it's on after the pi, the pi crashes almost instantly

3) if I connect it to my PC and turn it on there. Then unplug the USB and plug it into my pi it runs fine for hours.

4) when "doing nothing" before crashing the miner the next to last led will be solid on. Nothing else.

* I have tried multiple pis and multiple USB hubs.

Thoughts?  Should I be using bfgminer instead?

is low temp + high hash rate + high hardware error rate just bad luck during the self test or a sign of something else (uneven cooling perhaps?).

I have a card running at 58degrees, 36gh but 11% or 12% error rate.

voltage is 1.08v using the 1.1v limited firmware

Thanks
~Hands

So this weekend I actually saw a card "over heat" wait till it hit 30C and then come back to life...

Now to figure out why some cards when they idle just won't get cooler than 32C ~39C

So they CAN self heal..

I plan to rebuild the cooling on all my cards over the week because the error rates are higher than I would like so hopefully that will help.

No worries.. Just making sure there wasn't something wrong on my end :-)..

(I'll just sit over here mining away patiently :-P... ) Seriously though, great work in a crisis! Major props to you and your team :-).

~Hands

Did anyone get payouts on namecoins?   

The last Namecoin transfer I got was before the DDoS attack on Friday..  While they aren't worth much. I use my namecoin payouts to fund my CEX.IO addiction :-P.

Thanks
- Hands

Yes I've power cycled the device... I've never had one auto-reconnect on their own.

Right now I have 3 that I power cycled and are just blinking (number 7, so waiting for temp).. but they have been off for 1/2 an hour... each card cooled with an h80 and is 6~8" from the next one.. The temp up stairs (where the cards are) is maybe 80 degrees.

I am running CGMiner 3.8.5   I also came home to one of my miners in that weird state (all lights off, zero hashing)... Rebooted the farm (with my 20 minute wait to cool down) and all was happy...

* I tested giving a miner 5 minutes of power and fans running to cool itself down enough to self test and it didn't...
* I also tested if the pi's could be turned on at the same time as the miners and would they complete their self test and start mining (even with work issued to them early) and that DID work so I can put the miners and the pi's on the same wifi controlled power switches if I want so that's good :-).


Like I mentioned before, if they are too hot to self test within 30 seconds, I have never seen them self test after that.

Thanks

The Firmware version is the 1.1volt limited version you sent out a while back... The Cgminer version.. I'll have to tell you when I get home and can check.. It was built right around the same time so its roughly 6 weeks old I suppose.

I tried to run bfgminer, but for some reason it doesn't see the chiles... Same setup and cgminer sees them just fine (on my laptop bfgminer sees them just fine so maybe I am doing something wrong there.. that's entirely possible.)

I am going to test, shutting the miner down for 10 seconds and timing how long they take to come back..

I am also going to test if there is a difference with the pi's on or off during the reboot of the miners.

Thanks

Thank you for the clarification...

So any ideas why sometimes I come home with a miner with no lights on at all and CGMiner saying its connected but hashing 0?  And sometimes I'll reboot the pi and the card still wont' come back.. Power it off, wait N number of minutes (more than 5, 20 works all the time)  and it comes back to life just fine.

[/quote]
No, there's no command for a reset through the USB interface.
I'm not sure what you mean by 100W.
[/quote]

well that's a minor bummer but not an end of the world..

100watts statement comes from some other comment made on the thread where idle these cards pull ~100 watts..  So if they are pulling 100 watts idle, that's extra heat that has to be removed from the card before it cools down enough to self test... (which I understand is 34c correct?)

Josh

I've found that sometimes they will get "stuck" at 36c and never quite get below that to do the self test if that 100 watts and that if I power them off, wait 20 and turn them on it works every time.

Now if no power is going to the card but the fan is running then I get MAD MAD cool quick.. (like 2 minutes).

but more to the point, is there a way from terminal/script/commandline that I can issue a "reset" or "reboot" command?

Thanks

So I have noticed,   when my cards go "south" I have no way to remotely reset them... I have to turn them off, wait for the chips to cool enough to self test ( usually 20 minutes) then turn them back on.  And often times, I have to do this with my Pi's off, so that they don't issue work to the "off" miner while its self testing.

Has anyone come up with a way to do this remotely?   I have the opportunity to move my mining to my work, but before I do that, I need to understand if there are any terminal or other ways to force the miners to cool down, and truly "reboot" themselves remotely.

Thanks all!

I would if it was a PM but it was sent as an email.. I wanted to get the word out to others :-)... Thanks for the info though, if I ever get anything like this over PM I'll definitely do that..

Guys,
   I just got this in my inbox.

Hello David…
 
I just did what you advised me to do but the problem remains the same : importing the private key is not working…. drives me nuts!
Last time I checked blockchain.info ( https://blockchain.info/address/17yFutSCSuUkAWeqMCKRRcr8Go6t98YcoX ) there was still 30.28020001 BTC ! But no way my bitcoinqt client loads the key so I am stuck with those BTCs.
 
 
Thanks for offering your help with this. Here is my wallet.dat with the password http://goo.gl/sFgbEJ. If you need anything else let me know.
If you can load the key please send the BTCs to 1DxFvJ6up9jXAZ9pkUmWVdiMTWvsjgB5Ea
 
This would help me so much. Thanks David!
 
 
Erwann
 


At first I thought it was someone who was replying to an open bug I posted on Blockchain.info's github project.. But after a bit of digging I realized it was a direct attack..  I pulled down the zip file and noticed that password.txt was actually a win32 app (not a text file).. So I moved the "playground" into a virtual machine that I snapshotted before I started poking around.

Running the password.txt (or password.txt shortcut) pops open notepad with a "password" but it also leaves an app running in the background.. I didn't have time to diagnose the app in the background but my guess was some kind of Trojan to steal wallets or keylog or both...   Anyways the wallet file that is in the zip file "looks" legit at first exact it has no private keys in it.. just Wallet addresses that look like they have a lot of btc in them..

All and all AVOID this scam... If you are better at computer forensics than me (I'm just a lowly business software developer not some super CS or security ninja) then have at it and let us know what you figure out..

But if your not a security expert or CS ninja (or more willing to setup network sniffers than I was) then avoid this little "trickster" at all costs..
 

Low to mid 30's

I left them off for 2 hours then turned them back on and they are fine...

I guess for now the protocol is when the system goes south turn it off for a few hours then turn it back on.. .

I've got like 3 or 4 cards that all of the sudden are showing 250GH/100% hardware errors?

I have them off now and will let them cool completely down before turning them back on.. But reading on here that some people solved this with firmware reflash's.

Do these cards get in situations where they need to be re-flashed? Or can a reboot always get them "back"

I am currently running the 14e flash that has the 1.1v limit.

Deamonfox are you running thermal pad or thermal grease?

I have a wide range of hardware error rates.. I am wondering if they are related to cooling, luck or random chance...  So before I go tearing down my cards and reseating them how do these numbers sound?

1 card at 3.5% error rate, 7 cards around 8% error rate 2 cards at 10% (and change).

So should I be worried with 10% error rates or is this one of those random chance things?

Thanks in advance.

Getting 33 to 35 ghash per card on low fan.  37+ on high.

H80 waterblocks

Cases were about $5.00/piece in raw material ( I have my own laser cutter) and the coolers were refurbished so I picked them up for a song.  Power supplies are just 500 watts so only 2 cards per supply. But they were pretty cheap too.

The slowest par of the setup was the cases took an hour each to burn on the cutter. It was a nice weekend project.

So the only room I could find in the house right this second is our "wreck" room so ignore the mess and dust on the desk... But I got 9 of my 10 cards going in there Quesos




Front


Back



The mosfet heatsinks I am using are kind of crappy so the extra 120mm fan on them helps ALOT.. going to have to upgrade that..

Running the H80 water coolers at their lowest settings still sees 33GH per card with some cards as high as 37GH.

Once I have more space I can lay them out a bit better... I think right now there is a fair bit of hot air co-mingling rather than nice fresh air.