T17+ hashes for 5 minutes then reboots, rinse & repeat

[danieleither]

I have a T17+ 58T which keeps throwing the following error message:

Code:

ERROR: src/chip139x.c:1049 chain[0] - Failed to receive chip replies

The board shows 44 of 44 asics in the log during startup, and runs for around 5 minutes perfectly then throws this error message, followed by the miner rebooting and then running for around 5 minutes again.

I have tried disconnecting the other 2 hashboards so only this hashboard is connected and running, and also tried connecting to a different chain on the controller (with same result).

What causes this?

[BitMaxz]

You should post the whole kernel logs so that we can determine the cause of this issue.

The error above might be a sensor issue not detecting ASIC chip and it stops mining because sensors are failing or it stops mining because of high temp protection.

But if it's running with only one hashboard it sounds like a PSU issue. Do you have extra PSU? If you have then try that first and make sure the source power is around 230v if you running it to 110v this miner won't run properly.

[wndsnb]

Full log would help, but I think it's probably a flaky chip or connection to a chip. I've seen this type of thing multiple times. It's also a pain in the ass to fix since a lot of times the issue is hard to reproduce on a test fixture.

[mikeywith]

This is usually caused by physical damage to that particular hash board, some of its components have toasted, the miner reboots as a result of this, I would just unplug that bad board and keep the other 2 to hash, the miner will stop rebooting when you do that.

With that being said, I have had a bit of luck with custom firmware when such issues show up, and since you lose nothing, give Vnish (AwosmeMiner/Asic.to) a try and see if you get any different results.