Quote from: kano on October 19, 2015, 10:39:37 PM

Quote from: Jethroz on October 19, 2015, 06:36:08 PM

Quote from: Dmc123dmc on October 19, 2015, 05:40:22 PM

Has anybody had issues with Kano's s3 update? The day i moved my 2x s3's here i updated them with Kano's update. I bought anther s3 whilst mining here and it came with an earlier version of the update perhaps. I know it looked different to what i had with my other 2. I left it with that update. Saturday i noticed my hash rate was down a lot. I checked the miners and the most recent one wasn't hashing. There were no values in the status area. I rebooted it and stayed the same. unplugged it for a bit and powered on it was still the same. I did a factory reset through the web GUI and it started hashing again. So I put the latest update on the same as my other 2 and it hashed for a while so i thought problem was solved. I discovered yesterday it had died again sometime after the update. I have factory reset it again and is hashing happily again for the last 2 hours. Any good advice out there?

Noticed over the weekend that my 2 S3s (both /K software versions) started acting strange also but everything seems to be going well this morning. Just glanced at them now and both keep showing less than 10GH/s in the GH/S(5s) box, even though the pool stats show what I should be submitting.

It was, however, enough to plant the S7 seed in my head again...

One cause can be if the time jumps forward - the web/API elapsed will show that.
My update also checks if the time jumps forward more than 70 days and will kill and restart cgminer - that will also come into effect if it has been mining for 70 days.

If the time jumped forward a lot but less than 70 days it would show a low hash rate.
The pool of course will know the corrected hash rate based on the proper time.

The "Share Rate" on the Workers page can also help see that it's working ok - it shows the hash rate for the given short interval "«Elapsed"
It resets every network block, thus shows the shares submitted since then converted directly to a hash rate.
Note also, the "Share Rate" for my antminer cgminer versions will have high variance since I set the internal work difficulty as high as possible to match the pool work difficulty (but of course less than or equal to the pool difficulty)

I noticed it was down on the website. It said the last share was submitted 4 days ago by worker 3. I will leave it a few days and try reinstalling the update. Is there anything i can show you or give to you if it happens again to diagnose the fault? If so i'm happy to help.