Antminer S9j Hashboard missing

[Scorpyy]

Recently one of my hash-boards stopped appearing after regular cleaning.

Kernel log showed:

Code:

Chain[J6] has 63 asic
Chain[J7] has 63 asic
Chain[J8] has 0 asic

Booting sequence:

Red led light on hash board is on during the booting process on "defective" board and only on one of the working boards. The 3rd working board has no red led.
After that the all 2 leds turn off.
Lastly the 2 leds on 2 working boards turn on, the led on "defective" board stays off.

The green lights on control board seem normal ( as on any other working miner ) when miner starts mining ( with 2 boards )

I have tried:

Software related stuff:

Rebooting the miner several times
Reset miner to default twice
Re-flash miner to Antminer-S9j-all-201811071118-autofreq-user-Update2UBI-NF also several times.
Re-uploading backup files i had saved when i got the machine

Hardware:

Changing PSU connectors, switching to the known working ones from other boards.
Changed whole PSU, tried using a different one.
Changed order of data cables; as well as switching the whole cable.

After changing the data cable orders, different Chain showed 0 asic in kernel log ( first time it was Chain[J8] has 0 asic, and after the change Chain[J7] has 0 asic )

Miner is still under warranty however i do believe its not valid anymore since i opened it for cleaning.

Any ideas for further troubleshooting of hash board would be greatly appreciated.

Kernel log:

