Topic: Cube and Blades restarting every 5 minutes. (Read 851 times)
I recently had the same issue running one cube. I fixed it by adding a secondary IP address to my proxy machine and pointing the backup pool in the cube config to that address. Check out my thread for more info https://bitcointalksearch.org/topic/solved-be-cube-keeps-restarting-proxy-issue-418856
Well, i've got on v2.01 blade which wil only hash @ 6gh when... wait for it... wifi is on on my htc sensation.. Switching off the wifi on my phone and restarting the blade made it go up to the full 10gh!
I had a similar issue with BE cube.
The cube (or the proxy) needs some minutes to get enough work to hash at full speed. The more work the cube gets the more power it consumes. And then the PSU switches off because of overload.
Make sure that you don´t use to much power per 12V. Even if the PSU has 1 billion watts: To much Ampere over one 12V lets the PSU reset / switch off.
Sorry for my bad english.
The cube (or the proxy) needs some minutes to get enough work to hash at full speed. The more work the cube gets the more power it consumes. And then the PSU switches off because of overload.
Make sure that you don´t use to much power per 12V. Even if the PSU has 1 billion watts: To much Ampere over one 12V lets the PSU reset / switch off.
Sorry for my bad english.
There might be hardware issue.
Try to use a cooler instead
Try to use a cooler instead
How about running just one device (say, the cube) by itself off of your power supply and see how it acts. Or just one of the blades. Whichever, you choose. If it runs steady by itself, then add another device until your issue returns.
I'm betting that your power supply doesnt have enough juice and/or isn't designed correctly to handle everything going at once. What PSU are you using exactly?
I'm betting that your power supply doesnt have enough juice and/or isn't designed correctly to handle everything going at once. What PSU are you using exactly?
I'm thinking it's a proxy issue - part of the programming makes it so the devices (v2 blades and cube) restart when they don't get any work. All three restart simultaneously and the problem is most assuredly not heat related.
Sorry - just noticed you said it wasn't heat related. Okay; I too use Slush's proxy... I however, have a separate proxy for each cube because I became tired of troubleshooting issues related to using a single proxy. You could try my setup.
https://bitcointalksearch.org/topic/m.4349054
Hello,
I have two V2 blades and a cube connected to Slush's stratum proxy. The hardware itself seems to be in good shape, all three devices achieve the desired hashrate but after about five minutes - they restart. Every time this happens they need a few moments to get back up to speed and in the process I lose tons of hashes. The blades average out at only about 7.5Gh/s (out of 10Gh/s) while the cube averages only 25Gh/s (out of 38Gh/s), I'm guessing since it takes longer to reach its target rate upon restart.
So far I've tried different pools and exchanged the power supply to see if those could be the problem, but the results were the same. Honestly any information would be greatly appreciated and I'll tip whoever can make this go away. I feel like a noob for not being able to figure this out, but I'm treading in the dark.
I have two V2 blades and a cube connected to Slush's stratum proxy. The hardware itself seems to be in good shape, all three devices achieve the desired hashrate but after about five minutes - they restart. Every time this happens they need a few moments to get back up to speed and in the process I lose tons of hashes. The blades average out at only about 7.5Gh/s (out of 10Gh/s) while the cube averages only 25Gh/s (out of 38Gh/s), I'm guessing since it takes longer to reach its target rate upon restart.
So far I've tried different pools and exchanged the power supply to see if those could be the problem, but the results were the same. Honestly any information would be greatly appreciated and I'll tip whoever can make this go away. I feel like a noob for not being able to figure this out, but I'm treading in the dark.
It's likely a heat issue, have you checked that? If the cubes get hot, it's likely to reboot to cool off... are you running it in High or Low mode? If High, does it change running in Low? If it's Low, is the air that's being sucked in cool or warm? You can try putting it a cooler area of your home or other cool location. Sucking in air isn't enough, it needs to suck in 'cool' air....
As a test, you can set one in your window (if it's cold where you are) and it's not wet outside... have it suck in the cold air and exhaust into your home. If it doesn't shutdown, then snap... you found the problem, heat. My $0.02.
What kind of power supply do you have them on? Oddly enough I am running a cube and two blades myself with no problems. I am using the mining_proxy.exe on Slush's
Sounds power related to me.... Also is it showing hardware errors?
Woodser
Sounds power related to me.... Also is it showing hardware errors?
Woodser
I'm thinking it's a proxy issue - part of the programming makes it so the devices (v2 blades and cube) restart when they don't get any work. All three restart simultaneously and the problem is most assuredly not heat related.
Do they restart regularly after a set amount of time?
My first guess would be heat.
My first guess would be heat.
also are they both resetting together simultaneously?
Do they restart regularly after a set amount of time?
My first guess would be heat.
My first guess would be heat.
Hello,
I have two V2 blades and a cube connected to Slush's stratum proxy. The hardware itself seems to be in good shape, all three devices achieve the desired hashrate but after about five minutes - they restart. Every time this happens they need a few moments to get back up to speed and in the process I lose tons of hashes. The blades average out at only about 7.5Gh/s (out of 10Gh/s) while the cube averages only 25Gh/s (out of 38Gh/s), I'm guessing since it takes longer to reach its target rate upon restart.
So far I've tried different pools and exchanged the power supply to see if those could be the problem, but the results were the same. Honestly any information would be greatly appreciated and I'll tip whoever can make this go away. I feel like a noob for not being able to figure this out, but I'm treading in the dark.
I have two V2 blades and a cube connected to Slush's stratum proxy. The hardware itself seems to be in good shape, all three devices achieve the desired hashrate but after about five minutes - they restart. Every time this happens they need a few moments to get back up to speed and in the process I lose tons of hashes. The blades average out at only about 7.5Gh/s (out of 10Gh/s) while the cube averages only 25Gh/s (out of 38Gh/s), I'm guessing since it takes longer to reach its target rate upon restart.
So far I've tried different pools and exchanged the power supply to see if those could be the problem, but the results were the same. Honestly any information would be greatly appreciated and I'll tip whoever can make this go away. I feel like a noob for not being able to figure this out, but I'm treading in the dark.
Jump to: