Ethash-LowMemory Getting Lot of Rejected Shares

Steve Sokolowski wrote:

romes wrote: Still having issue. Seems if I reboot the miner itll start getting shares and finding blocks without any rejections and then after some time shares will start being rejected. Not sure what the cause is. I've tried several variations of variables in my pass field.

This error implies that your miner isn't responding to the latest work being sent to it. It would still be mining an old job, which the mining servers need to reject because there is no money the pool can make by trying to find old blocks.

Unfortunately, I don't know how to resolve the issue, but I thought this information might be of some help.

Ok. That makes sense.

It seems to be working fine now. I changed the pass field to 'l=4,i=e3_180,a=ethash-lowmemory'

See if that helps. Will keep monitoring. Thanks for the response.

Steve Sokolowski wrote: Unfortunately, I don't know how to resolve the issue

Thats ok. At least I know whats happening now and can monitor it and reboot it when it gets stuck on a job. Much appreciate your honest answer.

Steve Sokolowski wrote:

romes wrote: Still having issue. Seems if I reboot the miner itll start getting shares and finding blocks without any rejections and then after some time shares will start being rejected. Not sure what the cause is. I've tried several variations of variables in my pass field.

This error implies that your miner isn't responding to the latest work being sent to it. It would still be mining an old job, which the mining servers need to reject because there is no money the pool can make by trying to find old blocks.

Unfortunately, I don't know how to resolve the issue, but I thought this information might be of some help.

Any idea about my problem?

That pass field change seems to maybe have solved my issue. I will continue to monitor but its been hashing away flawlessly since I made that change.

romes wrote: That pass field change seems to maybe have solved my issue. I will continue to monitor but its been hashing away flawlessly since I made that change.

Ok maybe not heh. I'll just continue to monitor and restart when its stuck on a job.

I may have resolved it. We'll see. I had older firmware and it looks like this firmware upgrade may have solved my issue.

Btw, this issue was resolved with firmware upgrade. Also, for those with an E3 who try to upgrade the firmware, Bitmain will provide instructions how to do so using a 4GB micro SD card. However, this is not needed. All you need to do is ssh into the miner using linux terminal OR Putty if using windows, and delete the core file which is preventing the firmware from being able to be uploaded due to not enough space. Here is a youtube video on how to do this. https://www.youtube.com/watch?v=Xafo-iFdMDk