T17 keeps restarting with no errors in kernal log.

JustaVirus

newbie

Activity: 29

Merit: 16

Quote from: BitMaxz on June 07, 2022, 06:35:16 PM

How did you find the broken hashboard? Did you run them one by one? If you accidentally choose the right one without testing there is a possibility that the true culprit is the PSU.
Maybe PSU is not giving enough power to 3 hashboard so removing one hashboard can PSU provide enough power to 2 hashboard.

Why not try to run the broken hashboard without the two hashboard? To make sure that one is broken?

Hello,
The log I shared was at the start of the issue. Later on, it stopped detecting the first board showing " failed to detect all chips". That's how I decided to remove it.

But I'll remove a "healthy board" and replace the one I think is faulty. If it works, then your theory is right, maybe it was a PSU thing all along.

BitMaxz

legendary

Activity: 3374

Merit: 3095

Playbet.io - Crypto Casino and Sportsbook

How did you find the broken hashboard? Did you run them one by one? If you accidentally choose the right one without testing there is a possibility that the true culprit is the PSU.
Maybe PSU is not giving enough power to 3 hashboard so removing one hashboard can PSU provide enough power to 2 hashboard.

Why not try to run the broken hashboard without the two hashboard? To make sure that one is broken?

JustaVirus

newbie

Activity: 29

Merit: 16

Quote from: mikeywith on June 07, 2022, 01:08:07 AM

Quote from: JustaVirus on June 06, 2022, 04:32:04 AM

Hello,
I rebooted, reset, but it keeps restarting. I'm using ASIC.to firmware. Autotuning is off. It's been working for 3 weeks straight.

How do you know Autotuning is off? just disabling it on the profile page, doesn't mean it will stop, anyway, go to Miner Configuration > Mining profiles and scroll down, there will be another log, please post that.

I also don't think you need to worry about the health of the hash boards, they read just fine

Code:

[2022/06/06 09:31:30] INFO: chain[2] - 30 chips detected
[2022/06/06 09:31:31] INFO: chain[1] - 30 chips detected
[2022/06/06 09:31:32] INFO: chain[0] - 30 chips detected

Just to directly answer your question, Mike. This detection was a one-time thing. It kept failing to detect the first board ever since. Removing it fixed the issue.
Sorry, I moved to Braiins now and don't have what you asked me to post.

JustaVirus

newbie

Activity: 29

Merit: 16

Quote from: BitMaxz on June 06, 2022, 05:18:14 PM

Quote from: JustaVirus on June 06, 2022, 12:15:29 PM

I noticed that both lights are off. I referred to bitmain page which suggested a faulty board. Is there a way to confirm that?

Since you are using modded firmware from asic.to the only thing that you need to confirm that the board is faulty is by using a test fixture.

And why not try to run the miner again but this time enable the autotuning?

I read the documentation about this asic.to firmware and according to it if it's not mining you can try to enable the "Resolve Dev Fee".

And under "mining profiles", you can see how this miner will shutdown/restart automatically it has only two options either the miner has HW errors more than the value you set or if the hashrate is dropping.

What I would like you to try is to flash it again with that firmware or try to switch to brains OS.

Quote from: mikeywith on June 07, 2022, 01:08:07 AM

Quote from: JustaVirus on June 06, 2022, 04:32:04 AM

Hello,
I rebooted, reset, but it keeps restarting. I'm using ASIC.to firmware. Autotuning is off. It's been working for 3 weeks straight.

How do you know Autotuning is off? just disabling it on the profile page, doesn't mean it will stop, anyway, go to Miner Configuration > Mining profiles and scroll down, there will be another log, please post that.

I also don't think you need to worry about the health of the hash boards, they read just fine

Code:

[2022/06/06 09:31:30] INFO: chain[2] - 30 chips detected
[2022/06/06 09:31:31] INFO: chain[1] - 30 chips detected
[2022/06/06 09:31:32] INFO: chain[0] - 30 chips detected

Hello Mike and Max

Thank you both for your valuable troubleshooting and the time you spent reading about this firmware.
I have flashed it again and used Braiins OS but that did not solve the issue.