Code:

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.14.0-xilinx-g16220c3 (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #83 SMP PREEMPT Thu Jul 12 11:42:53 CST 2018
[    0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Xilinx Zynq
[    0.000000] cma: CMA: reserved 128 MiB at 16800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 126976
[    0.000000] free_area_init_node: node 0, pgdat c074ac00, node_mem_map debd8000
[    0.000000]   Normal zone: 992 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 126976 pages, LIFO batch:31
[    0.000000] PERCPU: Embedded 8 pages/cpu @debc1000 s9088 r8192 d15488 u32768
[    0.000000] pcpu-alloc: s9088 r8192 d15488 u32768 alloc=8*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 125984
[    0.000000] Kernel command line: noinitrd mem=496M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 364316K/507904K available (5057K kernel code, 284K rwdata, 1928K rodata, 204K init, 258K bss, 143588K reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xdf800000 - 0xff000000   ( 504 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xdf000000   ( 496 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc06da8ac   (6987 kB)
[    0.000000]       .init : 0xc06db000 - 0xc070e380   ( 205 kB)
[    0.000000]       .data : 0xc0710000 - 0xc0757138   ( 285 kB)
[    0.000000]        .bss : 0xc0757144 - 0xc0797bfc   ( 259 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] 	Dump stacks of tasks blocking RCU-preempt GP.
[    0.000000] 	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] ps7-slcr mapped to df802000
[    0.000000] zynq_clock_init: clkc starts at df802100
[    0.000000] Zynq clock init
[    0.000015] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[    0.000293] ps7-ttc #0 at df804000, irq=43
[    0.000594] Console: colour dummy device 80x30
[    0.000624] Calibrating delay loop... 1325.46 BogoMIPS (lpj=6627328)
[    0.040196] pid_max: default: 32768 minimum: 301
[    0.040403] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.040423] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.042580] CPU: Testing write buffer coherency: ok
[    0.042887] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.042943] Setting up static identity map for 0x4cb118 - 0x4cb170
[    0.043163] L310 cache controller enabled
[    0.043183] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[    0.120984] CPU1: Booted secondary processor
[    0.210218] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.210347] Brought up 2 CPUs
[    0.210367] SMP: Total of 2 processors activated.
[    0.210375] CPU: All CPU(s) started in SVC mode.
[    0.211046] devtmpfs: initialized
[    0.213473] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.214657] regulator-dummy: no parameters
[    0.221519] NET: Registered protocol family 16
[    0.223782] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.226050] cpuidle: using governor ladder
[    0.226063] cpuidle: using governor menu
[    0.233409] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[    0.234900] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.234913] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.235028] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xdf880000
[    0.256638] bio: create slab <bio-0> at 0
[    0.258038] vgaarb: loaded
[    0.258716] SCSI subsystem initialized
[    0.259614] usbcore: registered new interface driver usbfs
[    0.259781] usbcore: registered new interface driver hub
[    0.260021] usbcore: registered new device driver usb
[    0.260696] media: Linux media interface: v0.10
[    0.260854] Linux video capture interface: v2.00
[    0.261097] pps_core: LinuxPPS API ver. 1 registered
[    0.261109] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.261257] PTP clock support registered
[    0.261620] EDAC MC: Ver: 3.0.0
[    0.262786] Advanced Linux Sound Architecture Driver Initialized.
[    0.265514] DMA-API: preallocated 4096 debug entries
[    0.265527] DMA-API: debugging enabled by kernel config
[    0.265595] Switched to clocksource arm_global_timer
[    0.286516] NET: Registered protocol family 2
[    0.287157] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.287214] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    0.287299] TCP: Hash tables configured (established 4096 bind 4096)
[    0.287339] TCP: reno registered
[    0.287356] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.287386] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.287625] NET: Registered protocol family 1
[    0.287956] RPC: Registered named UNIX socket transport module.
[    0.287968] RPC: Registered udp transport module.
[    0.287977] RPC: Registered tcp transport module.
[    0.287985] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.287997] PCI: CLS 0 bytes, default 64
[    0.288431] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.290418] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.292476] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.292657] msgmni has been set to 967
[    0.293411] io scheduler noop registered
[    0.293425] io scheduler deadline registered
[    0.293476] io scheduler cfq registered (default)
[    0.307900] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[    0.307921] dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.429932] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[    0.997220] console [ttyPS0] enabled
[    1.001471] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to df866000
[    1.009082] [drm] Initialized drm 1.1.0 20060810
[    1.026158] brd: module loaded
[    1.035500] loop: module loaded
[    1.044881] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    1.050857] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[    1.058721] libphy: XEMACPS mii bus: probed
[    1.063094] ------------- phy_id = 0x3625e62
[    1.068036] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[    1.076620] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.083240] ehci-pci: EHCI PCI platform driver
[    1.090486] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[    1.097316] usbcore: registered new interface driver usb-storage
[    1.104144] mousedev: PS/2 mouse device common for all mice
[    1.110254] i2c /dev entries driver
[    1.117149] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[    1.122630] cpufreq_cpu0: failed to get cpu0 regulator: -19
[    1.128552] Xilinx Zynq CpuIdle Driver started
[    1.133394] sdhci: Secure Digital Host Controller Interface driver
[    1.139628] sdhci: Copyright(c) Pierre Ossman
[    1.143896] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.150716] mmc0: no vqmmc regulator found
[    1.154732] mmc0: no vmmc regulator found
[    1.195642] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[    1.204333] usbcore: registered new interface driver usbhid
[    1.209841] usbhid: USB HID core driver
[    1.214562] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.220864] nand: Micron MT29F2G08ABAEAWP
[    1.224823] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[    1.230757] Bad block table found at page 131008, version 0x01
[    1.236982] Bad block table found at page 130944, version 0x01
[    1.243031] 3 ofpart partitions found on MTD device pl353-nand
[    1.248813] Creating 3 MTD partitions on "pl353-nand":
[    1.253903] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[    1.261955] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[    1.269290] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[    1.280002] TCP: cubic registered
[    1.283239] NET: Registered protocol family 17
[    1.287939] Registering SWP/SWPB emulation handler
[    1.293809] regulator-dummy: disabling
[    1.298141] UBI: attaching mtd1 to ubi0
[    1.824320] UBI: scanning is finished
[    1.835927] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[    1.842977] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.849763] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.856449] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.863287] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[    1.869297] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.876408] UBI: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 1893680516
[    1.885422] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[    1.894653] UBI: background thread "ubi_bgt0d" started, PID 1084
[    1.894659] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.898591] ALSA device list:
[    1.898595]   No soundcards found.
[    1.914906] UBIFS: background thread "ubifs_bgt0_0" started, PID 1086
[    1.943878] UBIFS: recovery needed
[    2.013753] UBIFS: recovery completed
[    2.017470] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    2.023391] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.032525] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    2.042416] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.047450] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 9D373F07-FDB6-4278-8D91-DA51B37CDEF0, small LPT model
[    2.058720] VFS: Mounted root (ubifs filesystem) on device 0:11.
[    2.065909] devtmpfs: mounted
[    2.069015] Freeing unused kernel memory: 204K (c06db000 - c070e000)
[    2.908526] random: dd urandom read with 1 bits of entropy available
[    3.285641] 
[    3.285641] bcm54xx_config_init
[    3.895645] 
[    3.895645] bcm54xx_config_init
[    6.896467] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[    6.902559] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[   20.381361] In axi fpga driver!
[   20.384432] request_mem_region OK!
[   20.387860] AXI fpga dev virtual address is 0xdf9fe000
[   20.392930] *base_vir_addr = 0xc51e
[   20.407853] In fpga mem driver!
[   20.410922] request_mem_region OK!
[   20.414486] fpga mem virtual address is 0xe2000000
[   21.205025] 
[   21.205025] bcm54xx_config_init
[   21.834962] 
[   21.834962] bcm54xx_config_init
[   24.835485] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[   24.841504] xemacps e000b000.ps7-ethernet: link up (100/FULL)
Detect 512MB control board of XILINX
Miner Type = S9
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x0000ffff
Check chain[5] PIC fw version=0x03
Check chain[6] PIC fw version=0x03
Check chain[7] PIC fw version=0x03
Fix freq=600 Chain[5] voltage_pic=108 value=880
Fix freq=600 Chain[6] voltage_pic=108 value=880
Fix freq=600 Chain[7] voltage_pic=108 value=880
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
Chain[J6] has 63 asic
Chain[J7] has 63 asic
Chain[J8] has 0 asic
set_reset_hashboard = 0x00000080
set_reset_hashboard = 0x00000000
retry Chain[J8] has 0 asic
set_reset_hashboard = 0x00000080
set_reset_hashboard = 0x00000000
retry Chain[J8] has 0 asic
set_reset_hashboard = 0x00000080
set_reset_hashboard = 0x00000000
retry Chain[J8] has 0 asic
set_reset_hashboard = 0x00000080
set_reset_hashboard = 0x00000000
retry Chain[J8] has 0 asic
set_reset_hashboard = 0x00000080
set_reset_hashboard = 0x00000000
retry Chain[J8] has 0 asic
set_reset_hashboard = 0x00000080
set_reset_hashboard = 0x00000000
retry Chain[J8] has 0 asic
Chain[J6] has no freq in PIC, set default freq=600M Ooooooh you changed the clock speed... TO THE MOON!
Chain[J6] has no core num in PIC
Chain[J7] has no freq in PIC, set default freq=600M Ooooooh you changed the clock speed... TO THE MOON!
Chain[J7] has no core num in PIC

