Closed teckel12 closed 6 years ago
With what M parameter are you running equihash? Default one? You can read the mode from the cmd window.
Also, excavator logs would be a big help. Run excavator with -f 0 flag to enable file logging.
@dropky M=1
Excavator is running via Nicehash, so I'm not sure how to run it with a flag. That's why I came here to begin with, to find out how to send parameters to Excavator and if there was a parameter for minimum hash rate (like with Claymore miners).
Thanks again.
To pass -f 0 flag to excavator while using NiceHash Miner you'll have to edit General.json file located in C:\Users\user_name\AppData\Roaming\nhm2\configs\General.json
. Set ExcavatorExtraStartupParameters to -f 0 ("ExcavatorExtraStartupParameters": "-f 0"
). Restart NiceHash Miner. You'll find excavator's logs in C:\Users\user_name\AppData\Roaming\nhm2\bin\excavator_server\archived_logs
directory or in one directory above (if you haven't close the excavator yet).
FYI: Make sure you disable the -f 0 flag after, otherwise it could fill up all your disk space.
Done and running. When it started I noticed the -f 0
in the startup command line. The archived_logs
folder was created, but at this time there's no log files contained within.
I'll keep an eye on it and when it fails I'll post the log file here.
That's completely normal. You should notice the log file in the same directory where excavator.exe is located. When it get's big enough, it will automatically be moved into archived_logs directory and a new log file will be created. The active log file is always located in the same dir where excavator is, old log files are moved to archived_logs.
@dropky Here's my log file from a failure:
A little background: I cycled power before restarting just in case it was something like that. I've also been running on this box for a couple months without any issues till the last few days. I can't say that it was linked to any kind of update or anything else. This box isn't used for anything else, it's just an extra PC I had laying around. Finally, I changed my NiceHash hash in the log file as I wasn't sure if that was private or not.
Let me know what you see and thanks again.
I went over the log file and the reason for equihash speed dropping to zero is because miner.stop method is called. Please check if you enabled the minimum income option in NiceHash Miner, under configuration? If you have then probably the profitability is lower than the one provided with minimum income and consequently the miner has stopped mining.
Let me know if that's the case.
@dropky That's odd because it was still mining CryptoNightV7. And NiceHash wasn't saying that it wasn't mining due to being below the minimum income level. Also, when I would restart, it was over the minimum and would run for a few hours before stopping again.
I changed the minimum to 0 and it hasn't stopped since. But, it seems there's some kind of problem with the minimum code. Is the minimum for each miner or each device or total? As there's only one minimum, I assumed it was for all combined.
Minimum income is for all devices combined. Your problem might be related to the recent problems that we had with exchange rates and profit calculations. Anyway.. I'm closing this issue since it works now.
Sounds good.
Running v1.5.4a on a 750 Ti mining Equihash. Sometimes, the hash rate goes to zero and stays there. This doesn't trigger a warning and doesn't restart. It just stays at zero till I notice. I restart mining and it all works again, until the next time.
Two things. First, something must be wrong for it to go to a zero hash rate. Secondly, if the hash rate is zero for a certain amount of time, it would probably be a good idea to restart automatically.
Thanks!