The problem was, as Bitmax kindly noted, in one of the hashboard, it was causing this constant rebooting. I have removed it and it's been running smoothly ever since.

I'm now overclocking the crap out of the other two, I don't care if this T17 breaks, it is a really bad model and a waste of a good $1000.

mikeywith

legendary

Activity: 2394

Merit: 6581

be constructive or S.T.F.U

Quote from: JustaVirus on June 06, 2022, 04:32:04 AM

Hello,
I rebooted, reset, but it keeps restarting. I'm using ASIC.to firmware. Autotuning is off. It's been working for 3 weeks straight.

How do you know Autotuning is off? just disabling it on the profile page, doesn't mean it will stop, anyway, go to Miner Configuration > Mining profiles and scroll down, there will be another log, please post that.

I also don't think you need to worry about the health of the hash boards, they read just fine

Code:

[2022/06/06 09:31:30] INFO: chain[2] - 30 chips detected
[2022/06/06 09:31:31] INFO: chain[1] - 30 chips detected
[2022/06/06 09:31:32] INFO: chain[0] - 30 chips detected

BitMaxz

legendary

Activity: 3374

Merit: 3095

Playbet.io - Crypto Casino and Sportsbook

Quote from: JustaVirus on June 06, 2022, 12:15:29 PM

I noticed that both lights are off. I referred to bitmain page which suggested a faulty board. Is there a way to confirm that?

Since you are using modded firmware from asic.to the only thing that you need to confirm that the board is faulty is by using a test fixture.

And why not try to run the miner again but this time enable the autotuning?

I read the documentation about this asic.to firmware and according to it if it's not mining you can try to enable the "Resolve Dev Fee".

And under "mining profiles", you can see how this miner will shutdown/restart automatically it has only two options either the miner has HW errors more than the value you set or if the hashrate is dropping.

What I would like you to try is to flash it again with that firmware or try to switch to brains OS.

JustaVirus

newbie

Activity: 29

Merit: 16

Quote from: BitMaxz on June 06, 2022, 11:39:42 AM

I don't know how asic.to firmware works there might be different logs and the errors might be on the other logs like API logs..

If you want us to troubleshoot the issue with this unit I suggest you revert it back to the original/stock firmware so that you can get the errors under kernel logs.

I noticed that both lights are off. I referred to bitmain page which suggested a faulty board. Is there a way to confirm that?

JustaVirus

newbie

Activity: 29

Merit: 16

Quote from: BitMaxz on June 06, 2022, 11:39:42 AM

I don't know how asic.to firmware works there might be different logs and the errors might be on the other logs like API logs..

If you want us to troubleshoot the issue with this unit I suggest you revert it back to the original/stock firmware so that you can get the errors under kernel logs.

I’d love to but this unit is immersed. Stock fw would be filled with Fan errors

BitMaxz

legendary

Activity: 3374

Merit: 3095

Playbet.io - Crypto Casino and Sportsbook

I don't know how asic.to firmware works there might be different logs and the errors might be on the other logs like API logs..

If you want us to troubleshoot the issue with this unit I suggest you revert it back to the original/stock firmware so that you can get the errors under kernel logs.

JustaVirus

newbie

Activity: 29

Merit: 16

Hello,
I rebooted, reset, but it keeps restarting. I'm using ASIC.to firmware. Autotuning is off. It's been working for 3 weeks straight.

Code:

