The cost of 15 minute boot time is pretty much what the t17 takes in the first place.
socket connect fail is also normal
So you are looking good .
Topic: New Antminer T17 issues - page 2. (Read 869 times)
I didn't because i don't think its neither hashboard or PSU problem. Here is why:
I have contacted Bitmain support. They have provided me with newest firmware: Antminer-T17 +-user-OM-202002281759-sig_5446.tar.gz - File System Version - Fri Feb 28 17:59:06 CST 2020
Previous system was File System Version Fri Dec 6 10:46:34 CST 2019
Outcome is that each time machine boots i get an: Hardware Version Socket connect failed: Connection refused ; And machine takes like 10-15 minutes to start hashing. However now it works well, all 3 hashboards are visible and 1 of them doesn't disappear anymore. I tried re-flashing board with sd card with zip file Bitmain sent me. However didn't manage to do it, both leds remain on for 30 mins, and nothing happens. Machine boots normally after SD card is removed. I also tried factory reset few times. I tried downgrading firmware to 2019 version but it won't let me go back.
So long story short, i fixed the problem with new firmware at the cost of machine taking 15 mins to boot which im fine with. Hope my experience helps.
I have contacted Bitmain support. They have provided me with newest firmware: Antminer-T17 +-user-OM-202002281759-sig_5446.tar.gz - File System Version - Fri Feb 28 17:59:06 CST 2020
Previous system was File System Version Fri Dec 6 10:46:34 CST 2019
Outcome is that each time machine boots i get an: Hardware Version Socket connect failed: Connection refused ; And machine takes like 10-15 minutes to start hashing. However now it works well, all 3 hashboards are visible and 1 of them doesn't disappear anymore. I tried re-flashing board with sd card with zip file Bitmain sent me. However didn't manage to do it, both leds remain on for 30 mins, and nothing happens. Machine boots normally after SD card is removed. I also tried factory reset few times. I tried downgrading firmware to 2019 version but it won't let me go back.
So long story short, i fixed the problem with new firmware at the cost of machine taking 15 mins to boot which im fine with. Hope my experience helps.
Did you manage to find any fix to this issue? One of my T17+ machines is acting the same. I get the same info in log, 1-2 hours of mining one of boards stops hashing. After a reboot it works fine for few hours then issue repeats.
Have you tried the other solution above? If you confirmed that the PSU is good then I would like to suggest moving the miner on the other outlets or plug the miner directly to the wall outlet then test it again.
Because sometimes extensions can't handle high wattage and can't give enough power to the miner.
Did you manage to find any fix to this issue? One of my T17+ machines is acting the same. I get the same info in log, 1-2 hours of mining one of boards stops hashing. After a reboot it works fine for few hours then issue repeats.
If you confirmed that all 3 hash boards work just fine, i think it would be best to buy a new PSU, for two main reasons. First one is this PSU is not good and it could damage the hash boards eventually, so there is a good amount of risk in keeping it. The second reason is economically based, T17 40th makes about 6.3$ a day (before electricity bill) so every board makes a good 60$ a month, T17 PSU costs 134$, say 30$ for shipping. you are looking at about 160$. If your power cost is 5 cents then PSU ROI will be about 5 months.
if you decide to keep on mining with only 2 boards, at least sell the other one that's sitting there doing nothing. Just 2 two sats.
if you decide to keep on mining with only 2 boards, at least sell the other one that's sitting there doing nothing. Just 2 two sats.
... So using 2 boards may be your best choice.
I'm starting to think the same.. i guess the last attempt is to disassemble the PSU and look for any obvious damage.
Thank you both!
UPDATE:
I disassembled the miner and disconnected the power from Chain [2], now the miner works fine, including Chain[0] which had the problem before, does this mean that there is a power problem ?
I disassembled the miner and disconnected the power from Chain [2], now the miner works fine, including Chain[0] which had the problem before, does this mean that there is a power problem ?
This is a good sign that all 3 boards are still good, here are the three possible reasons.
1- Voltage:
if you are not feeding the miner with 200-240v it could act weird and not be able to power on 3 hashboards.
2-PSU is dying:
Due to unregulated voltage or simply bad luck, the PSU can't feed enough power for all boards
3-The data-cable
Make sure you test all three of them by swapping them.
also can you tell us what is the exact voltage you plugging the miner to? please notice these new gears take voltage very seriously, anything above 240v or below 200 vots is simply a free ride to RMA.
By disconnecting 1 of 3 boards you may have shifted the board counter over
Hard to tell exactly what you did.
If you could disconnect two boards and boot and do full code of log
then do two boards again show full log
then do two boards again show full log.
each time you do this make sure
board 0 on first try is connected
board 1 on second try is connected
board 2 on third they is connected.
if you always get 1 board to work and if it is a different board each time you may not have a board issue.
then try with 2 boards connected make board 0 disconnected
try 2 boards connected make board 1 disconnect
try 2 boards connected make board 2 disconnect
if you always get 2 boards to work you may not have a board issue
lastly try all three and if board zero does not work I suspect the psu which means order a psu
https://shop.bitmain.com/product/detail?pid=0002019072316001724716dkNtX50679
looks like it is sold out may need to wait til feb to get one.
https://hmtech.co/ is in use they got me a psu for my m20s from whatsminer maybe they have a t17 psu
but do the trouble shooting before you buy a psu.
There is a cost analysis since you are getting 2 boards to work right now spending 200 for a psu many not pay off.
If you are off 14 th that is about 2 dollars a day with free power if your power is a dollar it is a dollar a day so a 200 dollar psu will take 200 days to pay off. The ½ ing comes in 120 days. So using 2 boards may be your best choice.
Hard to tell exactly what you did.
If you could disconnect two boards and boot and do full code of log
then do two boards again show full log
then do two boards again show full log.
each time you do this make sure
board 0 on first try is connected
board 1 on second try is connected
board 2 on third they is connected.
if you always get 1 board to work and if it is a different board each time you may not have a board issue.
then try with 2 boards connected make board 0 disconnected
try 2 boards connected make board 1 disconnect
try 2 boards connected make board 2 disconnect
if you always get 2 boards to work you may not have a board issue
lastly try all three and if board zero does not work I suspect the psu which means order a psu
https://shop.bitmain.com/product/detail?pid=0002019072316001724716dkNtX50679
looks like it is sold out may need to wait til feb to get one.
https://hmtech.co/ is in use they got me a psu for my m20s from whatsminer maybe they have a t17 psu
but do the trouble shooting before you buy a psu.
There is a cost analysis since you are getting 2 boards to work right now spending 200 for a psu many not pay off.
If you are off 14 th that is about 2 dollars a day with free power if your power is a dollar it is a dollar a day so a 200 dollar psu will take 200 days to pay off. The ½ ing comes in 120 days. So using 2 boards may be your best choice.
The miner is just over a month old and is showing issues with Chain[0].
The kernel log shows the first error:
Then it shuts down that chip, and gets stuck in retrying to check temp.
It worked normally a few weeks ago, and even worked with 2/3 chips yesterday with 2/3 hash rate.
I have followed the five steps in the first post on this website but still nothing.
Could anyone help ?
UPDATE:
I disassembled the miner and disconnected the power from Chain [2], now the miner works fine, including Chain[0] which had the problem before, does this mean that there is a power problem ?
The kernel log shows the first error:
Code:
temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 0
Then it shuts down that chip, and gets stuck in retrying to check temp.
It worked normally a few weeks ago, and even worked with 2/3 chips yesterday with 2/3 hash rate.
I have followed the five steps in the first post on this website but still nothing.
Could anyone help ?
Code:
2020-01-15 11:31:28 thread.c:105:pic_heart_beat_thread: chain[0] heart beat fail 5 times.
2020-01-15 11:31:30 power_api.c:86:get_average_voltage: chain[0], voltage is: 0.000000
2020-01-15 11:31:32 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.781328
2020-01-15 11:31:33 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 1
2020-01-15 11:31:35 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.001758
2020-01-15 11:31:35 power_api.c:97:get_average_voltage: aveage voltage is: 11.927695
2020-01-15 11:31:35 power_api.c:110:check_voltage: target_vol = 17.90, actural_vol = 11.93, more than 1.0v diff.
2020-01-15 11:31:36 power_api.c:124:check_voltage_multi: retry time: 6
2020-01-15 11:31:40 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 0
2020-01-15 11:31:48 power_api.c:86:get_average_voltage: chain[0], voltage is: 0.000000
2020-01-15 11:31:50 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.787451
2020-01-15 11:31:53 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 1
2020-01-15 11:31:53 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.014004
2020-01-15 11:31:53 power_api.c:97:get_average_voltage: aveage voltage is: 11.933818
2020-01-15 11:31:53 power_api.c:110:check_voltage: target_vol = 17.90, actural_vol = 11.93, more than 1.0v diff.
2020-01-15 11:31:54 power_api.c:124:check_voltage_multi: retry time: 7
2020-01-15 11:31:54 thread.c:642:check_temperature: over max temp, pcb temp 69 (max 80), chip temp 107(max 103)
2020-01-15 11:31:54 driver-btm-api.c:201:set_miner_status: ERROR_TEMP_TOO_HIGH
2020-01-15 11:31:54 driver-btm-api.c:142:stop_mining: stop mining: over max temp
2020-01-15 11:31:54 thread.c:824:cancel_temperature_monitor_thread: cancel thread
2020-01-15 11:31:54 thread.c:834:cancel_read_nonce_reg_thread: cancel thread
2020-01-15 11:31:54 driver-btm-api.c:128:killall_hashboard: ****power off hashboard****
2020-01-15 11:31:56 thread.c:105:pic_heart_beat_thread: chain[0] heart beat fail 6 times.
2020-01-15 11:32:10 power_api.c:86:get_average_voltage: chain[0], voltage is: 0.000000
2020-01-15 11:32:12 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.775205
2020-01-15 11:32:15 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.007881
2020-01-15 11:32:15 power_api.c:97:get_average_voltage: aveage voltage is: 11.927695
2020-01-15 11:32:15 power_api.c:110:check_voltage: target_vol = 17.90, actural_vol = 11.93, more than 1.0v diff.
2020-01-15 11:32:16 power_api.c:124:check_voltage_multi: retry time: 8
2020-01-15 11:32:29 thread.c:105:pic_heart_beat_thread: chain[0] heart beat fail 7 times.
2020-01-15 11:32:30 power_api.c:86:get_average_voltage: chain[0], voltage is: 0.000000
2020-01-15 11:32:32 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.799697
2020-01-15 11:32:35 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.050742
2020-01-15 11:32:35 power_api.c:97:get_average_voltage: aveage voltage is: 11.950146
2020-01-15 11:32:35 power_api.c:110:check_voltage: target_vol = 17.90, actural_vol = 11.95, more than 1.0v diff.
2020-01-15 11:32:36 power_api.c:124:check_voltage_multi: retry time: 9
2020-01-15 11:32:48 power_api.c:86:get_average_voltage: chain[0], voltage is: 0.000000
2020-01-15 11:32:50 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.799697
2020-01-15 11:32:53 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.050742
2020-01-15 11:32:53 power_api.c:97:get_average_voltage: aveage voltage is: 11.950146
2020-01-15 11:32:53 power_api.c:110:check_voltage: target_vol = 17.90, actural_vol = 11.95, more than 1.0v diff.
2020-01-15 11:32:54 power_api.c:124:check_voltage_multi: retry time: 10
2020-01-15 11:32:56 thread.c:105:pic_heart_beat_thread: chain[0] heart beat fail 8 times.
2020-01-15 11:33:07 power_api.c:86:get_average_voltage: chain[0], voltage is: 0.000000
2020-01-15 11:33:08 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.799697
2020-01-15 11:33:10 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.050742
2020-01-15 11:33:10 power_api.c:97:get_average_voltage: aveage voltage is: 11.950146
2020-01-15 11:33:10 power_api.c:110:check_voltage: target_vol = 17.90, actural_vol = 11.95, more than 1.0v diff.
2020-01-15 11:33:11 power_api.c:124:check_voltage_multi: retry time: 11
UPDATE:
I disassembled the miner and disconnected the power from Chain [2], now the miner works fine, including Chain[0] which had the problem before, does this mean that there is a power problem ?
Jump to: