s17 antminer Voltage Setting Failed: I2C Error

So I'm getting this warning: "PSU: Executing set voltage failed: I2C error, retrying..." I tried swapping out the control board, changing the wires, and even using a new PSU, but I'm still stuck with the same issue. The voltmeter reads 21v on PSU out1 and zero volts on out2. Anyone got any ideas? Appreciate any help! Here's some log info: Fri Dec 10 19:05:03 2021 kern.info kernel: [ 0.000000] Booting Linux on physical CPU 0x0 Fri Dec 10 19:05:03 2021 kern.notice kernel: [ 0.000000] Linux version 4.4.0-xilinx-g518c00cd977f-dirty (build@runner-pegegjka-project-312-concurrent-1) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3560-79f57e422d) ) #0 SMP PREEMPT Wed Oct 27 14:27:11 2021 Fri Dec 10 19:05:03 2021 kern.info kernel: [ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d Fri Dec 10 19:05:03 2021 kern.info kernel: [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache Fri Dec 10 19:05:03 2021 kern.info kernel: [ 0.000000] Machine model: Antminer S17 Miner Control Board Fri Dec 10 19:05:03 2021 kern.info kernel: [ 0.000000] cma: Reserved 16 MiB at 0x0f000000 Fri Dec 10 19:05:03 2021 kern.info kernel: [ 0.000000] Memory policy: Data cache writealloc Fri Dec 10 19:05:03 2021 kern.debug kernel: [ 0.000000] On node 0 totalpages: 65536 Fri Dec 10 19:05:03 2021 kern.debug kernel: [ 0.000000] free_area_init_node: node 0, pgdat c07ba340, node_mem_map cedf0000 Fri Dec 10 19:05:03 2021 kern.debug kernel: [ 0.000000] Normal zone: 512 pages used for memmap Fri Dec 10 19:05:03 2021 kern.debug kernel: [ 0.000000] Normal zone: 0 pages reserved Fri Dec 10 19:05:03 2021

Did you flash it with custom firmware it looks like you flash it with s17 pro Braiins OS? What exact unit model of your miner? s17 or s17 pro? I think we can troubleshoot this miner if you can revert it back to stock firmware. Follow the guide from here S17/S17Pro/S9 SE/S9k/Z11 control board program recovery (SD card flashing with customized PW) You can download the SD Card firmware on their download page. Once you are done flashing it to stock firmware run it first for 30 minutes or more and then copy the kernel logs paste it here. I suggest you use the "insert code" tag with # icon to make your post clean. Your post above actually looks messy and hard to understand. Use pastebin.com  if you have a limit in posting the whole kernel logs.

Hello sir thanks for reply sorry about the format post Yes its Braiins os and its s17pro here is the link for new kernal        https://pastebin.com/371YAZuK Thanks, Kian

Hey please put it back to stock firmware for making the troubleshooting easier for us, like BitMaxz proposed

Hi I did do that please the link to see the kernel    https://pastebin.com/371YAZuK

Ok sorry, my bad. In my eyes it seems that there are problems with the hash board in chain 2. Have you tried running it with only one hashboard in use at the time?

How do I do that? just disconnect the harness or take the hashboard completely out of case?

No need to completely remove the hashboard just disconnect PSU wire and ribbon cable and run them one by one you can follow the guide here below - https://support.bitmain.com/hc/en-us/articles/226142788-Test-hash-board-one-by-one But run chain 2 first and let see if it still shows 0 ASICS and also try to swap cables from other chains while running them one by one. Did you buy this 2nd hand unit? Chain 1 has a temp sensor issue What I see here is that you or the old owner of this miner switched to Braiins OS to bypass the temp issue?

Hi Yes, used unit...been working fine started losing boards then completely stopped--I put it on braiins just to test braiins and see what kinda of a different softwares make I am new to the game..braiins did lower the electricity but did not raise the hash had it on autotune ...braiins said  the reason did not raise the hash is because of temp ,these units have bad solder on the tin coolers...they said if I redo the cooling fins with better material it will get higher hash b/c temps will run lower. I will follow the steps you recommend and report back on the hashboard swaps Thanks, Kian