[2022/06/06 09:25:59] INFO: Power ON
[2022/06/06 09:26:01] INFO: Starting FPGA queue
[2022/06/06 09:26:01] INFO: Initializing hash boards
[2022/06/06 09:26:01] INFO: chain[2] - Initializing
[2022/06/06 09:26:01] INFO: chain[1] - Initializing
[2022/06/06 09:26:01] INFO: chain[0] - Initializing
[2022/06/06 09:26:14] INFO: chain[2] - 30 chips detected
[2022/06/06 09:26:15] INFO: chain[1] - 30 chips detected
[2022/06/06 09:26:16] INFO: chain[0] - 30 chips detected
[2022/06/06 09:26:22] INFO: Start-up temperature is 36 C (min -15 C)
[2022/06/06 09:26:22] INFO: Switching to manual fan control (100 %)
[2022/06/06 09:26:22] INFO: Changing voltage from 17000 to 18500 mV gradually
[2022/06/06 09:27:00] INFO: Raising freq from 50 to 500 Mhz gradually
[2022/06/06 09:27:10] INFO: Switching to immersion fan control
[2022/06/06 09:27:10] INFO: Start mining!
[2022/06/06 09:27:27] INFO: Detected 256 Mb of RAM
[2022/06/06 09:27:27] INFO: Switching to immersion fan control
[2022/06/06 09:27:33] INFO: Power ON
[2022/06/06 09:27:35] INFO: Starting FPGA queue
[2022/06/06 09:27:35] INFO: Initializing hash boards
[2022/06/06 09:27:35] INFO: chain[2] - Initializing
[2022/06/06 09:27:35] INFO: chain[1] - Initializing
[2022/06/06 09:27:35] INFO: chain[0] - Initializing
[2022/06/06 09:27:49] INFO: chain[2] - 30 chips detected
[2022/06/06 09:27:51] INFO: chain[1] - 30 chips detected
[2022/06/06 09:27:52] INFO: chain[0] - 30 chips detected
[2022/06/06 09:27:58] INFO: Start-up temperature is 36 C (min -15 C)
[2022/06/06 09:27:58] INFO: Switching to manual fan control (100 %)
[2022/06/06 09:27:58] INFO: Changing voltage from 17000 to 18500 mV gradually
[2022/06/06 09:28:36] INFO: Raising freq from 50 to 500 Mhz gradually
[2022/06/06 09:28:46] INFO: Switching to immersion fan control
[2022/06/06 09:28:46] INFO: Start mining!
[2022/06/06 09:29:17] INFO: Detected 256 Mb of RAM
[2022/06/06 09:29:17] INFO: Switching to immersion fan control
[2022/06/06 09:29:23] INFO: Power ON
[2022/06/06 09:29:25] INFO: Starting FPGA queue
[2022/06/06 09:29:25] INFO: Initializing hash boards
[2022/06/06 09:29:25] INFO: chain[2] - Initializing
[2022/06/06 09:29:25] INFO: chain[1] - Initializing
[2022/06/06 09:29:25] INFO: chain[0] - Initializing
[2022/06/06 09:29:39] INFO: chain[2] - 30 chips detected
[2022/06/06 09:29:41] INFO: chain[1] - 30 chips detected
[2022/06/06 09:29:42] INFO: chain[0] - 30 chips detected
[2022/06/06 09:29:49] INFO: Start-up temperature is 37 C (min -15 C)
[2022/06/06 09:29:49] INFO: Switching to manual fan control (100 %)
[2022/06/06 09:29:49] INFO: Changing voltage from 17000 to 18500 mV gradually
[2022/06/06 09:30:26] INFO: Raising freq from 50 to 500 Mhz gradually
[2022/06/06 09:30:36] INFO: Switching to immersion fan control
[2022/06/06 09:30:36] INFO: Start mining!
[2022/06/06 09:31:07] INFO: Detected 256 Mb of RAM
[2022/06/06 09:31:07] INFO: Switching to immersion fan control
[2022/06/06 09:31:13] INFO: Power ON
[2022/06/06 09:31:16] INFO: Starting FPGA queue
[2022/06/06 09:31:16] INFO: Initializing hash boards
[2022/06/06 09:31:16] INFO: chain[2] - Initializing
[2022/06/06 09:31:16] INFO: chain[1] - Initializing
[2022/06/06 09:31:16] INFO: chain[0] - Initializing
[2022/06/06 09:31:30] INFO: chain[2] - 30 chips detected
[2022/06/06 09:31:31] INFO: chain[1] - 30 chips detected
[2022/06/06 09:31:32] INFO: chain[0] - 30 chips detected
[2022/06/06 09:31:38] INFO: Start-up temperature is 37 C (min -15 C)
[2022/06/06 09:31:38] INFO: Switching to manual fan control (100 %)
[2022/06/06 09:31:38] INFO: Changing voltage from 17000 to 18500 mV gradually

Topic: T17 keeps restarting with no errors in kernal log. (Read 147 times)