Antminer s9 keeps restarting or rebooting?

[Katanabits]

Hi just online back again because i need help to experience how to fix the antminer s9 always restarting?
I bought this miner few weeks ago and it's running fine for few days now the miner is always restarting I dont know why.

can you help please?

[BitMaxz]

Have you tried to factory reset the miner? If not, you can follow this guide from here 3 ways to restore factory the s9 miner.

After that set the fan speed to high speed you can find the fan speed in secret menu if you don't know how to do this you can follow the guide from here https://bitcointalk.org/index.php?topic=2690140.0  

If the above solution doesn't work you can post the kernel logs here so that we can easily spot the problem. You can find the kernel logs from the miner dashboard> system >kernel logs. Then paste it here or in http://pastebin.com/

[PassThePopcorn]

What's in the /config/ folder when you SSH into it?

[mikeywith]

check the temps, S9 auto reboot when temps are high

[fanatic26_]

check the temps, S9 auto reboot when temps are high

This is not true...they will stall out and stop when they hit the overheating limit but do not auto restart. The status page will show the last status when it was mining, but otherwise it will just sit there until manually rebooted from heat issues.

[mikeywith]

This is not true...they will stall out and stop when they hit the overheating limit but do not auto restart. The status page will show the last status when it was mining, but otherwise it will just sit there until manually rebooted from heat issues.

maybe it's different from a firmware to another, but i am 100% sure that many of my S9s rebooted a few times when temps where high. i think your scenario happens when you check " stop running when temp is over 80c ", at that point the miner might stall, other wise if it passes i think "115c" it will restart.

[BitcoinRack]

We had a batch of 60 S9s sent to one of our facilities brand new from Bitmain. At least 10 of them began to do this after just one month. After a lot of trial and error, it was found to be faulty fans. Bitmain admitted to us that they had some fans with issues causing this. It may be worth a shot swapping out the fans.

On another note, sometimes firmware updates can be iffy. Sometimes when not fully successful, the chip temps or the fan RPMs will not be read correctly. This will cause the miner to continually reboot. Reverting back to an older firmware and running it for 15 minutes can rule this out.

[tim-bc]

Most commonly I have seen this as a PSU issue. Check on your PSU and power arrangement, and swap out PSU / cords etc. to see if that makes a difference.

[papampi]

I have seen this problem on faulty PSU too, swap it and see how it goes.

[fanatic26_]

I also vote PSU as the first thing to check on. It soudns like its hitting its power limit randomly and going into protect for a moment which causes a reboot similar to unplugging and plugging the PSU back in

[minerdady4]