They miner is set to run at a fixed frequency so we can all buy some lambos.
read PIC voltage=940 on chain[5]
Chain:5 chipnum=63
Asic[ 0]:600 
Asic[ 1]:600 Asic[ 2]:600 Asic[ 3]:600 Asic[ 4]:600 Asic[ 5]:600 Asic[ 6]:600 Asic[ 7]:600 Asic[ 8]:600 
Asic[ 9]:600 Asic[10]:600 Asic[11]:600 Asic[12]:600 Asic[13]:600 Asic[14]:600 Asic[15]:600 Asic[16]:600 
Asic[17]:600 Asic[18]:600 Asic[19]:600 Asic[20]:600 Asic[21]:600 Asic[22]:600 Asic[23]:600 Asic[24]:600 
Asic[25]:600 Asic[26]:600 Asic[27]:600 Asic[28]:600 Asic[29]:600 Asic[30]:600 Asic[31]:600 Asic[32]:600 
Asic[33]:600 Asic[34]:600 Asic[35]:600 Asic[36]:600 Asic[37]:600 Asic[38]:600 Asic[39]:600 Asic[40]:600 
Asic[41]:600 Asic[42]:600 Asic[43]:600 Asic[44]:600 Asic[45]:600 Asic[46]:600 Asic[47]:600 Asic[48]:600 
Asic[49]:600 Asic[50]:600 Asic[51]:600 Asic[52]:600 Asic[53]:600 Asic[54]:600 Asic[55]:600 Asic[56]:600 
Asic[57]:600 Asic[58]:600 Asic[59]:600 Asic[60]:600 Asic[61]:600 Asic[62]:600 
Chain:5 max freq=600
Chain:5 min freq=600

