Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Sorry about the annoyance with code format 
but im still a newbie 
, seems as a plausible explanation, as the the power cut only involed one of the two powercords. icould try with a psu from a T17 40 Th would that be sufficient for the test of the faulty T17+ 58th? Upgraded to latest Bitmain orginal FW, and now flashed the awesom SD 2.03.
but im still a newbie , seems as a plausible explanation, as the the power cut only involed one of the two powercords. icould try with a psu from a T17 40 Th would that be sufficient for the test of the faulty T17+ 58th? Upgraded to latest Bitmain orginal FW, and now flashed the awesom SD 2.03.Please use the code function to post kernel logs, it's really annoying and hurts the eyes. 
, use something like this
What the kernel log suggests is that all 3 hashboards have only 44 asics, which means the signal at chip 45 gets interrupted, it is unlikely that all 3 hash boards will have the exact same problem, so my guess is your PSU got a problem, can you test the miner with another working PSU?
, use something like thisCode:
[2020/11/25 14:09:43] WARN: chain[2] - 44 of 65 chips detected
[2020/11/25 14:09:46] WARN: chain[1] - 44 of 65 chips detected
[2020/11/25 14:09:49] WARN: chain[0] - 44 of 65 chips detected
[2020/11/25 14:09:46] WARN: chain[1] - 44 of 65 chips detected
[2020/11/25 14:09:49] WARN: chain[0] - 44 of 65 chips detected
What the kernel log suggests is that all 3 hashboards have only 44 asics, which means the signal at chip 45 gets interrupted, it is unlikely that all 3 hash boards will have the exact same problem, so my guess is your PSU got a problem, can you test the miner with another working PSU?