Antminer S19k Pro – Hashboard Not Detected
Critical — Immediate action required
Symptoms
- Web UI shows 2/3 or 1/3 hashboards detected; the missing chain reads 0 chips, `--` temperature, and 0 GH/s
- Realised hashrate drops to ~76 TH/s (one board lost) or ~38 TH/s (two lost) on a 115-120 TH/s nameplate S19k Pro
- `kern.log` shows `check_asic_number_with_power_on: Chain[X]: find 0 asic` repeating at boot
- `kern.log` shows `Chain X only find 0 ASICs, will power off hash board X`
- `kern.log` shows `fail to read pic temp for chain X` — points at PIC chip / I2C path on that hashboard
- Pool side: one worker entry flagged `Dead` or contributing zero shares, others hashing normally
- Red LED on the control board's chain-status indicator; fans still ramp, network UI reachable
- Dead board was handled recently — shipped, re-racked, thermal-cycled from cold garage to full load, or bumped during cleaning
- Previous OC / UV profile pushed BM1398 frequency above ~675 MHz or chip voltage below spec floor, fault appeared after next reboot
- Intermittent drop: enumerates on cold boot, fails within 20-120 minutes under load, recovers on power-cycle — cap creep or reflow-joint fatigue
- Burnt-electrolytic or rosin smell from one board; visible discolouration near PMIC, 19 V boost input caps, or a specific chip position
- Multimeter at the hashboard 6-pin power connector under load reads 0 V on the dead slot, or sags below 11.6 V
Step-by-Step Fix
Hard power-cycle at the PDU for 60 seconds — not a soft reboot, a physical disconnect. Clears wedged driver state from the previous boot and gives the Zynq SoC a clean power-on reset, which re-enumerates a marginal hashboard that failed on a soft restart. First move on every ticket, costs nothing, closes roughly 10% of cases on its own.
Open the chassis with power off at the breaker. Confirm which chain is missing by checking the web UI / kernel log. Reseat the three ribbon cables and both 6-pin PCIe power connectors on the affected slot; listen for the click. Inspect each contact for blackening, corrosion, or mechanical damage before reconnecting. S19k Pro ribbons are friction-fit and walk loose under thermal cycling — this step alone closes roughly 40% of D-Central's remote-support tickets on this error before the customer ships.
Shop-vac dust from the hashboard stack, intake grille, and PSU intake. Dust accumulation raises BM1398 junction temp, and thermal stress is the proximate cause of most ribbon-walk and cap-drift failures downstream. Cleaning does not fix an already-failed board but it is a free prerequisite before chasing silicon, and it extends the life of the surviving chains.
Check Bitmain firmware version at support.bitmain.com/downloads. Roll one version back or forward if you are on a known-buggy build for your BHB56902 hardware revision. Some early S19k Pro firmware builds shipped with aggressive chain-init timeouts that flagged healthy boards as missing; a firmware roll-back is a five-minute fix that works on roughly 1 in 20 tickets. Verify the hardware table before flashing — wrong firmware for your revision bricks the control board.
Verify PSU health. Bitmain APW-family PSUs age, and a tired PSU on one output leg can cause the hashboard on that leg to brown out at boot. Swap in a known-good replacement PSU (APW12-class or APW171215a rated for the S19k Pro's ~3250 W steady-state draw) for a 15-minute test before you dig deeper into the hashboard itself. This isolates the PSU from the board.
Slot-swap isolation test. Label slots 0 / 1 / 2 with tape. Move the suspect board to a known-good slot and a known-good board into the suspect slot. Power up, check enumeration. Fault follows the board = board-level problem (ribbon/PIC/chip/PMIC). Fault stays in the slot = control-board, ribbon, or rail problem. This single test saves roughly 30 minutes of downstream diagnosis on every ticket and prevents replacing the wrong component.
Measure the 12 V hashboard rail at the 6-pin PCIe connector under load with a multimeter on DC. Probe while the miner is powering up the chain (post-boot, during the ~30-second power-on window before the control board gives up). Expect ~12.0-12.4 V steady. Below 11.6 V, or a rail that sags when the chain attempts to draw, points at a tired PSU output or a cable problem. Swap the cable first, PSU second.
Probe the 19 V boost output on the hashboard itself. Position varies by BHB56902 revision — the Zeus Mining S19 Pro reference documents C55 as the output test point on the S19 Pro board, and the S19k Pro layout is similar; verify against your specific revision before probing. A dead 19 V rail on a healthy 12 V input means the input-side boost converter has failed — proceed to Tier 3 component-level work or ship to D-Central.
Inspect the input-side electrolytics and MOS tubes visually. Bulged 470 uF / 1000 uF electrolytics near the input, discoloured PCB near a MOSFET, or a burnt-rosin smell are all terminal for that component. Photograph the damage before you touch anything so you have a record for the D-Central intake form if you decide to ship. Do not attempt to hand-desolder bulged caps on an energised board — power off first.
Reseat the ribbon cable at both ends, inspect for oxidation and bent pins, swap with a known-good ribbon if available. Ribbons are consumables on mining hardware — the FFC contacts oxidise over 3-5 years of continuous thermal cycling, and a bad ribbon manifests as exactly this error. Spares cost $5-15 each; order a handful and save yourself a repair invoice down the line.
Flash DCENT_OS, Braiins OS+, LuxOS, or Vnish for per-chip chain visibility. DCENT_OS is D-Central's own open-source Antminer firmware — per-chip HW% visibility, autotuning, chain diagnostics, and stratum v2 support, open-source, maintained by the Mining Hackers, no licensing fees or vendor lock-in. Let the miner stabilise 20 minutes then identify whether the 'not detected' chain has a single broken chip position versus a systemic failure. Single biggest diagnostic upgrade on S19k Pro repair work.
Apply the dichotomy method to isolate the dead chip. Short RO and 1V8 between chips at the chain midpoint — S19 Pro reference: between the 38th and 39th chip; verify BHB56902 split-point before cutting in. If the chain enumerates as half-present after the short, the dead chip is in the other half. Binary-search down to a single chip position. Canonical Zeus Mining repair procedure for the S19 family; works on the S19k Pro with position adjustment per the board revision.
Reflow the suspected dead BM1398AH chip. Remove the heatsink, flux the BGA, preheat bottom side to ~150 C, top-side hot air at 310-330 C for roughly 30 seconds. Cool naturally — forced cooling cracks joints. Re-apply thermal paste (Arctic MX-6 or Thermal Grizzly Kryonaut), reassemble. BM1398 packages tolerate one reflow cycle reliably; a second reflow on the same chip rarely helps and signals the chip needs replacement.
Replace a failed PIC microcontroller. If diagnostic Step 5 isolated a PIC communication failure and a firmware reflash through Bitmain's hash board code editor tool did not clear it, the PIC chip itself is dead. Desolder the PIC16F1704-class part, fit a new one, program it with the stock hash-board firmware image for your BHB56902 revision. Soldering-iron + programmer job, not a reflow job. Success on roughly 1 in 3 'dead board' intakes where kern.log pointed at the PIC.
Swap the input-side boost circuit components. Bulged input caps (470 uF / 1000 uF electrolytics are the common suspects), a blown MOS tube, or a shorted boost inductor — all bench-replaceable with generic parts matched to the board's markings. Verify the 19 V boost output at the test point after the repair before you re-install the board in the chassis. Skipping the post-repair verification wastes a reassembly cycle.
Roll firmware to a known-good version for your specific BHB56902 hardware revision. Verify the hardware table at support.bitmain.com before flashing. Flashing a firmware built for a different S19 variant on the S19k Pro control board will brick the unit — budget an extra hour and a spare SD card if you are wrong about the revision. Take a note of your current version before you start.
Stop DIY when: two hashboards show the same failing chip position (PCB-level issue); PMIC or voltage-domain IC is suspected (visible heat damage, short to ground, PMIC sanity check failing); a reflowed chip fails again within 30 days; bulged caps beyond the input-side boost circuit; any burnt-component smell you cannot localise. Book a D-Central ASIC Repair slot at https://d-central.tech/services/asic-repair/ — 5-10 business day turnaround Canada-wide, US and international accepted.
What D-Central does at the bench: BHB56902-specific test fixture with programmable load, per-chip isolation using Bitmain test binaries matched to the hardware revision, BM1398AH chip replacement from graded inventory (new-old-stock and salvage-grade), full reflow and reseal, PIC reprogramming where needed, PMIC and voltage-domain IC component-level swap, 24-hour burn-in at nameplate to confirm stability before return shipping.
Ship safely. Anti-static bags on each board, double-boxed with at least 5 cm of foam on every side. Include a note with: observed symptoms, firmware version, kernel log excerpt, whatever you have already tried, and your contact info. Saves us diagnostic time, saves you money on the invoice. Canadian customers: Canada Post Expedited with signature is the reliable default; US / international welcome, duties and GST at your side.
Decide repair vs replace before you pull the trigger on either. S19k Pro hashboards run $400-700 CAD on the secondary market for salvaged-grade stock. D-Central component-level repair is typically $100-300 CAD per board. If two of three boards on the same rig are marginal, repair both in one bench visit — consolidated bench setup saves you the second invoice's fixed overhead. At sub-$0.08/kWh power, repair is almost always the better ROI than migrating to S21.
When to Seek Professional Repair
If the steps above do not resolve the issue, or if you are not comfortable performing these repairs yourself, professional service is recommended. Attempting advanced repairs without proper equipment can cause further damage.
Related Error Codes
Still Having Issues?
Our team of Bitcoin Mining Hackers has been repairing ASIC miners since 2016. We have seen it all and fixed it all. Get a professional diagnosis.