My Antminer s9 keeps reverting back to an old URL and worker address and its extremely frustrating because every few hrs, or even minutes sometimes, it will revert back to a previously loaded URL and worker address.  I have swapped out the PS and also tried uploading new firmware, but oddly, it gives me an error code everytime i try to upload the firmware.  its almost like the previous owner ran code into it so that it constantly reverts, so that when I am not paying attention, it starts paying him.  Please help....Below is the kernal log:

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.14.0-xilinx-ge8a2f71-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #82 SMP PREEMPT Tue May 16 19:49:53 CST 2017
[    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 c0740a40, 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
• 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: 364356K/507904K available (5032K kernel code, 283K rwdata, 1916K rodata, 204K init, 258K bss, 143548K 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 - 0xc06d1374   (6949 kB)
[    0.000000]       .init : 0xc06d2000 - 0xc0705380   ( 205 kB)
[    0.000000]       .data : 0xc0706000 - 0xc074cf78   ( 284 kB)
[    0.000000]        .bss : 0xc074cf84 - 0xc078d9fc   ( 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.000311] ps7-ttc #0 at df804000, irq=43
[    0.000626] Console: colour dummy device 80x30
[    0.000657] Calibrating delay loop... 1325.46 BogoMIPS (lpj=6627328)
[    0.040208] pid_max: default: 32768 minimum: 301
[    0.040433] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.040455] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.042615] CPU: Testing write buffer coherency: ok
[    0.042962] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.043023] Setting up static identity map for 0x4c4b00 - 0x4c4b58
[    0.043248] L310 cache controller enabled
[    0.043268] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[    0.121044] CPU1: Booted secondary processor
[    0.210228] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.210363] Brought up 2 CPUs
[    0.210381] SMP: Total of 2 processors activated.
[    0.210390] CPU: All CPU(s) started in SVC mode.
[    0.211067] devtmpfs: initialized
[    0.213486] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.214742] regulator-dummy: no parameters
[    0.223731] NET: Registered protocol family 16
[    0.225999] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.228335] cpuidle: using governor ladder
[    0.228349] cpuidle: using governor menu
[    0.235903] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[    0.237452] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.237466] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.237587] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xdf880000
[    0.259996] bio: create slab <bio-0> at 0
[    0.262127] vgaarb: loaded
[    0.262850] SCSI subsystem initialized
[    0.263727] usbcore: registered new interface driver usbfs
[    0.263903] usbcore: registered new interface driver hub
[    0.264130] usbcore: registered new device driver usb
[    0.264661] media: Linux media interface: v0.10
[    0.264821] Linux video capture interface: v2.00
[    0.265062] pps_core: LinuxPPS API ver. 1 registered
[    0.265074] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.265197] PTP clock support registered
[    0.265553] EDAC MC: Ver: 3.0.0
[    0.266623] Advanced Linux Sound Architecture Driver Initialized.
[    0.269578] DMA-API: preallocated 4096 debug entries
[    0.269593] DMA-API: debugging enabled by kernel config
[    0.269686] Switched to clocksource arm_global_timer
[    0.290536] NET: Registered protocol family 2
[    0.291213] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.291271] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    0.291356] TCP: Hash tables configured (established 4096 bind 4096)
[    0.291407] TCP: reno registered
[    0.291425] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.291459] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.291718] NET: Registered protocol family 1
[    0.292102] RPC: Registered named UNIX socket transport module.
[    0.292114] RPC: Registered udp transport module.
[    0.292122] RPC: Registered tcp transport module.
[    0.292130] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.292144] PCI: CLS 0 bytes, default 64
[    0.292597] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.294675] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.296858] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.297047] msgmni has been set to 967
[    0.297845] io scheduler noop registered
[    0.297858] io scheduler deadline registered
[    0.297909] io scheduler cfq registered (default)
[    0.312321] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[    0.312342] dma-pl330 f8003000.ps7-dma:    DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.437254] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[    1.005652] console [ttyPS0] enabled
[    1.009987] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to df866000
[    1.017641] [drm] Initialized drm 1.1.0 20060810
[    1.034739] brd: module loaded
[    1.044177] loop: module loaded
[    1.053796] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    1.059545] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[    1.067450] libphy: XEMACPS mii bus: probed
[    1.071850] ------------- phy_id = 0x3625e62
[    1.076592] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[    1.085467] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.092125] ehci-pci: EHCI PCI platform driver
[    1.099368] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[    1.106451] usbcore: registered new interface driver usb-storage
[    1.113379] mousedev: PS/2 mouse device common for all mice
[    1.119508] i2c /dev entries driver
[    1.126481] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[    1.132054] cpufreq_cpu0: failed to get cpu0 regulator: -19
[    1.137950] Xilinx Zynq CpuIdle Driver started
[    1.142829] sdhci: Secure Digital Host Controller Interface driver
[    1.148922] sdhci: Copyright(c) Pierre Ossman
[    1.153334] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.160096] mmc0: no vqmmc regulator found
[    1.164108] mmc0: no vmmc regulator found
[    1.199722] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[    1.208407] usbcore: registered new interface driver usbhid
[    1.213922] usbhid: USB HID core driver
[    1.218639] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.224941] nand: Micron MT29F2G08ABAEAWP
[    1.228904] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[    1.234851] Bad block table found at page 131008, version 0x01
[    1.241093] Bad block table found at page 130944, version 0x01
[    1.247149] 3 ofpart partitions found on MTD device pl353-nand
[    1.252919] Creating 3 MTD partitions on "pl353-nand":
[    1.258020] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[    1.266111] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[    1.273434] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[    1.282450] TCP: cubic registered
[    1.285690] NET: Registered protocol family 17
[    1.290420] Registering SWP/SWPB emulation handler
[    1.296332] regulator-dummy: disabling
[    1.300767] UBI: attaching mtd1 to ubi0
[    1.828510] UBI: scanning is finished
[    1.840293] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[    1.847344] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.854142] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.860817] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.867655] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[    1.873665] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.880776] UBI: max/mean erase counter: 22/12, WL threshold: 4096, image sequence number: 1283732989
[    1.889979] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[    1.899177] UBI: background thread "ubi_bgt0d" started, PID 1080
[    1.899182] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.903220] ALSA device list:
[    1.903225]   No soundcards found.
[    1.919629] UBIFS: background thread "ubifs_bgt0_0" started, PID 1082
[    1.948962] UBIFS: recovery needed
[    2.055871] UBIFS: recovery completed
[    2.059543] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    2.065488] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.074592] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    2.084481] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.089512] UBIFS: media format: w4/r0 (latest is w4/r0), UUID C72F8006-6DFF-46BA-BBE9-380960A89F92, small LPT model
[    2.101288] VFS: Mounted root (ubifs filesystem) on device 0:11.
[    2.108711] devtmpfs: mounted
[    2.111846] Freeing unused kernel memory: 204K (c06d2000 - c0705000)
[    2.961345] random: dd urandom read with 0 bits of entropy available
[    3.359720]
[    3.359720] bcm54xx_config_init
[    3.969718]
[    3.969718] bcm54xx_config_init
[    7.970549] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[    7.976655] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
[   22.812698] In axi fpga driver!
[   22.815768] request_mem_region OK!
[   22.819198] AXI fpga dev virtual address is 0xdf9fc000
[   22.824264] *base_vir_addr = 0x8c510
[   22.840185] In fpga mem driver!
[   22.843257] request_mem_region OK!
[   22.846821] fpga mem virtual address is 0xe2000000
[   23.879145]
[   23.879145] bcm54xx_config_init
[   24.959047]
[   24.959047] bcm54xx_config_init
[   28.959420] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[   28.965529] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
This is XILINX board. Totalram:       507527168
Detect 512MB control board of XILINX
DETECT HW version=0008c510
miner ID : 814c840c6880881c
Miner Type = S9
AsicType = 1387
real AsicNum = 63
use critical mode to search freq...
get PLUG ON=0x000000e0
Find hashboard on Chain[5]
Find hashboard on Chain[6]
Find hashboard on Chain[7]
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
chain[5]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
has freq in PIC, will disable freq setting.
chain[5] has freq in PIC and will jump over...
Chain[5] has core num in PIC
Chain[5] ASIC[0] has core num=1
Chain[5] ASIC[1] has core num=1
Chain[5] ASIC[2] has core num=1
Chain[5] ASIC[3] has core num=2
Chain[5] ASIC[4] has core num=1
Chain[5] ASIC[5] has core num=1
Chain[5] ASIC[6] has core num=1
Chain[5] ASIC[7] has core num=1
Chain[5] ASIC[8] has core num=1
Chain[5] ASIC[9] has core num=1
Chain[5] ASIC[10] has core num=1
Chain[5] ASIC[11] has core num=1
Chain[5] ASIC[12] has core num=1
Chain[5] ASIC[13] has core num=2
Chain[5] ASIC[14] has core num=1
Chain[5] ASIC[15] has core num=1
Chain[5] ASIC[16] has core num=3
Chain[5] ASIC[17] has core num=1
Chain[5] ASIC[18] has core num=1
Chain[5] ASIC[19] has core num=2
Chain[5] ASIC[20] has core num=1
Chain[5] ASIC[21] has core num=1
Chain[5] ASIC[22] has core num=1
Chain[5] ASIC[23] has core num=1
Chain[5] ASIC[24] has core num=1
Chain[5] ASIC[25] has core num=1
Chain[5] ASIC[26] has core num=1
Chain[5] ASIC[27] has core num=2
Chain[5] ASIC[29] has core num=1
Chain[5] ASIC[30] has core num=2
Chain[5] ASIC[31] has core num=1
Chain[5] ASIC[32] has core num=1
Chain[5] ASIC[33] has core num=1
Chain[5] ASIC[34] has core num=1
Chain[5] ASIC[36] has core num=1
Chain[5] ASIC[37] has core num=1
Chain[5] ASIC[38] has core num=1
Chain[5] ASIC[39] has core num=1
Chain[5] ASIC[40] has core num=1
Chain[5] ASIC[41] has core num=1
Chain[5] ASIC[42] has core num=1
Chain[5] ASIC[43] has core num=1
Chain[5] ASIC[44] has core num=1
Chain[5] ASIC[45] has core num=1
Chain[5] ASIC[47] has core num=1
Chain[5] ASIC[48] has core num=1
Chain[5] ASIC[49] has core num=1
Chain[5] ASIC[50] has core num=1
Chain[5] ASIC[51] has core num=1
Chain[5] ASIC[52] has core num=1
Chain[5] ASIC[53] has core num=1
Chain[5] ASIC[54] has core num=2
Chain[5] ASIC[55] has core num=1
Chain[5] ASIC[56] has core num=1
Chain[5] ASIC[57] has core num=1
Chain[5] ASIC[59] has core num=1
Chain[5] ASIC[60] has core num=1
Chain[5] ASIC[61] has core num=2
Chain[5] ASIC[62] has core num=1
Check chain[5] PIC fw version=0x03
chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
has freq in PIC, will disable freq setting.
chain[6] has freq in PIC and will jump over...
Chain[6] has core num in PIC
Chain[6] ASIC[1] has core num=2
Chain[6] ASIC[2] has core num=1
Chain[6] ASIC[3] has core num=2
Chain[6] ASIC[4] has core num=1
Chain[6] ASIC[5] has core num=1
Chain[6] ASIC[6] has core num=1
Chain[6] ASIC[7] has core num=1
Chain[6] ASIC[8] has core num=2
Chain[6] ASIC[9] has core num=1
Chain[6] ASIC[10] has core num=1
Chain[6] ASIC[11] has core num=1
Chain[6] ASIC[12] has core num=2
Chain[6] ASIC[13] has core num=1
Chain[6] ASIC[14] has core num=2
Chain[6] ASIC[15] has core num=1
Chain[6] ASIC[16] has core num=4
Chain[6] ASIC[17] has core num=1
Chain[6] ASIC[18] has core num=2
Chain[6] ASIC[20] has core num=1
Chain[6] ASIC[21] has core num=1
Chain[6] ASIC[22] has core num=2
Chain[6] ASIC[23] has core num=1
Chain[6] ASIC[24] has core num=1
Chain[6] ASIC[25] has core num=1
Chain[6] ASIC[26] has core num=1
Chain[6] ASIC[27] has core num=2
Chain[6] ASIC[28] has core num=1
Chain[6] ASIC[29] has core num=1
Chain[6] ASIC[30] has core num=2
Chain[6] ASIC[31] has core num=1
Chain[6] ASIC[32] has core num=1
Chain[6] ASIC[33] has core num=1
Chain[6] ASIC[34] has core num=1
Chain[6] ASIC[35] has core num=1
Chain[6] ASIC[36] has core num=1
Chain[6] ASIC[37] has core num=1
Chain[6] ASIC[38] has core num=1
Chain[6] ASIC[39] has core num=1
Chain[6] ASIC[40] has core num=1
Chain[6] ASIC[41] has core num=1
Chain[6] ASIC[42] has core num=1
Chain[6] ASIC[43] has core num=1
Chain[6] ASIC[44] has core num=1
Chain[6] ASIC[45] has core num=1
Chain[6] ASIC[46] has core num=2
Chain[6] ASIC[47] has core num=1
Chain[6] ASIC[48] has core num=1
Chain[6] ASIC[49] has core num=1
Chain[6] ASIC[50] has core num=1
Chain[6] ASIC[51] has core num=1
Chain[6] ASIC[52] has core num=1
Chain[6] ASIC[53] has core num=1
Chain[6] ASIC[54] has core num=2
Chain[6] ASIC[55] has core num=1
Chain[6] ASIC[56] has core num=1
Chain[6] ASIC[57] has core num=1
Chain[6] ASIC[58] has core num=1
Chain[6] ASIC[59] has core num=1
Chain[6] ASIC[60] has core num=1
Chain[6] ASIC[61] has core num=1
Check chain[6] PIC fw version=0x03

