Troubleshooting · Antminer L9 · Find 0 ASIC · Hashboard Not Detected · Scrypt · LTC/DOGE
Antminer L9 "Chain Only Find 0 ASIC" — Hashboard Not Detected: Causes & Fix
If your Antminer L9 is running on two boards instead of three and the kernel log shows "Chain X only find 0 asic, will power off hash board X", the control board could not talk to a single chip on that hashboard. Here's what causes it, the checks that are safe to do yourself, and how the board is repaired when the fault is on the board itself.
- 0 ASIC
- No chip on the chain answered
- −⅓
- Hashrate lost per missing board
- 3
- Hashboards per L9
- 1–3 days
- Typical solo-miner repair
What "find 0 asic" means on an L9
Every time an Antminer L9 starts, the control board walks each of its three hashboard chains and asks every Scrypt chip to report in. When none of the chips on a chain answer, the kernel log shows a line like this:
What it looks like in the kernel log
Chain 1 only find 0 asic, will power off hash board 1
On some firmware it is followed by ERROR_SOC_INIT: soc init failed.
The miner then switches that board off and carries on with the other two, so you lose roughly one third of the L9's hashrate. Because the miner keeps running, this fault often goes unnoticed for days unless you watch per-board hashrate.
Zero is different from "fewer than expected". If a chain reports some chips but not all of them, the chain works up to a certain point and breaks further along — typically a failed chip or a dead voltage domain. "Find 0 asic" means the very first link failed, or the board never got usable signal or power at all.
Common L9 kernel log messages and what they mean
Search engines often send people here with a line copied straight from the log. These are the messages we see most often on L9s that come in with a missing board. Exact wording can vary slightly between firmware versions.
Chain X only find 0 asic, will power off hash board X
No chip on that chain answered, so the board was switched off
Cable and slot swap test, then bench diagnosis
check_asic_number_with_power_on: Chain[X]: find 0 asic
Same fault, reported during the power-on chip count
Same as above
ERROR_SOC_INIT: soc init failed
The miner could not initialise the chips on a chain
Usually follows a "find 0 asic" line — check that chain
Chain X only find N asic (fewer than the board should have)
The chain breaks part-way along — a failed chip or dead voltage domain
Bench repair at the position where the count stops
power voltage rise or drop / power voltage abnormity, pls check!
The control board saw the supply voltage go out of range
Check the PSU, power leads and site power
ERROR_POWER_LOST
Power fault detected, the miner stops hashing
PSU and power connections first
ERROR_TEMP_TOO_HIGH
Over-temperature protection shut the miner down
Cooling, fans and intake air — see our L9 overheating guide
ERROR_FAN_LOST
A fan is missing, unplugged or not spinning
Fan connectors and the fan itself
Causes, from simplest to most serious
Loose or damaged data cable
Error moves when you swap the cable
You — reseat or replace the cable
Control board port or firmware
Error stays on the same slot whichever board is in it
You — firmware update or SD-card recovery; otherwise control board repair
Power supply or power lead
Boards drop at start-up, sometimes more than one
You — test with a known-good PSU of the correct model
Board signal path or first chip
Error follows the board to any slot, no chips found
Bench repair — signal tracing and chip replacement
Shorted voltage domain or power-rail part
Board follows the error, may run hot or trip protection
Bench repair — short isolation and component replacement
Heat-damaged solder joints
Board found when cold, lost after warming up
Bench repair — rework of the failed joints
Safe checks you can do yourself
Bitmain's own guidance for a missing hashboard is to check the cables first and then try a firmware update or SD-card recovery, and it warns that blindly restarting a miner with a hardware fault can cause irreversible damage. Work through these in order, once:
Step 1
Save the kernel log
Copy the full log before you power-cycle. It lives in memory and is lost on reboot, and it tells a technician exactly which chain failed and how.
Step 2
Power off, then reseat the data cable
Unplug the miner, wait for it to discharge, and unplug and re-plug the data cable on both ends of the failed chain. Look for bent pins or burn marks.
Step 3
Swap the cable and the slot
Try a known-good cable, then move the board to another slot. Note whether the error stays with the slot, the cable or the board.
Step 4
Rule out the power supply
If you have a known-good PSU of the correct model, test with it. A weak PSU can fail to bring boards up at start-up.
Step 5
Update or recover the firmware
If the error stays with one slot, update the firmware or recover the control board from an SD card.
If the error follows the board to every slot, with a good cable and a good PSU, the fault is on the hashboard. Stop restarting the miner at that point — more power cycles on a shorted board can turn one failed part into several.
How we repair an L9 board that finds 0 ASIC
On the bench, the board goes on a test fixture that drives the chain directly, without the miner. We measure each voltage domain for shorts before applying full power, trace the clock, reset and data signals from the connector into the chain to see where they stop, and use thermal imaging under load to find a chip or power component that is not behaving. The failed part is replaced, the board's thermal interface is refreshed, and the board runs a full-load burn-in before it goes back.
A solo L9 is typically back in 1–3 days, and small batches are typically finished within 1–2 weeks. If the L9 is also running hot or slowly losing hashrate, read our L9 overheating and maintenance guide — heat is the most common reason an L9 board fails in the first place. For pricing and service details, see our Antminer L9 repair page.
Frequently asked questions
What does "Chain X only find 0 asic" mean on an Antminer L9?
During start-up the control board asks every chip on each hashboard to report in. "Find 0 asic" means not a single chip on that chain answered, so the miner powers that board off and keeps running on the others. The L9 then hashes at roughly two-thirds of its rated speed.
Is "find 0 asic" a cable problem or a dead hashboard?
It can be either. Power the miner off, reseat or swap the data cable, and move the board to another slot. If the error stays with the slot or the cable, the problem is there; if it follows the board wherever you put it, the fault is on the hashboard itself.
What is the difference between "find 0 asic" and finding fewer chips than expected?
Zero means nothing on the chain responded — usually a signal, power or first-chip problem. A partial count means the chain works up to a point and breaks further along, which usually points to a failed chip or a dead voltage domain at that position.
Should I keep restarting the L9 to see if the board comes back?
No. Bitmain warns that repeatedly restarting a miner with a hardware fault can make the damage worse. Save the kernel log, do the basic cable and slot checks once, and if the board still isn't found, have it diagnosed.
Can an L9 board with "find 0 asic" be repaired?
In most cases, yes. The fault is usually one failed component — a chip, a power-rail part, a connector or a cracked solder joint. It is found on a test fixture and repaired at the chip level, which costs far less than a replacement hashboard.
L9 running on two boards?
Get the missing L9 hashboard back
Chip-level L9 hashboard repair — solo miners typically in 1–3 days, small batches within 1–2 weeks. Mail-in or on-site across the USA.