The low hash rate usually manifests in two forms, that is, the miner’s local hash rate is less than the miner’s theoretical hash rate, or the mining pool’s hash rate is less than the miner’s local hash rate. Users can use the following troubleshooting to locate and solve the problem accurately.
1. The local hash rate of the miner is less than the theoretical hash rate
The miner’s local hash rate is less than the theoretical hash rate is mainly caused by some influencing factors of the miner’s hardware or the mining farm. You can refer to the following several common possibilities and solutions.
1) The miner has not warmed up, and the hash rate is insufficient when the miner is turned on.
Solution: It takes about 15 minutes for the miner to restart before the hash rate reaches the normal range; if the miner restarts automatically within a few minutes, please change the power supply test to confirm whether the abnormal power supply causes the restart.
2) Incomplete display of miner hash board.
Solution: If the number of hash boards displayed in the backstage of the miner is less than the number of the hash boards of the miner, re-plug the data cable at both ends of the hash board (or update the damaged data cable), and restart the operation.
3) The hash board has no hash rate and abnormal temperature sensor data.
The miner checks the hash board online backstage. Still, the hash rate is 0, or the number of chips is displayed as 0, or the temperature is abnormal (the temperature is different from other hash boards). At this time, please unplug and reconnect the data cables at both ends of the hash board and power on again.
4) Network delay, low uplink and downlink bandwidth, or severe packet drop.
This situation mainly manifests as a high rejection rate in the mining pool.
2. The hash rate of the mining pool is less than the local hash rate of the miner
It is recommended to refer to the following more common possibilities and solutions.
1) Mining software collects a handling fee, and currently commonly used mining software on the market charges a handling fee of about 1%-5%.
The charging model of mining software is as follows: miners have 36 seconds—72 seconds (3600 seconds X 1%—3600 seconds X 5%) per hour to mining the wallet address of the mining software developer. During this period, the miner's hash rate was not submitted to the miner's wallet address but the wallet address of the mining software developer. This is equivalent to between 1 hour and 24 hours, miners only spend 95%—99% of the time mining for miners, and the hash rate indicators of the mining pool are the average hash rate of 1 hour and the average hash rate of 24 hours, so the 1 hour and 24 hour average hash rate will therefore be 1%-5% less than the local hash rate. It can also be seen from this that mining software pumping has nothing to do with mining pools, and mining pools cannot control the pumping behavior of mining software.
Be careful not to use malicious mining software; they charge far more than 1%-5% and may even carry the virus.
2) Network transmission loss is 1%-3%.
The network transmission is lossy if the net loss is about 1%-3%. However, if there is a problem with the miner network (rejection rate and delay rate soaring), the loss will far exceed 3%.
3) Calculate the task switching loss of 0.5%-1%.
The mining pool server continuously pushes the latest calculation tasks to the miners, and the miners switch from the previous calculation task to the following calculation task, and there will be a 0.5%-1% hash rate loss. This is inevitable.
4) Severe overclocking.
If the miners overclocking is severe, the calculated result is invalid, and the mining pool will not accept such a calculation result. When the difference between your local hash rate and the hash rate displayed by the mining pool exceeds 8%, please check your miners and the internet.
The content of this article is from the Internet, compiled and edited by ZEUS MINING.