[BitMaxz]

My Antminer s9 keeps reverting back to an old URL and worker address and its extremely frustrating because every few hrs, or even minutes sometimes, it will revert back to a previously loaded URL and worker address.  I have swapped out the PS and also tried uploading new firmware, but oddly, it gives me an error code everytime i try to upload the firmware.  its almost like the previous owner ran code into it so that it constantly reverts, so that when I am not paying attention, it starts paying him.  Please help....Below is the kernal log:

That's a different issue than the OP next time make a new thread about your issue.

Yours is common mostly hacked or sold miners from 3rd party that has this kind of issues.

The only thing that I could suggest about your issue is to try to flash it through an SD card if you don't know how to do it you can follow the guide from this link below.
- https://support.bitmain.com/hc/en-us/articles/360019493654-S9-series-S9-S9i-S9j-S9-Hydro-Control-Board-Program-Recovery

If it still doesn't work I suggest make another thread about this here in the same section. So that other experts are aware and to get some advice and better solution to your problem.

[OldRadio]

I've owned hundreds of Antminers in the past year.  Presently I have 100+ of which I run approximately 25 at any given time.  ALL are on mobile racks and each rack mines a different algorithm/crypto.  I can mine ONLY two racks at a time due to electricity availability at my operation.  

Anyway.  I just spent the last 8 hours trying to diagnose a restart/reboot situation on an Antminer Z9 machine that has been running flawlessly up until yesterday.  Suspecting a bad hashboard, I unplugged ALL three of the hashboards and ran the machine with ONE at a time plugged in.  All three hashboards were fine and the machine would run fine with only ONE plugged in at a time.  BUT, as soon as any "two" were plugged in, "poof" restart and reboot every 60 seconds.  

It was through this posting that I decided to swap out the power supply and "VOILA"!!!  Yes INDEED, a faulty power supply that APPEARS to be working fine can be a "RESTART", "REBOOT" issue when this occurs.  The Antminer that I swapped out the power supply for is once again running LIKE A CHAMP!!

Yes, I do own "several" multi-meters and in the future, I will expedite this diagnostic "scenario" in the future.  If this ever occurs to me again, I will do DC VOLTAGE and DC AMPERE measurement before spending hours and hours and hours of "lost" time before swapping, plugging, flashing and pulling my hair out again!!  It's 8:00AM here, I started on my "restart/reboot" issue 10 hours ago and THANK GOD IT'S FIXED!!!  Drinking two pots of coffee and staying up ALL NIGHT to fix a machine is no fun!!

THANK YOU FOR THIS POST!! It's been "GOLD" in helping me find the solution to what could/should have been a very simple diagnosis for me.  The difficult problems I solve easily; the simple things take me a while..  

THANK YOU!!!  
THANK YOU!!!  
THANK YOU!!!  

Old`RADIO

[bittalk7]

wasn't PSU for me, I had a fan not working and that will get your machine to reboot. Took me about 5 hours to diagnose it lol!