read PIC voltage=940 on chain[6]
Chain:6 chipnum=63
Asic[ 0]:600 
Asic[ 1]:600 Asic[ 2]:600 Asic[ 3]:600 Asic[ 4]:600 Asic[ 5]:600 Asic[ 6]:600 Asic[ 7]:600 Asic[ 8]:600 
Asic[ 9]:600 Asic[10]:600 Asic[11]:600 Asic[12]:600 Asic[13]:600 Asic[14]:600 Asic[15]:600 Asic[16]:600 
Asic[17]:600 Asic[18]:600 Asic[19]:600 Asic[20]:600 Asic[21]:600 Asic[22]:600 Asic[23]:600 Asic[24]:600 
Asic[25]:600 Asic[26]:600 Asic[27]:600 Asic[28]:600 Asic[29]:600 Asic[30]:600 Asic[31]:600 Asic[32]:600 
Asic[33]:600 Asic[34]:600 Asic[35]:600 Asic[36]:600 Asic[37]:600 Asic[38]:600 Asic[39]:600 Asic[40]:600 
Asic[41]:600 Asic[42]:600 Asic[43]:600 Asic[44]:600 Asic[45]:600 Asic[46]:600 Asic[47]:600 Asic[48]:600 
Asic[49]:600 Asic[50]:600 Asic[51]:600 Asic[52]:600 Asic[53]:600 Asic[54]:600 Asic[55]:600 Asic[56]:600 
Asic[57]:600 Asic[58]:600 Asic[59]:600 Asic[60]:600 Asic[61]:600 Asic[62]:600 
Chain:6 max freq=600
Chain:6 min freq=600

max freq = 600
set baud=1
Chain[J6] PIC temp offset=62,0,0,0,0,0,36,28
Chain[J6] chip[244] use PIC middle temp offset=0 typeID=55
New offset Chain[5] chip[244] local:33 remote:35 offset:28 
Chain[J6] chip[244] get middle temp offset=28 typeID=55
Chain[J6] chip[140] use PIC middle temp offset=28 typeID=00
Warning: Chain[J6] has no temp offset in PIC! will fix it
New offset Chain[5] chip[244] local:33 remote:35 offset:28 
Chain[J6] chip[244] get middle temp offset=28 typeID=55
Chain[J7] PIC temp offset=62,0,0,0,0,0,36,28
Chain[J7] chip[244] use PIC middle temp offset=0 typeID=55
New offset Chain[6] chip[244] local:34 remote:35 offset:30 
Chain[J7] chip[244] get middle temp offset=30 typeID=55
Chain[J7] chip[140] use PIC middle temp offset=28 typeID=00
Warning: Chain[J7] has no temp offset in PIC! will fix it
New offset Chain[6] chip[244] local:34 remote:35 offset:30 
Chain[J7] chip[244] get middle temp offset=30 typeID=55
Chain[J6] set working voltage=880 [108]
Chain[J7] set working voltage=880 [108]
setStartTimePoint total_tv_start_sys=138 total_tv_end_sys=139
restartNum = 2 , auto-reinit enabled...
do read_temp_func once...
do check_asic_reg 0x08

get RT hashrate from Chain[5]: (asic index start from 1-63)
Asic[01]=74.7250 Asic[02]=67.8630 Asic[03]=64.9110 Asic[04]=71.1680 Asic[05]=71.4870 Asic[06]=65.9170 Asic[07]=66.6390 Asic[08]=68.7860 
Asic[09]=66.2860 Asic[10]=67.4770 Asic[11]=71.0170 Asic[12]=72.6950 Asic[13]=71.4540 Asic[14]=66.6550 Asic[15]=66.2700 Asic[16]=63.6520 
Asic[17]=70.1280 Asic[18]=69.1380 Asic[19]=69.1050 Asic[20]=68.6520 Asic[21]=71.0510 Asic[22]=67.3260 Asic[23]=72.9470 Asic[24]=68.6850 
Asic[25]=70.6480 Asic[26]=67.7290 Asic[27]=64.2730 Asic[28]=63.8540 Asic[29]=70.6820 Asic[30]=71.1680 Asic[31]=60.8500 Asic[32]=68.9540 
Asic[33]=66.7900 Asic[34]=68.3160 Asic[35]=67.5110 Asic[36]=67.9980 Asic[37]=72.5950 Asic[38]=69.9600 Asic[39]=66.2190 Asic[40]=66.7900 
Asic[41]=73.1310 Asic[42]=64.4410 Asic[43]=69.3900 Asic[44]=64.7430 Asic[45]=68.5010 Asic[46]=74.6250 Asic[47]=68.0650 Asic[48]=73.0640 
Asic[49]=68.0310 Asic[50]=66.1690 Asic[51]=66.6550 Asic[52]=63.4010 Asic[53]=66.4540 Asic[54]=65.0280 Asic[55]=71.5540 Asic[56]=71.0010 
Asic[57]=72.0740 Asic[58]=65.6990 Asic[59]=67.5610 Asic[60]=63.3500 Asic[61]=66.9410 Asic[62]=70.6650 Asic[63]=66.4710 

