Topic: S19 Water/Snow Intake Damage (Read 181 times)
I don't think that the stickers block any airflow...
Update - I was able to send the boards out for repair. The boards themselves were fixed as I received the same serial numbers back and I am now getting the expected hash rate.
Dumb question - the boards were returned with stickers on them to show which chips were repaired. Can I leave them on there so I know which chips had issues or will the boards get too hot?
Dumb question - the boards were returned with stickers on them to show which chips were repaired. Can I leave them on there so I know which chips had issues or will the boards get too hot?
Now I see the problem it only detects a few ASIC chips and the hashboard power off if the number of detected chips is lower than the expected number.
Possible few ASIC chips are damaged on that two hashboard or maybe there is a leak/colder joint on a few ASIC chips that need to be reflow with hot air. If you don't have BGA hot air try to use a hair blower and blow hot air to the broken hashboard 3 to 8 minutes and try to run it again.
If you can't find the exact hashboad which one is the broken and working one test them one by one just disconnect the other two hashboard PSU cable and ribbon cable from the control board.
Possible few ASIC chips are damaged on that two hashboard or maybe there is a leak/colder joint on a few ASIC chips that need to be reflow with hot air. If you don't have BGA hot air try to use a hair blower and blow hot air to the broken hashboard 3 to 8 minutes and try to run it again.
If you can't find the exact hashboad which one is the broken and working one test them one by one just disconnect the other two hashboard PSU cable and ribbon cable from the control board.
Thanks for the help.
I believe I have narrowed down the issue to the two hashboards, the good hashboard will show up as 1, 2, or 3 if I swap out the cables on the control board.
I tried cleaning some of the visible corrosion off but still only 1/3 boards is registering on the dashboard.
Looking through the logs, it appears some of the ASIC chips are not being detected.
I believe I have narrowed down the issue to the two hashboards, the good hashboard will show up as 1, 2, or 3 if I swap out the cables on the control board.
I tried cleaning some of the visible corrosion off but still only 1/3 boards is registering on the dashboard.
Looking through the logs, it appears some of the ASIC chips are not being detected.
Code:
===========================================Miner log===========================================
2000-01-01 00:00:09 Miner compile time: Wed Aug 25 17:40:50 CST 2021 type: Antminer S19j Pro
2000-01-01 00:00:10 This is fix-freq version
2000-01-01 00:00:10 Miner compile time: Wed Aug 25 17:40:50 CST 2021 type: Antminer S19j Pro
2000-01-01 00:00:10 commit version: f8df4d3 2021-08-25 17:12:31, build by: jenkins 2021-08-25 17:54:50
2000-01-01 00:00:10 opt_multi_version = 1
2000-01-01 00:00:10 opt_bitmain_ab = 1
2000-01-01 00:00:10 mid_auto_gen = 1
2000-01-01 00:00:10 opt_bitmain_work_mode = 0
2000-01-01 00:00:10 port 51 already exported
2000-01-01 00:00:10 port 49 already exported
2000-01-01 00:00:10 port 48 already exported
2000-01-01 00:00:10 port 60 already exported
2000-01-01 00:00:10 port 47 already exported
2000-01-01 00:00:10 port 27 already exported
2000-01-01 00:00:10 port 44 already exported
2000-01-01 00:00:10 port 22 already exported
2000-01-01 00:00:10 no board pluged in socket 44
2000-01-01 00:00:10 port 23 already exported
2000-01-01 00:00:10 port 45 already exported
2000-01-01 00:00:10 port 46 already exported
2000-01-01 00:00:10 port 26 already exported
2000-01-01 00:00:10 Note: front fan is power on!
2000-01-01 00:00:10 Note: rear fan is power on!
2000-01-01 00:00:10 start the http log.
2000-01-01 00:00:10 httpListenThread start ret=0
2000-01-01 00:00:10 start listen on 6060 ...
2000-01-01 00:00:10 load machine BHB42601 conf
2000-01-01 00:00:10 machine : BHB42601
2000-01-01 00:00:10 chain_num 4, chain_domain_num 42, chain_asic_num 126, domain_asic_num 3
2000-01-01 00:00:15 ==========================capability start==========================
2000-01-01 00:00:15 board num = 3
2000-01-01 00:00:15 board id = 0, chain num = 1
2000-01-01 00:00:15 chain id = 0
2000-01-01 00:00:15 board id = 1, chain num = 1
2000-01-01 00:00:15 chain id = 1
2000-01-01 00:00:15 board id = 2, chain num = 1
2000-01-01 00:00:15 chain id = 2
2000-01-01 00:00:15 ==========================capability end============================
2000-01-01 00:00:15 chain num = 3
2000-01-01 00:00:16 load chain 0 eeprom data
2000-01-01 00:00:17 load chain 1 eeprom data
2000-01-01 00:00:17 load chain 2 eeprom data
2000-01-01 00:00:17 fan_eft : 1 fan_pwm : 100
2000-01-01 00:00:17 create thread get_nonce_and_register_thread
2000-01-01 00:00:17 fixed working voltage = 1360
2000-01-01 00:00:17 Chain [0] PCB Version: 0x0130
2000-01-01 00:00:17 Chain [0] BOM Version: 0x0010
2000-01-01 00:00:17 Chain [1] PCB Version: 0x0130
2000-01-01 00:00:17 Chain [1] BOM Version: 0x0010
2000-01-01 00:00:17 Chain [2] PCB Version: 0x0130
2000-01-01 00:00:17 Chain [2] BOM Version: 0x0010
2000-01-01 00:00:17 Fan check passed.
2000-01-01 00:00:17 uart_trans addr:0xb42df000.
2000-01-01 00:00:18 chain[0] PIC jump to app
2022-01-30 17:44:06 Check chain[0] PIC fw version=0x89
2022-01-30 17:44:07 chain[1] PIC jump to app
2022-01-30 17:44:08 Check chain[1] PIC fw version=0x89
2022-01-30 17:44:09 chain[2] PIC jump to app
2022-01-30 17:44:11 Check chain[2] PIC fw version=0x89
2022-01-30 17:44:11 create thread pic_heart_beat_thread
2022-01-30 17:44:11 max sensor num = 4
2022-01-30 17:44:11 i2c_sim_init start
2022-01-30 17:44:11 temperature_monitor_thread start...
2022-01-30 17:44:11 i2c_sim_init end
2022-01-30 17:44:12 power open power_version = 0x71
2022-01-30 17:44:14 power type version: 0x0071
2022-01-30 17:44:14 Enter sleep to make sure power release finish.
2022-01-30 17:44:17 chain avg vol drop to 4.47
2022-01-30 17:44:45 Slept 30 seconds, diff = 3.
2022-01-30 17:44:46 set_voltage_by_steps to 1500.
2022-01-30 17:44:49 chain avg vol rise to 14.53
2022-01-30 17:44:51 start up min temp by 75a = 11
2022-01-30 17:45:02 Chain[0]: find 98 asic, times 0
2022-01-30 17:45:14 Chain[0]: find 98 asic, times 1
2022-01-30 17:45:26 Chain[0]: find 98 asic, times 2
2022-01-30 17:45:27 Chain 0 only find 98 asic, will power off hash board 0
2022-01-30 17:45:28 chain avg vol rise to 21.79
2022-01-30 17:45:29 chain avg vol drop to 14.55
2022-01-30 17:45:38 Chain[1]: find 126 asic, times 0
2022-01-30 17:45:48 Chain[2]: find 102 asic, times 0
2022-01-30 17:46:00 Chain[2]: find 102 asic, times 1
2022-01-30 17:46:13 Chain[2]: find 102 asic, times 2
2022-01-30 17:46:14 Chain 2 only find 102 asic, will power off hash board 2
2022-01-30 17:46:20 pulse_mode = 1, ccdly_sel = 0, pwth_sel = 1
2022-01-30 17:46:21 min freq in eeprom = 545
2022-01-30 17:46:21 fixed frequency is 545
2022-01-30 17:46:21 Bring up temperature is 13
2022-01-30 17:46:21 set UART baud to 3000000
2022-01-30 17:46:21 STATUS_INITED: soc init done!
2022-01-30 17:46:21 create thread check_miner_status_thread
2022-01-30 17:46:21 create thread check_system_work_thread
2022-01-30 17:46:24 start to init...
2022-01-30 17:46:24 set_voltage_by_steps to 1450.
2022-01-30 17:46:26 fixed step freq_start = 50, freq_end = 545, freq_step = 6.25
2022-01-30 17:46:26 chain = 1 set freq to 56.25
2022-01-30 17:46:26 chain = 1 set freq to 62.50
2022-01-30 17:46:26 chain = 1 set freq to 68.75
2022-01-30 17:46:26 chain = 1 set freq to 75.00
2022-01-30 17:46:26 chain = 1 set freq to 81.25
2022-01-30 17:46:26 chain = 1 set freq to 87.50
2022-01-30 17:46:27 chain = 1 set freq to 93.75
2022-01-30 17:46:27 chain = 1 set freq to 100.00
2022-01-30 17:46:27 chain = 1 set freq to 106.25
2022-01-30 17:46:27 chain = 1 set freq to 112.50
2022-01-30 17:46:27 chain = 1 set freq to 118.75
2022-01-30 17:46:27 chain = 1 set freq to 125.00
2022-01-30 17:46:27 chain = 1 set freq to 131.25
2022-01-30 17:46:27 chain = 1 set freq to 137.50
2022-01-30 17:46:27 chain = 1 set freq to 143.75
2022-01-30 17:46:27 chain = 1 set freq to 150.00
2022-01-30 17:46:28 chain = 1 set freq to 156.25
2022-01-30 17:46:28 chain = 1 set freq to 162.50
2022-01-30 17:46:28 chain = 1 set freq to 168.75
2022-01-30 17:46:28 chain = 1 set freq to 175.00
2022-01-30 17:46:28 chain = 1 set freq to 181.25
2022-01-30 17:46:28 chain = 1 set freq to 187.50
2022-01-30 17:46:28 chain = 1 set freq to 193.75
2022-01-30 17:46:28 chain = 1 set freq to 200.00
2022-01-30 17:46:28 chain = 1 set freq to 206.25
2022-01-30 17:46:28 chain = 1 set freq to 212.50
2022-01-30 17:46:29 chain = 1 set freq to 218.75
2022-01-30 17:46:29 chain = 1 set freq to 225.00
2022-01-30 17:46:29 chain = 1 set freq to 231.25
2022-01-30 17:46:29 chain = 1 set freq to 237.50
2022-01-30 17:46:29 chain = 1 set freq to 243.75
2022-01-30 17:46:29 chain = 1 set freq to 250.00
2022-01-30 17:46:29 chain = 1 set freq to 256.25
2022-01-30 17:46:29 chain = 1 set freq to 262.50
2022-01-30 17:46:29 chain = 1 set freq to 268.75
2022-01-30 17:46:29 chain = 1 set freq to 275.00
2022-01-30 17:46:30 chain = 1 set freq to 281.25
2022-01-30 17:46:30 chain = 1 set freq to 287.50
2022-01-30 17:46:30 chain = 1 set freq to 293.75
2022-01-30 17:46:30 chain = 1 set freq to 300.00
2022-01-30 17:46:30 chain = 1 set freq to 306.25
2022-01-30 17:46:30 chain = 1 set freq to 312.50
2022-01-30 17:46:30 chain = 1 set freq to 318.75
2022-01-30 17:46:30 chain = 1 set freq to 325.00
2022-01-30 17:46:30 chain = 1 set freq to 331.25
2022-01-30 17:46:31 chain = 1 set freq to 337.50
2022-01-30 17:46:31 chain = 1 set freq to 343.75
2022-01-30 17:46:31 chain = 1 set freq to 350.00
2022-01-30 17:46:31 chain = 1 set freq to 356.25
2022-01-30 17:46:31 chain = 1 set freq to 362.50
2022-01-30 17:46:31 chain = 1 set freq to 368.75
2022-01-30 17:46:31 chain = 1 set freq to 375.00
2022-01-30 17:46:31 chain = 1 set freq to 381.25
2022-01-30 17:46:31 chain = 1 set freq to 387.50
2022-01-30 17:46:31 chain = 1 set freq to 393.75
2022-01-30 17:46:32 chain = 1 set freq to 400.00
2022-01-30 17:46:32 chain = 1 set freq to 406.25
2022-01-30 17:46:32 chain = 1 set freq to 412.50
2022-01-30 17:46:32 chain = 1 set freq to 418.75
2022-01-30 17:46:32 chain = 1 set freq to 425.00
2022-01-30 17:46:32 chain = 1 set freq to 431.25
2022-01-30 17:46:32 chain = 1 set freq to 437.50
2022-01-30 17:46:32 chain = 1 set freq to 443.75
2022-01-30 17:46:32 chain = 1 set freq to 450.00
2022-01-30 17:46:32 chain = 1 set freq to 456.25
2022-01-30 17:46:33 chain = 1 set freq to 462.50
2022-01-30 17:46:33 chain = 1 set freq to 468.75
2022-01-30 17:46:33 chain = 1 set freq to 475.00
2022-01-30 17:46:33 chain = 1 set freq to 481.25
2022-01-30 17:46:33 chain = 1 set freq to 487.50
2022-01-30 17:46:33 chain = 1 set freq to 493.75
2022-01-30 17:46:33 chain = 1 set freq to 500.00
2022-01-30 17:46:33 chain = 1 set freq to 506.25
2022-01-30 17:46:33 chain = 1 set freq to 512.50
2022-01-30 17:46:33 chain = 1 set freq to 518.75
2022-01-30 17:46:34 chain = 1 set freq to 525.00
2022-01-30 17:46:34 chain = 1 set freq to 531.25
2022-01-30 17:46:34 chain = 1 set freq to 537.50
2022-01-30 17:46:34 chain = 1 set freq to 543.75
2022-01-30 17:46:34 chain = 1 set freq to 545.00
2022-01-30 17:46:34 pulse_mode = 1, ccdly_sel = 0, pwth_sel = 1
2022-01-30 17:46:34 start do_core_reset
2022-01-30 17:46:41 end do_core_reset
2022-01-30 17:46:51 set_voltage_by_steps to 1392.
2022-01-30 17:46:52 Init done!
2022-01-30 17:46:52 STATUS_OKAY
2022-01-30 17:46:52 start the cached job
2022-01-30 17:46:52 Version num 65536
2022-01-30 17:46:52 Mask num 0x1fffe000
2022-01-30 17:46:52 opt_multi_version = 65536, interval timeout = 2837042
2022-01-30 17:46:52 freq = 545, percent = 90, hcn = 4809, timeout = 2837042
2022-01-30 17:46:52 set_start_time_point total_tv_start_sys=189 total_tv_end_sys=190
2022-01-30 17:46:53 set_voltage_by_steps to 1425.
Check those two hashboard not showing on the dashboard physically and maybe there are corrosion and rust after you dried them.
Also, if you want us to troubleshoot it for you then post the whole kernel logs here, and don't forget to put it inside the code tag(a # button you can find this while editing your post).
But if you decided to hire a tech contact zeusbtc.com for help.
Also, if you want us to troubleshoot it for you then post the whole kernel logs here, and don't forget to put it inside the code tag(a # button you can find this while editing your post).
But if you decided to hire a tech contact zeusbtc.com for help.
First about venting:
If you are talking about anything resembling the unit on a table exhausting its hot air toward an opened window, the unit will wither be too close, too far or both, depending on the weather. There is no sweet spot, unless you can somehow force a positive pressure in the room. Fans from the unit produce airflow that cannot compensate for the negative pressure in the room.
If you have only one unit, a properly sized air hose from the exhaust of the unit to the outside will "force" the air to go out, and you have to prevent water from following the hose to the unit, for example, by making the air exit below the unit.
Hopefully it is helpful for you next setup, or prevents that mishap to someone else. Unless actively forcing a positive pressure in a building, the wind direction and its environment will decide where air comes in and where it goes out.
Now that it happened...
WARNING: If some part(s) makes some other part(s) fail, then playing around may damage parts that are not yet damaged.
It appears that you may have 2 failed hashboards. Sometimes, somehow, swapping things around fixes stuff for unknown reasons.
If you haven't done so already, you should clean the boards. Removing dirt alone may fix it.
Then look at the logs. Sharing it here may help. You want to know, for example, if the boards are not-detected or detected but malfunctioning. It may literally tell you what is the problem.
After identifying which board is working, you know that its data cable and its power cables are working.
You can test each data port by connecting the working board with the working data cable to each port of the control board.
If the working board does NOT work when connected to the two other data ports, then the control board is almost certainly the (or a) problem.
If the board DOES works in all data ports, then you can test each data cables, then each power cables, etc. to isolate the problem.
A bad hashboard, bad power supply, a bad data cable, a bad connection of the data cable and/or a bad control board, or any combination of those may have the very same symptoms. The physical position of the parts may squeeze or stretch something just a bit in a way that makes the difference between it working and not working.
If you are equipped to do so and "have a clue" about it, I would suggest testing the power supply first, then testing for short circuits on the hashbords power inputs.
Did you contact Bitmain? It is unlikely covered by the warranty, but they may be able to give you some directions.
Best of luck!
If you are talking about anything resembling the unit on a table exhausting its hot air toward an opened window, the unit will wither be too close, too far or both, depending on the weather. There is no sweet spot, unless you can somehow force a positive pressure in the room. Fans from the unit produce airflow that cannot compensate for the negative pressure in the room.
If you have only one unit, a properly sized air hose from the exhaust of the unit to the outside will "force" the air to go out, and you have to prevent water from following the hose to the unit, for example, by making the air exit below the unit.
Hopefully it is helpful for you next setup, or prevents that mishap to someone else. Unless actively forcing a positive pressure in a building, the wind direction and its environment will decide where air comes in and where it goes out.
Now that it happened...
WARNING: If some part(s) makes some other part(s) fail, then playing around may damage parts that are not yet damaged.
It appears that you may have 2 failed hashboards. Sometimes, somehow, swapping things around fixes stuff for unknown reasons.
If you haven't done so already, you should clean the boards. Removing dirt alone may fix it.
Then look at the logs. Sharing it here may help. You want to know, for example, if the boards are not-detected or detected but malfunctioning. It may literally tell you what is the problem.
After identifying which board is working, you know that its data cable and its power cables are working.
You can test each data port by connecting the working board with the working data cable to each port of the control board.
If the working board does NOT work when connected to the two other data ports, then the control board is almost certainly the (or a) problem.
If the board DOES works in all data ports, then you can test each data cables, then each power cables, etc. to isolate the problem.
A bad hashboard, bad power supply, a bad data cable, a bad connection of the data cable and/or a bad control board, or any combination of those may have the very same symptoms. The physical position of the parts may squeeze or stretch something just a bit in a way that makes the difference between it working and not working.
If you are equipped to do so and "have a clue" about it, I would suggest testing the power supply first, then testing for short circuits on the hashbords power inputs.
Did you contact Bitmain? It is unlikely covered by the warranty, but they may be able to give you some directions.
Best of luck!
I recently installed a single S19J Pro unit in my home that is vented to the outside to keep the unit cool.
I underestimated the suction coming through the vents and the unit sucked up snow during a recent storm. I took it apart and dried everything out but only 1/3 hashboards register on the dashboard and I am only getting 1/3 of the expected hashing power. I have also factory reset the unit with no luck.
I am new to mining and do not know what troubleshooting steps to take next or where to source replacement parts. Any advice is greatly appreciated.
I underestimated the suction coming through the vents and the unit sucked up snow during a recent storm. I took it apart and dried everything out but only 1/3 hashboards register on the dashboard and I am only getting 1/3 of the expected hashing power. I have also factory reset the unit with no luck.
I am new to mining and do not know what troubleshooting steps to take next or where to source replacement parts. Any advice is greatly appreciated.
Jump to: