|
January 10, 2022, 10:24:46 PM |
|
Good evening all
I recently purchased 2 s17+ boxes, in used, but good condition (cosmetically anyway). Each was checked on collection and everything seemed to be absolutely fine (30 min test, hashrate as expected, kernel logs 'normal', temps and fans again normal).
Having moved the boxes to their new home (200km drive - well packed) one of the boxes stopped hashing after approx 2 hours and despite best efforts, it has not recovered.
Having restarted the problematic machine, logs indicated 0 asics found on all 3 boards. Reinstalled firmware (June 2020) no change. Contacted Bitmain support and got a link to factory firmware, no change. Updated to latest firmware, no change. Now running Braiins (from SD), no change.
The other s17+ (which this one is installed next to) is running perfectly, so I dont think this can be an environmental issue (box ~58, chips ~72, fans all 3k)
I could understand 1 board failing, but not all 3, and not at the same time?
I do have the opportunity to switch out the hashboards between the 2 units (in case there is a controller or PSU issue) however I do not have much (any) experience with this hardware, and although the process looks relatively straight forward, I am somewhat apprehensive about interfering with the one thats working.
I did try disabling all combinations of hashboards whilst running Braiins, but this made no difference.
Is anyone able to suggest any possible cause for a systemic failure of this nature, or any other practical steps I could take to troubleshoot further?
I can provide current logs if they might be of use (but with my basic understanding, it finds 0 asics on each board and then powers them down). Unfortunately I do not have the log from the first failure.
Thanks
T
|