[2022/05/17 21:20:01] INFO: chain[0] ->
[2022/05/17 21:20:01] INFO: domain[9] - set freq to 595 Mhz
[2022/05/17 21:20:01] INFO: fixed (unbalanced=0, unstable=1)
[2022/05/17 21:20:01] INFO: chain[1] ->
[2022/05/17 21:20:01] INFO: ok
[2022/05/17 21:20:01] INFO: chain[2] ->
[2022/05/17 21:20:01] INFO: ok
[2022/05/17 21:21:51] INFO: =[ Tuner ]==============================
[2022/05/17 21:21:51] INFO: Starting auto-tuning
[2022/05/17 21:21:51] INFO: Preset: Profile 36Th @ 600MHz
Ok, so what the tuner is telling you is that chain 1 and 2 were tuned successfully but then chain 0 had an issue with at least 1 chip, and thus it's trying to reduce the frequency of that hash board to get to a stable point, that also perfectly matches what wndsnb mentioned about one of your hash board showing a temp sensor error in the kernel log you posted earlier.
Eventually, the tuner might get it to a stable stage, but that could take very long and thus you are better off manually setting the frequency, use 600MHz on the two good boards and start with the lowest frequency on the bad board, and then slowly increase it until it becomes stable, keep in mind that sometimes even with the lowest frequency the hash board won't hash well which means you will need to unplug so that it does not affect the other two hash boards.
On a side but related note, the two working boards seem to do very well with a frequency of 600MHz, which means you could probably increase it, that gives you more hashrate and of course more heat, so you need to find that perfect spot.
Hi Mike. Thanks for the time spent debugging my log. Yes, I did exactly that and sat the freq to 690 and volt to 16.3. It has been running smoothly for a day hashing away at 38T and drawing 2kw. More details here:https://imgur.com/a/gynUI5j. Are you happy with this?
I have two red chips on chain 0. The moment I play around with them to get them to at least an orange, I keep getting the same error as the tuning. I decided to let them be. Are you happy with these numbers? Thanks again.