A hashboard reported as "not detected" on an Antminer S19 does not necessarily mean the board has failed. First, confirm the missing chain on the miner's local interface and save the kernel log. Then check the signal-cable connection with the miner disconnected from power, review any logged faults, and confirm that the firmware matches the exact model. If the chain remains missing, use the collected evidence to request further diagnosis.

Zero hashrate alone does not confirm a missing hashboard. Fan, temperature, power, and network faults can also interrupt mining, so distinguish those conditions from a board-detection failure before deciding what needs repair.

Check for stop-use warning signs first

Before restarting the miner or carrying out physical checks, stop and seek qualified repair assistance if you notice:

• Visible burn marks, melted connectors, or heat-related discoloration
• A chemical or burning odor during operation
• Physical damage following an impact or drop

Do not keep restarting a miner with these signs. Disconnect power if it is safe to do so. Do not remove heatsinks, probe voltage rails, replace ASIC chips, or open the power supply as part of this guide. These checks do not cover component-level repairs or work inside high-voltage equipment.

Confirm the model and missing-board symptom

Record the exact S19 model and firmware version, then compare the local status page with the expected configuration for that model. Distinguish between two symptoms:

• A whole chain missing: an expected hashboard chain is absent. BITMAIN recommends checking that the cables are in good condition and correctly connected.
• A chain detected but with missing chips: the chain appears, but its ASIC count is below the expected count. BITMAIN lists PSU and grounding checks for this separate fault category; it should not automatically be treated as a failed board.

These are separate diagnostic paths in BITMAIN's 19-series troubleshooting guide. Record which chain is affected and whether it is absent or reporting fewer chips.

Capture logs before changing anything

Save the current kernel log while the fault is present. BITMAIN distinguishes current logs from historical logs and notes that historical storage is limited, so capture the evidence before a restart or firmware change.

Prepare:

• Exact miner model and serial number
• Current firmware version
• A screenshot showing the missing chain or unexpected chip count
• The current kernel log
• The affected chain identifier
• When the issue began, including any recent transport, cleaning, firmware update, or power event

Look for accompanying errors rather than diagnosing from the dashboard alone. BITMAIN's S19 zero-hashrate guidance identifies hashboard-version, PIC, temperature, and EEPROM errors among faults that can stop mining.

This material helps support personnel assess the problem. Treat it as a useful preparation checklist; the repair portal's current fields determine what is required when submitting a ticket.

Check connections, logged faults, and firmware

Inspect the signal-cable connection

Shut the miner down completely, disconnect all power connections, and let it cool before inspecting an internal cable. Never reseat connectors while the miner is energized.

If you are familiar with the model's service procedure, inspect the signal cable between the affected hashboard and control board for a loose connection, pinching, damage, or corrosion. Reseat an incompletely seated connector without forcing it. If access or the condition of the connector is uncertain, leave the check to qualified service personnel.

This follows BITMAIN's recommended first check for a missing hashboard; it does not establish how frequently cables cause the fault.

Review cooling and protection errors

Check the saved log and status information for fan or temperature faults. BITMAIN documents that fan failure and overtemperature protection can cut power to the hashboards and cause zero hashrate. That does not, by itself, establish that a particular chain is undetected.

Inspect for blocked airflow, dust, or recirculated hot exhaust. The 19-series troubleshooting guide recommends 5–35°C in its temperature guidance; check the documentation for your exact variant before applying that range.

Refer power-related faults for qualified diagnosis

If the log indicates a power fault, the PSU or power-control connections may need investigation. A qualified technician may use a known-good, compatible PSU as part of fault isolation. This is outside the basic cable inspection described above.

If the chain remains missing after a PSU substitution, further diagnosis is still needed. That result alone does not distinguish a hashboard fault from unresolved signal-cable or control-board-side problems. Do not open the PSU or attempt electrical measurements as part of this guide.

Check firmware compatibility

Record the installed firmware before making changes. Use only official firmware intended for the exact miner model and control-board version. Cross-model or third-party firmware is not a recommended troubleshooting step here.

If the issue started after an update, record that timing and retain any available logs from before and after it. Reinstallation should follow the relevant BITMAIN instructions or support advice for the logged fault; it is not a general fix for every missing hashboard.

After any appropriate basic check, reassess the local chain status and save a fresh log. If the fault persists or returns, stop repeating restarts and request further diagnosis.

Keep pool monitoring separate from board detection

A miner can detect its hashboards locally while pool-side activity is interrupted by a Stratum address, port, worker configuration, or network issue. Pool-side zero hashrate therefore cannot confirm a missing board.

ViaBTC's BTC mining guide recommends checking the Workers and Earnings pages after the miner has been stable for around 10–15 minutes. This is guidance on when to check mining activity, not a fixed data-refresh guarantee or a hardware-detection test.

Use the miner's local status and kernel log to assess board detection. Changing pool settings is not a remedy for a confirmed local missing-chain fault.

Prepare a repair request

If a chain remains undetected or repeatedly disappears, contact BITMAIN or a qualified repair provider with the evidence already gathered. Include the affected chain, fault timeline, and checks performed, alongside the model, serial number, firmware version, screenshots, and logs. Persistent PIC, EEPROM, temperature-sensor, or ASIC-related errors should also be included for diagnosis.

Follow the current BITMAIN repair-ticket instructions. They instruct customers to upload correct tracking information and dispatch the defective product within 7 days. This is a customer shipping deadline, not a promise that BITMAIN will return a repaired or replacement unit within 7 days. The instructions also require receipt within 15 days of ticket creation and warn that warranty coverage cannot be honored if a late-arriving product is received after its warranty period. Confirm the requirements applicable to your ticket before shipping.

Also confirm whether the receiving repair center accepts a single hashboard for your model and board type. For example, BITMAIN's S19k Pro guidance allows the aluminum-board version to be returned as a single board or complete miner, while the non-aluminum-board version requires the complete miner.

Use the applicable BITMAIN packaging recommendations, including suitable cushioning and anti-static protection. Confirm shipment eligibility with the receiving center before packing a board separately.

FAQ

Does a missing hashboard always mean the board has failed?

No. BITMAIN recommends checking cable condition and placement first for a missing hashboard. Confirm the affected chain and review the kernel log before deciding which component needs repair.

Can zero hashrate on the pool dashboard confirm a missing hashboard?

No. Pool-side hashrate depends on submitted shares and can be affected by connectivity or configuration problems. Check board detection on the miner's own interface and in its kernel log.

Is it safe to reseat hashboard cables myself?

Only attempt a signal-cable check if you are familiar with the model's service procedure and there are no damage or overheating warning signs. Completely disconnect power and let the miner cool first. If you are unsure, use qualified service personnel.

Will reinstalling firmware fix a missing hashboard?

Not reliably. Follow model-specific BITMAIN instructions or support advice for the logged fault. Use official firmware compatible with the exact model and control-board version.

What should I include in a repair request?

Prepare the model and serial number, firmware version, fault-state kernel log, status screenshot, affected chain, and a brief account of when the issue began and what checks were performed. Follow the repair portal's current submission requirements.

References

• BITMAIN, Common Problems and Solutions for ANTMINER (19 series)
• BITMAIN, Solution of Zero Hashrate on S19 Miner
• BITMAIN, How to create or edit an Apply for Repair ticket
• BITMAIN, How to distinguish S19k Pro hashboard types and the repair related precautions
• BITMAIN, Packaging Recommendations for Returning ANTMINERs for Repair
• ViaBTC Help Center, BTC Mining