get RT hashrate from Chain[6]: (asic index start from 1-63)
Asic[01]=66.7390 Asic[02]=66.9070 Asic[03]=67.6280 Asic[04]=64.1720 Asic[05]=67.0410 Asic[06]=70.3300 Asic[07]=67.0750 Asic[08]=71.1680 
Asic[09]=61.7060 Asic[10]=63.7530 Asic[11]=65.1120 Asic[12]=66.5040 Asic[13]=64.4740 Asic[14]=65.2960 Asic[15]=67.8470 Asic[16]=70.7150 
Asic[17]=68.2660 Asic[18]=69.1220 Asic[19]=71.3530 Asic[20]=62.4440 Asic[21]=71.7560 Asic[22]=72.4270 Asic[23]=72.6950 Asic[24]=65.5820 
Asic[25]=70.5140 Asic[26]=68.4340 Asic[27]=70.6820 Asic[28]=65.7330 Asic[29]=61.7060 Asic[30]=65.0950 Asic[31]=67.5780 Asic[32]=70.4810 
Asic[33]=66.3370 Asic[34]=65.3970 Asic[35]=70.7830 Asic[36]=68.1150 Asic[37]=67.2760 Asic[38]=68.0310 Asic[39]=71.9910 Asic[40]=68.5510 
Asic[41]=62.0580 Asic[42]=68.5010 Asic[43]=65.4470 Asic[44]=59.4920 Asic[45]=64.7260 Asic[46]=67.5110 Asic[47]=66.0350 Asic[48]=66.4040 
Asic[49]=68.8200 Asic[50]=69.4240 Asic[51]=67.6280 Asic[52]=66.4370 Asic[53]=73.5680 Asic[54]=70.7320 Asic[55]=66.2700 Asic[56]=69.2060 
Asic[57]=70.6150 Asic[58]=67.6280 Asic[59]=69.2220 Asic[60]=69.3400 Asic[61]=70.6650 Asic[62]=69.0550 Asic[63]=70.5140 
Check Chain[J6] ASIC RT error: (asic index start from 1-63)
Check Chain[J7] ASIC RT error: (asic index start from 1-63)
Done check_asic_reg
do read temp on Chain[5]
Chain[5] Chip[62] TempTypeID=55 middle offset=28
Chain[5] Chip[62] local Temp=65
Chain[5] Chip[62] middle Temp=70
Done read temp on Chain[5]
do read temp on Chain[6]
Chain[6] Chip[62] TempTypeID=55 middle offset=30
Chain[6] Chip[62] local Temp=64
Chain[6] Chip[62] middle Temp=71
Done read temp on Chain[6]
set FAN speed according to: temp_highest=71 temp_top1[PWM_T]=71 temp_top1[TEMP_POS_LOCAL]=65 temp_change=0 fix_fan_steps=-7
set normal FAN speed... with fix_fan_steps=-8
FAN PWM: 46
read_temp_func Done! Doesn't matter much since I think we are going to want to set that to 100
Why is that you ask? Because we are blasting off to the MOON!
CRC error counter=13

[BitMaxz]

Are you sure that you are flashing it with official antminer firmware from bitmain?

The kernel logs show something like "Ooooooh you changed the clock speed... TO THE MOON!" it seems that someone hacked your miner and replace the firmware with their own customized firmware.

Can you flash it with SD card.

You can follow this guide S9 series (S9, S9i, S9j, S9 Hydro) Control Board Program Recovery

Then flash it with this firmware instead of s9j flash it with s9 firmware "Antminer-S9-all-201711171757-autofreq-user-Update2UBI-NF.tar.gz" in webGUI. After that test, it again for 30 minutes if it doesn't work post the new kernel logs here.

You can also try the Braiins OS to test if your 3rd hashboard if its totally dead or not.

[mikeywith]

