Whatsminer Error 2010 – All Pools Disabled
Warning — the hashboards are fine, the chips are fine, the firmware is fine
Warning — Should be addressed soon
Symptoms
- WhatsminerTool error log returns exactly `2010` — **not** `2000` (no pool info configured), `2020` / `2021` / `2022` (Pool 0 / Pool 1 / Pool 2 individual handshake fail), `2030` (high rejection rate), or `2040` (ASICboost not supported)
- `btminer.log` shows the literal line `all pools disabled for 2s` repeating every two seconds from boot forward
- Dashboard `GHSavg` reads `0.00 GH/s` — clean zero, not a degraded value — while the chassis shows `alive` and `boards: 3/3`
- Hashboard temperatures read normal (`50-75 °C` under the fan-floor behaviour, sometimes cooler because no hashing is happening)
- Fans ramp to `~40-60%` and hold steady — the chassis is alive and thermally balanced, just not submitting work
- Pool-side dashboard (F2Pool, Slush, Braiins, ViaBTC, solo.ckpool.org, Public Pool, etc.) shows the worker as `offline` or `never connected` — not as `connected but submitting stale shares`
- `cgminer`-style API query on TCP `4028` (`curl -s http://<miner-ip>:4028 -d '{"cmd":"pools"}'`) returns the three pool slots with `Status: Disabled` or empty URL fields — the authoritative confirmation
- LED on the control board sits in the standard operating pattern (solid or slow blink), not the red-fault pattern — `2010` does not trigger the fault LED because it isn't a hardware event
- Recent event: factory reset, firmware flash, config import from another miner, wallet address rotation, or password change on the pool account
- A known-good sibling miner on the same LAN with the same pool config **is** mining — isolates the fault to this specific miner rather than an upstream pool outage
- Behavior is persistent across at least two full cold cycles — not an intermittent ghost
- The `btminer.log` does not show any `chip_id` failures, `SM not found`, `psu_fault`, or thermal codes adjacent to the `2010` lines — the rest of the chassis is healthy
Step-by-Step Fix
Pull the BTMiner log via WhatsminerTool and confirm the exact error line Expected: log shows `all pools disabled for 2s` repeating every 2s with code `2010` If the line reads `2000` / `2020-2022` / `2030`: wrong page, see per-code remediation
Open Pool Configuration in WhatsminerTool and inspect all three slots Expected: Pool 0, Pool 1, Pool 2 each show stratum URL, worker, password If any slot is empty / shows placeholder / has trailing characters: re-enter that slot
Ping the primary pool host from a sibling machine on the same LAN Expected: ping returns < 100ms, no packet loss If ping fails: network / DNS / ISP / firewall fault — fix network first
Port test the stratum port from a sibling machine on the same LAN Expected: `nc -vz <pool-host> <port>` returns `Connection succeeded` If port test fails: firewall / ISP / VPN blocking outbound stratum — fix network
Verify worker credentials on the pool's own dashboard Expected: worker name present, account active, no abuse flag If worker is disabled / wallet rotated: update config, re-authorize
Check miner clock against NTP time Expected: miner clock within 60s of current UTC If clock is 1970-01-01 or badly skewed: force NTP sync, replace RTC battery if needed
Factory reset, then re-provision via WhatsminerTool from a clean config Expected: fresh config, single known-good pool URL, cold boot clears 2010 If 2010 persists after clean reset + known-good config: firmware or nvram fault (Tier 3)
Escalate. Firmware reflash → last resort before the bench ```
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.