Quote from: soy on September 22, 2014, 05:09:29 PM

Quote from: soy on September 22, 2014, 03:50:09 PM

Quote from: soy on September 22, 2014, 01:53:48 PM

Quote from: soy on September 22, 2014, 12:54:30 AM

Yes, this is better. Before it barely got up to 435GH/s with the low hashing board on the right side when looking at the RJ45 connector end. The right side is the top chain and generally has the higher temperature and faster fan. In this case it had lower temperature and slower fan than the lower chain. So, taking the end plates and their fans, swapping ends and moving the controller board, put it back the way it was shipped, the questionable board on the cooler side.

Almost right away the average went above 441GH/s and has remained above 440GH/s for the last 3h 23m and is presently 442.04 tho the utility is only 15. No hardware errors in that time. It was started as the afternoon cooled. It remains to be seen what happens tonight as the humidity increases.

Oh well. A minor improvement over yesterday morning and there's even greater humidity as it rained. This morning the problem S3 is hashing at 434.15GH/s. A nice improvement over finding it down at 419GH/s in the AM. Guess I'll just have to settle with this hashrate. The good S3 immediately next to it is at 440.85.

...1½ hrs after running /etc/init.d/cgminer stop, it restarts automatically after a minute or two, the hashrate of the problem is up to 442.18GH/s(avg). It restarts with a fresh Elapsed duration. So, I'll schedule this to run middle of the night and again in the AM.

Okay, I see this problem has been address in message #482 this forum with cgminer-avg-monitor script. Kudos.

Okay, have written/modified the scripts and changed scheduled tasks. By the time I was done the hashrate was down to 435.09GH/s So, in about 22 minutes the script will run and it should restart leaving a record in /usr/bin/avg.log. Nah, will try running from the command line...failed, typing errors I presume.

Okay, the lower case L was actually a one. Runs fine.

darn, restarted with an x at position 8 of the 16 representing the problem board.

A cold reboot with the machine off a minute allowed it to wake to 441.05GH/s and the x gone. An x in the 8 position can only be in the center of the board if upper left ASIC is 1, lower far left ASIC is 2, second upper left ASIC is 3, etc. This would put the eighth position of the chain at the center left bottom ASIC. Next time I take it one apart I'll look at the component numbering and finding a component common to each ASIC, see how they progress. Who knows, the ASICs themselves might be numbered.

Up 11 minutes and there's an x in a different position, now in the #2 position of the top chain.