Nice catch, couldn't see that at first glance.

Anyhow just to make OP's life easier, in most cases a simple reset will be enough to get rid of the hacked firmware, but there is a trick  that needs to be done while resetting.

1-Use the IP-report to reset the the miner.

2-Flash a new firmware right away , you have only a few seconds to do so,  the flash will fail if you take more than 20-30 seconds to hit that upgrade button, so make sure you prepare everything in advance so that you can perform the flash as quickly as possible.

[Artemis3]

The kernel logs show something like "Ooooooh you changed the clock speed... TO THE MOON!" it seems that someone hacked your miner and replace the firmware with their own customized firmware.

read_temp_func Done! Doesn't matter much since I think we are going to want to set that to 100
Why is that you ask? Because we are blasting off to the MOON!

Cheesy. I wonder what else does this firmware does? It would be interesting to inspect bmminer.conf

I would go the Braiins OS route, but in any case not only you need to restore the firmware, but also set up a password... Preferably from a non tainted PC (ie. not the Windows pc that installed the malware, lol).

Unless this is one of the known firmware mods and was installed willingly by the owner or former owner.

[Scorpyy]

I do not believe that my miners are infected with malicious virus, since i've used official bitmain firmware and bmminer from tazers: https://bitcointalk.org/index.php?topic=4513567.0

I've saw that TO THE MOON message in kernel log on all of my miners but i was sure that tazers left that message in there. It would be great if someone who also clocked them had the same kernel log messages just to confirm

[mikeywith]

I just texted taserz on telegram and he did confirm that this line is in his firmware (he checked the code)

Why is that you ask? Because we are blasting off to the MOON!

So it does not seem like your gear is hacked anymore, but the best way to confirm would be checking the hashrate on the pool, if the average 24 hrs are similar on both the pool and the miner GUI then you are good.

but now that you mentioned about using taserz's firmware, it is safe to assume that you tried to overclock your gear and you got that board toasted , what setting you had on it and what was the temp?

[taserz]

What frequency and voltage did you set it at? Genuinely curious as I have some s9's running at 18th/s for the past year. Most of mine run at 16th or 17th to keep things on the safer side.

[BitMaxz]

I do not believe that my miners are infected with malicious virus, since i've used official bitmain firmware and bmminer from tazers: https://bitcointalk.org/index.php?topic=4513567.0...

Oh.. I see...

I agree with mikeywith it's possible that your hashboard is dead due to overclocking(like the other said overclocking is always reducing the lifespan of the miner) if you continue to run the miner at the full capacity other hashboard will be dead just like what happened to Chain[J8].  Known issue of moded bmminer of taserz according to the thraed "Hashboard do not report temps" so there is a possibility that the Chain[J8] is overheated.

Did you try the method that I provided above? Make program recovery and then flash it with "Antminer-S9-all-201711171757-autofreq-user-Update2UBI-NF.tar.gz"?

Let's see if the hash board still could run at a lower frequency.

[tim-bc]

If you use the multi-option firmware from May 2019 you will be able to switch between many efficiency settings, and it will autotune rather than forcing you to set voltage and freq manually for each miner/hashboard.

[Artemis3]

If you use the multi-option firmware from May 2019 you will be able to switch between many efficiency settings, and it will autotune rather than forcing you to set voltage and freq manually for each miner/hashboard.

And lock you out of your miner removing ssh access and chance for trying other firmwares... Thanks but no thanks. Avoid Bitmain's 2019 firmware like the plague.

[Scorpyy]

Did you try the method that I provided above? Make program recovery and then flash it with "Antminer-S9-all-201711171757-autofreq-user-Update2UBI-NF.tar.gz"?

Let's see if the hash board still could run at a lower frequency.

Read bolded only for short version

I forgot to mention that i also tried to flash it with Antminer-S9-all-201711171757-autofreq-user-Update2UBI-NF.tar.gz , however then the miner wasn't hashing at all ( loads a screen with 0 values everywhere --> http://prntscr.com/oltgfm ).
I do believe it is because of that firmware does not support my s9j machine as stated on bitmain website: * Support S9 miners except S9-11.85T，12.93T，14T with fixed frequency  -> My machine is 14T.

I also tried the LPM flash Antminer-S9-LPM-20181102.tar.gz but had same results - hashboard is not visible.

