Yeah... I saw that post earlier...

so.much.work.

Plus I don't have one of these, "ubuntu 12.10 32bit linux server install".

Any other suggestions or comments on this issue I am having?

First of all, a big thanks to Dogie for the setup guide.

I'm looking for the collective wisdom on the best fan replacement for the Cube. I am looking for one as quiet as I can get it while moving enough air to run in overclocked mode. Specific model recommendations would be dandy (I read earlier in the thread that someone recommended a Scythe Gentle Typhoon model), but even knowing the minimum CFM rating it needs would be very helpful.

I have a problem with my cube

I have taken it all apart and tightened the heatsink screws and re seated the boards

It runs off a Corsair cx750 M

It will run for a undetermined time and re set itself ( Here a clicking sound ) Exact same sound as when it starts on

Normally runs for around a couple of hours before this happens

There are no errors on the chips all say 0000000

Running at 93% efficiency

I know a few of you are having the same problem but I couldn't see the cause or solution to this If anyone can help me I would be most gratefull

I use the AX860i's to power two cubes each; no issues.  Someone stated it was a GS (Gaming Series) that did it; sounds now from your experiences that it could just be a bad Corsair power supply that's failing (the GS).

You could substitute the 1st DNS setting for your *actual* DNS, but going through 192.168.1.1 as an intermediary is still NOT likely enough to cause the slowdown your seeing.

I've gotten low rates like this before when there's a "bad actor" on the net - some device not playing nice on your local network.  Have you don't the remove-all-other-net-devices check I recommended way back in the thread?

Running these through an additional network layer like a cloud architecture would not be my first inclination.  They are extremely sensitive to network environment - the slightest preferential QoS setting, noise on the lines, android-phone-hogging wifi, etc, can drastically cut into your hashrate.  That said, I have been able to run 7 Cubes and 2 Blades over 500 MBs PowerLine modules from ActionTek, but ONLY after removing a somewhat misbehaving router that was sharing the subnet.  It worked fine for other computers and such, but while it was on the net, not even direct wired Cube/Blade hashing was reliable.

if anyone has fixed the random restarting please tell me I will pay a donation I have 3 restarting cubes and I have reasembled them all with no fix please help

Random restarting happens under two conditions that I've seen - one power related (see the rest of this thread for ideas on how to solve power sensitivities), but the other is when the device is pointed to two instances of the same proxy if your network has any appreciable traffic.  When it gets "confused" it tries the other proxy, which is the same if you're not running two separate copies, so then it stays confused, stops processing work, and then the device does the auto-reboot when it notices it's been without work.

I solved this second type by running two separate proxies, and having it switch between the two.  This approach works for two mining_proxy (slush's proxy program) instances, but if you're using bfgminer, I've found the better solution is to have the second pool point to a port that is not active (but is on a real machine on your network - it could just be the same ip address but a different, unavailable port, say 8425 or some such), so it bounces after enough time to get unconfused (a mere hiccup), and then it gets back to hashing.

Well, I can tell you that 60 CFM is not quite enough.


Whatever fan you decide on, make sure it has the standard three pins.  Please share your experience.