Topic: [Mining OS] SimpleMining.net - Manage Your GPU farm the easy way! (30 days free) - page 434. (Read 835818 times)

Hey, I'm mining ETH on nanopool stable for a few days now and just now I noticed strange thing - my rig console was showing me something like



It lasted for 20 minutes until I realised something wrong is going on.
I simply pressed "r" to reload pool and it started to mine as nothing happened.

Do you know what could be the reason and how to prevent that in future? As I said, it was doing nothing for 20 minutes so I don't know if it would soon go back to life or autoreboot the rig...

config claymore-eth-v9.4:
-wd 1 -r 1 -epool eu1.nanopool.org:9999 -ewal $walletETH -epsw x -eworker rig1
 
MSI Gaming Pro CARBON
7xASUS DUAL RX580

ya but whats the problem on that? just get a new version and put it in /root/miner/ ... after that it should work when u chose the overwritten miner in the online interface

on the other hand: shouldnt be a big problem for tytus to load the new miners and send an update ... but focus is on nvidea now

That's what I was saying. You've got to load the full complied version or the old binary won't recognize the newer kernel.

why not loading the complete miner and put it in the sgminer folder of SMOS instead of just loading a component which the miner doenst know cause of wrong version?

Regarding sgminer-gm, I originally tried just adding ethhash-new.cl to the kernel folder but it's not recognized unless you have a re-compiled version of the main binary.

This is what my working sgminer-gm shows as the version: sgminer 5.5.5-gm-a

have you tried to set fanspeed on your own manually via shell? dunno how claymore controls that but the command should also work from the shell

its insane that people cry about 2 dollar fee.
I love your OS- made my life much easy! and Sir keep the goood  job and we love your OS! and thank you again.

any news on adding ethash-new.cl ?

isn't it as straightforward as just simply uploading ethash-new.cl into the sgminer-gm v5.5.5 appropriate kernel directory - if yes, you can already test ETH mining without Claymore.

Do you know how much the fees are? Can't find it on their site. Thanks anwyays!

Also is there any good config to overclock my RX 480 8G GPU on your OS?

I am trying to set the gpu fan to a fixed speed but with "-tt 70 -fanmin 80" but I get an error "Failed to set new fan speed, check if miner has root access!".
Has this already been discussed? I could not find an advise to fix this.

afaik  ethdcrminer64 process runs under the user "miner" which has sudo root rights:

# Allow members of group sudo to execute any command
%sudo   ALL=(ALL:ALL) ALL
miner         ALL = (ALL) NOPASSWD: ALL

Is this not enough?

It's across two different locations. I'm moving things over to the new version of claymore as a test. If that's not it, I'll try a different pool.

mhh that sounds like the pool is crashing you probably ... are you solo mining or using a pool? if solomining check your wallet for a new version or a restart ... maybe there is something wrong

only way how could be affected all your systems in my eyes ... mhhh ... except of there is a problem in your powersupply at the wall ... thunderstorms or something like? maybe check the main fuse?

Looks like Claymore has jumped to v9.5 in the last day or two. I'm going to roll that out and see if helps.

Thanks Tytanik. I'm purposefully not automatically rebooting because it masks issues with the systems or would take a whole machine down when only one card was acting up.

Just to be clear, it's been all of my rigs across multiple levels of overclock. 16 systems in total. These are rigs that have been very stable in the past but have all decided to flip out at the same time. The symptom is that all cards in the system throw GPU errors all at once. I was just wondering if anyone else started to see the same issues or had noticed an uptick in reboots due to automatic reboots.

Outside of Simpleming OS systems, I've also had a Windows system and a raw ubuntu system with Nvidia cards also drop off. I'm really starting to think its an issue with Claymore. It's just odd that it started so long after his last release. Maybe its an issue with the latest DAG file.

On a side note, I think it's super critical to get a new version of sgminer-gm loaded that includes the ethhash-new.cl kernel. That way, we have a fallback from Claymore if folks are having issues with it or just want to avoid the stability issues that are associated with his dev fee process. Last time that I checked, v1095, that new Kernel wasn't included. PM me if you want a copy of the version I've complied and put on my systems.

for any reason your gpus have any problem ... try tytus' way to autoreboot (-w 1 -r 1) ... probably lower the core speed for testing proposes.

Use
-wd 1 -r 1
in claymore command line
it will reboot automatically your rig.

The system is what it is. Its online service only. No offline version. And thats it. the end.
I am not making custom versions or sharing my personally written code with anybody.

Right now i will froun rocket chat (someone told me about it before) and it suits my needs.
I will introduce it soon.

Anyone else having watchdog issues where the systems drop to 0 hashes and need to be rebooted? Or having issues with rigs rebooting a bunch.

I purposefully left the auto reboot setting off Claymore to highlight rigs with hanging card issues and had my systems pretty stable. Starting about 5AM this morning, I've been having issues with machines at two different locations where the watchdog timers show all GPUs with OpenCL errors. Sometimes a simple reboot takes care of things. Other times the systems require a hard power cycle.

So far, I've rebooted every one of my systems(16 in total) at least once with several needing to be rebooted multiple times. These are systems that have been very stable for days and in some cases, weeks. Continuing to troubleshoot here but wondering if anyone else is seeing similar things happening.

ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s, GPU6 0.000 Mh/s
GPU0 t=42C fan=47%, GPU1 t=41C fan=47%, GPU2 t=45C fan=47%, GPU3 t=38C fan=47%, GPU4 t=43C fan=47%, GPU5 t=42C fan=47%, GPU6 t=4
0C fan=47%
WATCHDOG: GPU 0 hangs in OpenCL call, you need to restart miner
WATCHDOG: GPU 0 hangs in OpenCL call, you need to restart miner
WATCHDOG: GPU 1 hangs in OpenCL call, you need to restart miner
WATCHDOG: GPU 1 hangs in OpenCL call, you need to restart miner
WATCHDOG: GPU 2 hangs in OpenCL call, you need to restart miner
WATCHDOG: GPU 2 hangs in OpenCL call, you need to restart miner
WATCHDOG: GPU 3 hangs in OpenCL call, you need to restart miner
WATCHDOG: GPU 3 hangs in OpenCL call, you need to restart miner
WATCHDOG: GPU 4 hangs in OpenCL call, you need to restart miner
WATCHDOG: GPU 4 hangs in OpenCL call, you need to restart miner
WATCHDOG: GPU 5 hangs in OpenCL call, you need to restart miner
WATCHDOG: GPU 5 hangs in OpenCL call, you need to restart miner
WATCHDOG: GPU 6 hangs in OpenCL call, you need to restart miner
WATCHDOG: GPU 6 hangs in OpenCL call, you need to restart miner

read it 3 times and still dont got the point what ur talking about xD

The first time that I ran into this type of amazement was when the first power ASIC's hit the streets.  Keep in mind that most of the members on this forum won't trust downloading an image file because of the deep level of paranoia.  So, here were the first ASIC's, their own custom coded Linux based systems that you were supposed to configure and leave on your network without giving them a second thought.  They became a huge hit very fast, as you know.