Just now out of curiosity i also tried Antminer-S9-all-201705031838-650M-user-Update2UBI-NF . - hashboard is not visible

I did try however only the "normal" firmware upgrade, i didn't try any of methods above that suggested using SD card as well as troubleshooting of control board as i believe those answers were suggestions if my machine was hacked which we now agreed it is not.

but now that you mentioned about using taserz's firmware, it is safe to assume that you tried to overclock your gear and you got that board toasted , what setting you had on it and what was the temp?

My miners are overclocked and are working in that state from 8 to 10 months depending on when machine was bought. The thing is this hash board stopped appearing after regular cleaning was performed as i stated in first post. Regular cleaning we do on all machines which included cleaning of both fans, vacuum cleaning front hashboard side that collected the most dirt, small cleaning of inside parts with small objects like toothpick etc...

What frequency and voltage did you set it at? Genuinely curious as I have some s9's running at 18th/s for the past year. Most of mine run at 16th or 17th to keep things on the safer side.

Here are the most recent values i had, some machines are 14.5T some 14T:

Asic / voltage / freq / hashrate / power consumption

s9j1 - 9.0v - 825 - 17,560.88      1.937 kW
s9j2 - 9.2v - 825 - 17,544.47      1.965 kW
s9j3 - 9.2v - 800 - 17,105.40
s9j4 - 9.0v - 800 - 16,986.38      1.805 kW
s9j5 - 9.0v - 825 - 17,748.28      1.896 kW
s9j6 - 9.0v - 850 - 18,251.05      1.988 kW
s9j7 - 9.0v - 825 - 17,775.45      1.925 kW

Temp vary between 74 and 94 ( depending how hot is outside )

I can't find where i wrote exact power consumption of s9j2 as it is using 2 different PSU-s ( Bitmain-s PSU bugged out, decided not to give anymore power if it goes past 1500W, so it is powering 1 hashboard and control board only now while the other psu powers 2 hashboards )

s9j4 is the one that is having a faulted hashboard at the moment.

[Artemis3]

Well you know what to do. Take that unit apart, and test each board separately at normal (non overclocked) values, change power and data cables and see if there is any chance for the single board to work again.

Perhaps your last cleaning broke something...

At the end i would try it with BraiinsOS to see if the board only has lost sensors.

[taserz]

Yeah you're running a very balanced overclock. I would try what Artemis3 said.

[Scorpyy]

I have tried all suggestions above, except the one with BrainsOS because i have 0 knowledge in troubleshooting the hash board via it and i wasn't able to find any tutorial yet. I have found some videos on how to install it, but then i'm not really sure what they are doing from that point.

If you have any known tutorials for it please post it here so that we can help other people who experience this issue in future.

[BitMaxz]

Braiins OS already have step by step to make a bootable or flash the Braiins OS to nand.

You try to follow the Phase 1 from here https://docs.braiins-os.org/#phase-1-creating-bootable-sd-card-image-antminer-s9-example

Note: Just phase one don't go to Phase 2 because it will "Permanently Migrating it from Factory Firmware to Braiins OS" just use the bootable first to check if the 3rd hashboard will run at this OS it will bypass all sensor check.

If still the Chain[J8] showing no ASIC and no hashrate the hashboard might totally dead this is related to hardware issue.


Let me ask one more question how did you know that you are not infected?

If you never change the root password it is still possible that someone access the miner and put the virus to your network. I don't know if your miner is infected but why not try to clean your network first and maybe someone is hijacking your one hashboard. Try this one Viruses, malware and remote attacks on Antminers – How to prevent and remove them?

If all of these doesn't work I consider it as dead or hardware related issue.

[Scorpyy]

So in the meantime 1 more board on another miner stopped appearing. Then i finally decided to try BraiinsOS, and that board came back, however the first one ( original topic oriented ) is still missing.

https://prntscr.com/pdn1ou

If anyone knows how to troubleshoot further using BraiinsOS please let me know.

[BitMaxz]

If you did everything above possible this is a hardware related issue.

Find the hashboard which is not detected try to get the hashboard and put it to other working miner or swap. Then test it if it will work if not then your problem is under the hashboard. It could be shorted(short circuit) or some parts are burnt but try to clean the hashboard(the not working one) again with lacquer flo thinner and clean the power terminal and some parts with a brush then test it again.

If still doesn't work try to resolder the terminal the 6 pins and the 18 pins then test it again.