Antminer S19a Pro just stopped hashing all of a sudden

Hey everyone, my Antminer S19a has just randomly stopped hashing. I tried unplugging it and plugging it back in, but no luck. It just reboots and the real-time hash rate is showing 0. Here are the logs from the miner. Normal zone: 0 pages set aside Normal zone: 61440 pages, LIFO batch:15 percpu: Embedded 12 pages/cpu @cddf0000 s19916 r8192 d21044 u49152 pcpu-alloc: s19916 r8192 d21044 u49152 alloc=12*4096 pcpu-alloc: 0 1 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960 Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk PID hash table entries: 1024 (order: 0, 4096 bytes) Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 209668K/245760K available (6317K kernel code, 243K rwdata, 1932K rodata, 1024K init, 232K bss, 19708K reserved, 16384K cma-reserved, 0K highmem) Virtual kernel memory layout: vector : 0xffff0000 0xffff1000 ( 4 kB) fixmap : 0xffc00000 0xfff00000 (3072 kB) vmalloc : 0xcf800000 0xff800000 ( 768 MB) lowmem : 0xc0000000 0xcf000000 ( 240 MB) pkmap : 0xbfe00000 0xc0000000 ( 2 MB) modules : 0xbf000000 0xbfe00000 ( 14 MB) .text : 0xc0008000 0xc090e410 (9242 kB) .init : 0xc0a00000 0xc0b00000 (1024 kB) .data : 0xc0b00000 0xc0b3cda0 ( 244 kB) .bss : 0xc0b3cda0 0xc0b77024 ( 233 kB) Preemptible hierarchical RCU implementation. Build-time adjustment of leaf fanout to 32. RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2. RCU: Adjusting geometry for r

you may have a bad pool  it claims you have good status but in a ½ hour time period it reads 0 hashrate.  your pool you are mining to may have an issue. "2024-05-02 09:09:50 STATUS_OKAY 2024-05-02 09:09:50 start the cached job 2024-05-02 09:09:50 Version num 8 2024-05-02 09:09:50 Mask num 0xe000 2024-05-02 09:09:50 freq = 575, percent = 90, hcn = 11392, timeout = 410 2024-05-02 09:09:50 set_start_time_point total_tv_start_sys=130 total_tv_end_sys=131 2024-05-02 09:39:27 avg rate is lower than ideal rate, 0.00 in 31 mins 2024-05-02 10:09:28 avg rate is lower than ideal rate, 0.00 in 29 mins 2024-05-02 10:39:29 avg rate is lower than ideal rate, 0.00 in 30 mins 2024-05-02 11:09:29 avg rate is lower than ideal rate, 0.00 in 30 mins 2024-05-02 11:39:30 avg rate is lower than ideal rate, 0.00 in 30 mins 2024-05-02 12:09:31 avg rate is lower than ideal rate, 0.00 in 30 mins 2024-05-02 12:39:32 avg rate is lower than ideal rate, 0.00 in 30 mins 2024-05-02 13:09:33 avg rate is lower than ideal rate, 0.00 in 30 mins 2024-05-02 13:39:34 avg rate is lower than ideal rate, 0.00 in 30 mins 2024-05-02 14:09:35 avg rate is lower than ideal rate, 0.00 in 30 mins 2024-05-02 14:39:36 avg rate is lower than ideal rate, 0.00 in 30 mins" what pool are you pointed to? you could try a different one

Same here I can't see anything weird from the logs. Anyway, incase the above suggestion do not work you can try to let it run it first for 1 hour and then factory reset the unit by holding the IP report button for 5 seconds then setup the pool config and make sure you paste/type it with no extra spaces then test it again. Other possible solution for 0 hashrate you can get idea from this link below. - https://www.zeusbtc.com/articles/asic-miner-troubleshooting/4501-zero-hash-rate-solution-for-s19-miners

There may be a problem with the hash rate of a certain ASIC chip. You need to check the status of the hash board on the WEB page. If the hash rate is 0, you need to use the test fixture to run the PT1+ or PT2 test to find the faulty chip.