Quote from: allinvain on May 02, 2014, 09:52:26 PM

Anyone encountered an odd issue where all units stop hashing after several days (this happened to me before but now it occurred after 6 days of nonstop hashing)? I use 3 pool with ghash.io as the primary and it seems like the units switch over to the secondary and tertiary backup but never go back to the primary. Even if there was a brief issue with the primary pool they should all eventually retry the primary.

This would not be such a big deal but what is happening is that after some time they units stop hashing even on the backup pools - ie I see no increased share count on any of the pools. The hashrate counter looks like it maintains the same average. It's as if it's hashing into thin air.

The fix is to reboot the units, then they go back to hashing as normal.

All my units are running the Dec 26 firmware except one which is running the Fed 04 one, but it is doing the same thing.

I think this is a firmware bug, but I just wanted to hear if anyone else out there is experiencing the same thing.

Quote from: CosaNostra on May 03, 2014, 06:20:06 PM

Having the same issue with ghash.io, not sure about other pools. Antminer's interface is showing regular hashrate, but not the pool ((( The problem appeared recently -- week or so. Anyone having this sort of issue with other pools?

I'm having the same problem, units are hashing away normally but when checking on ghash it shows no work being done. None of the failovers are showing work being done either, after rebooting the units start showing up on ghash. I've lost too many days to this...going to try using a different pool as primary, see if ghash is the cause.

caution

Posts

Merits