Kernel Log
The kernel log is the miner's diary: startup, chip detection, temperatures, errors. Half of all diagnoses come from the log without touching a screwdriver.
What the log records and how to read it
The log opens in the ASIC's web interface and starts with the boot: loading, versions, detection of hashboards and chips chain by chain. Lines like chain 1: find 76 asic are the chip roll call, and a short count there names the sick board right away.
Then comes the working rhythm: connecting to the pool, accepted jobs, temperatures and fan speeds, submitted shares. Against that background the events stand out: restarts, lost sensors, fan errors, dropped pool connections.
The main habit: save the log before rebooting. A restart wipes the journal, and the picture of the failure disappears with it. The miner acted strange: first a copy of the log to a file, then any actions.
The log travels to the repair shop with the ASIC or ahead of it. The error lines and the chip roll call tell a diagnostician more than any verbal description of symptoms, and often let them name the repair price before opening the case.
The short version in a table
| Where to open it | in the ASIC's web interface |
| The key lines | chip roll call, temperatures, errors |
| The main habit | save the log before rebooting |
| What wipes the journal | restarting the miner |
| For the repair shop | the log beats any description in words |
What to look for in typical troubles
Hashrate dropped: check the chip roll call chain by chain and compare with the rated count. A short chain names the board.
The miner keeps stalling: look at the last lines before the stop, usually a temperature, a sensor or a fan.
A worker vanishes from the pool: lines about reconnects and timeouts show whether the link breaks on the ASIC's side.
The miner reboots on its own: look for the restart cause at the end of the previous session, which is exactly why you save the log in advance.
A reading example
An ASIC holds two thirds of its hashrate. The log says chain 2: find 50 asic against the expected 76: a third of the chips on the second board are silent. Temperatures on the other boards are even, the fans are fine. The diagnosis takes two minutes of reading: board number two goes in for repair, the miner keeps working on the rest.
Related terms
Where to go next on the site
Software
- Software firmware
- HashCore Toolkit firmware
Hardware
- ASIC Miner knowledge base
Questions and answers
The log is too long, where do I start
From the end and from the chip roll call: the latest events and the find asic lines answer most questions.
The miner rebooted, the log is empty, now what
Wait for a repeat and grab the log right after the failure. The habit of copying the journal before a reboot saves exactly these waiting cycles.
Do I need to read logs if I have monitoring
Monitoring says something is wrong, the log says what exactly. Different levels: the first one wakes you up, the second one gives the diagnosis.
How the terms connect
Every link in the chain is clickable. Orange marks where you are now.
Looking for an ASIC miner
The catalog holds 212 models. You can compare them by hashrate and by joules per terahash, then plug your own rate into the calculator and see what stays in your pocket.
Page written and checked by Denys Klimchuk. Updated .