The easiest way to do this would be to take a copy of oneBash; rename it, remove everything but the OC settings and implementation. Then you can run that renamed bashfile whenever to change clocks.

Actually xmr-stak-cpu is a great idea! It's super stable - I actually added it to one image of nvOS where I'm also cpu mining a while ago and it plays really nice with everything else on the distro. While at it I would suggest adding xmr-stak-nvidia I meant to test it when I had some cycles to spare, but since xmr-stak-cpu is on the radar, maybe we can also add it's nvidia cousin?

I integrated a slightly modified IAmNotAJeep_and_Maxximus007_WATCHDOG, fixed the typo in Maxximus007_AUTO_TEMPERATURE_CONTROL.

saflter your newest version of switch was causing problems when run with a monitor connected (LOCAL); I would recommend relying on the:

IAmNotAJeep_and_Maxximus007_WATCHDOG

to handle miner crashes / 0 hashrates.

I spent a couple hours testing this, and it is very effective; it is worth noting that it currently only works when the mining process is launched in a screen ( I will make it work for all the clients even when run locally soon: so don't spend a lot of time upgrading rigs with this)

Also even if your crashes are perfectly handled; if your OC is so high it crashes every 7 minutes or less: you are losing more time restarting the mining process then you are gaining with a slightly higher hashrate.

Use reasonable OC.

Please provide me with:

# IAmNotAJeep BTC address: <not yet provided>

# Maxximus007 BTC address: <not yet provided>

# _Parallax_ BTC address: <not yet provided>

It's great to see everyone get involved and speaking for myself, to feel like it's OK to contribute once in a while as well.Hats off to fullzero, Maxximus007 and _Parallax_!

without a doubt my biggest problem right now is that when my miner crashes it takes the whole rig down with it, everything gets stuck, SSH barely works, average system load jumps to 14.5!! and Xorg takes up 100% of the CPU, its so bad that none of the standard reboot commands work, they just do nothing, the only thing that actually reboots the rig in this state is "echo b > /proc/sysrq-trigger" so i've set up a script that checks the average system load and if its over 2 it uses the command to reboot, and it works, but i dont like this "solution", yesterday after a reboot nvOC got corrupted somehow, lost my customized oneBash and the whole system became read-only (thankfully i had a oneBash backup that was only a few days behind).

so the question is, what can i do to relive this Xorg error, i run a 7 card rig and never plan on going for a higher number, what can i do with Xorg that would fix this?

Thanks.

@ tempgoga

It seems that whenever a soft crash occurs most of the cards drop to zero, so while the display/keyboard is unresponsive you can catch the soft crash from nvidia-smi. The script below checks card utilization, if it drops below 90% it counts down a minute and if mining hasn't resumed it reboots the system.This seems to have worked at least once in my case (only got one soft crash this weekend) and the system recovered as expected.the threshold values work for my setup but others may find different values optimal

Also if anyone knows a way to iterate the if && statements we can get the card count from "cards=$(nvidia-smi -L | wc -l); echo $cards" but the way below also works with manual editing to adjust the watchdog for the number of cards in you individual system.___________

@ Maxximus007Thanks for putting these together, great collab! I'm not a bash expert, so maybe I'm reading this wrong, but here are some thoughts.The combined code seems to be evaluating each gpu individually for the fault condition to be met, which means if one fails and you have say 5 other cards working then it keeps going until all the cards give reduced output since all of them have to fail individually to increment the counter?So if 5/6 fail we keep going? (Again just looking at it and tracing it in my head so maybe I'm reading wrong).The way I was thinking about it, is that I wanted all the cards to work at above 90% efficiency and reboot as soon as any card strays beyond the threshold - this is why I did the "if and" statement and didn't iterate though "if" statements alone (I didn't know how to iterate "if and" based on an unknown number of cards lol). I had a version giving 6xOK and such but I think it's more efficient to just get 1xOK if ALL meet the 90% criteria and start the countdown as soon as anything is out of norm - and if the miner recovers, flush the counter. I observed a number of these conditions with Claymore where it recovers half the time, but then eventually craps out and the script kicks in. I haven't seen it on my Genoil rig yet since my other script has kept it in check without any softcrash for day 3 now.

A thought about the power draw as threshold measure - it is power limit/card specific and I guess people would need to tune their power threshold to their power limit so I agree it's best to use gpu util. (My cards are at 82W limit for example).Thoughts?

The code checks each cards individually, at times (with Claymore, not Genoil) I've seen that Util (or Powerpraw) is dropping, maybe even below 90 for a few seconds. In order not to generate too much restarts I check all cards. We can lower this or make it so that each of us can decide when it should reboot.I've combined the restart/reboot so that the first attempt is to restart miner. If that doesn't work, we reboot the machine. We might want to reset the reboot counter after a while, so we don't loose time with a full reboot.

In the first code I checked Powerdraw -> if 30 Watt less than Powerlimit there might be something wrong. Idling cards use around 10 Watt, so that works for all I think. We can combine this with Util if that helps.

So sure we can make it more advanced, we just have to determine the right parameters. Hope others can let us know in what circumstances they see hanging miners. Just one card, or more or everything? Is Util back to zero? or hanging on to 100%?

OK thanks for the clarification, it's really neat and rewarding to see different approaches to this problem Here is why I coded to test that all the cards meet the threshold as one with "if &&": as an example I'll use an event from from my test rig overnight: one card dropped, the "if &&" script waited for claymore to recover for one minute, then booted the system and that was that.Total down time, 2 mins, if you add the 1 minute of reduced capacity waiting for the miner to right itself, 3 minutes impact.

The "if &&" code does tests for a graceful miner recovery - by continuing to test the cards for above threshold utilization for 60 seconds after it detects a fault.If the miner recovers, but just sits there (saw both Claymore/Genoil do exactly that a number of times) that's not good enough and the system gets a boot.My other miner restart script did not handle this exact case and once every few days I would find the miner sitting pretty and blowing bubbles mining on one or two cards until I noticed because it did not "see" all the cards anymore but it did see some so it thought it "recovered".

If the miner recovers properly, all cards need to hit above threshold and we can flush the counter and life goes on. On my test rig, graceful miner recovery occurred 5-6 times in the past 24 hours without prompting a restart - which is desirable above either running at reduced capacity or 5-6 reboots (IMHO).

In contrast - if we test each card independently and increment the error counter one by one until it reaches the number of GPU's, then - depending on the number of cards in the system it could take a long time for all of them to fail - the more cards, the more time to fail (right? am I misunderstanding anything?) So the same event, would unfold differently: the test rig would continue at reduced capacity until COUNT reaches # of GPU's - but since it resets at next check, we can hobble on 5,4,3,2, 1 card until they all die or and the script kicks in or we freeze and require a manual intervention. This could be hours of impact (again if I'm reading this wrong, my apologies, but this is what I'm getting out of looking at it.)

So IMHO, by testing that all the cards meet the 90% utilization threshold (as one, all or nothing = if &&), we avoid hours of impact/decreased capacity. My other concern is that as soon as cards start dropping off one at a time the system gets unstable, increasing the risk of a hang or corrupted file system due to a hard crash.My view is that it should be cycled at maximum stability for a graceful restart.

Maybe there is a third approach not considered yet, Thoughts?

... edit:Actually one more thought - I did not test for this yet so I don't know the answer - but in the case where the miner does not see all the cards anymore, does this mean that nvidia-smi ALSO does not see all the cards anymore? If so, and if we get the number of cards from nvidia-smi, wouldn't the script assume that the rig has the right number of cards every time that nvidia-smi stop seeing one? I do recall cards disappearing even from nvidia-smi but I never kept track of this so I don't know how often this condition actually occurs.

Thanks for explaining, and you do have valid points here. Like your thinking. I will rework it with this in mind.

Just wondering: Your script reboots the rig, if the miner itself does not recover. Instead we could introduce reloading miner as the first step here. In my experience that resolves the issue almost every time. It will only save 1-2 minutes so it's not a big deal to just reboot (still had the boot time of V0014 in mind).

I did not experience that nvidia-smi looses a card while it's there, but I can imagine that happens with faulty risers. Perhaps we can run the card number count nvidia-smi only at startup the number of cards (saves a call as well) and keep that number during the watchdog process. If we loose a card we do have to reboot anyway.

One other thought: Perhaps it would be an idea to echo the output of the log to a screen (tail -f) so the former reboots are shown as well?

Hi, if it's a Genoil rig I run this setup: https://bitcointalk.org/index.php?topic=1854250.msg19943144#msg19943144 plus the watchdog script being discussed here in separate "screen -dmS" sessions so I have the watchdog and restart scripts running separately.for that setup I also tail the "ltail" script but if we run only one script then it would make sense to echo some diagnostic output of what faults and recoveries it detects (or log it - but then we need to think about logrotate or someone will run out of space in a few months lol).For the Claymore setup I only run the watchdog since Claymore has it's own fault detection and it restarts by itself so if the built in restart doesn't work, I cycle the box and log the reboot condition only so I don't have to logrotate.

I think it would be best to make the watchdog have a triple nested loop; first checking and doing the work of IAmNotAJeep's original scripts, then killing the screen and oneBash process if needed, then rebooting if needed.

Please try the new oneBash with the modified version of your watchdog; and let me know if it is working correctly / suggested changes / if you think the triple loop is a good idea.

Having some issues with the v0017 setup..for some reason the worker isn't showing up in my pool. just using nanopool for the time being. its only showing my one rig. made sure the wallet is right and all that and they have very different worker names..any thoughts? the other version im using is v0015

Having some issues with the v0017 setup..for some reason the worker isn't showing up in my pool. just using nanopool for the time being. its only showing my one rig. made sure the wallet is right and all that and they have very different worker names..any thoughts? the other version im using is v0015

What pool are you using, and what are your pool / worker / address settings?

The easiest way to do this would be to take a copy of oneBash; rename it, remove everything but the OC settings and implementation. Then you can run that renamed bashfile whenever to change clocks.

Actually xmr-stak-cpu is a great idea! It's super stable - I actually added it to one image of nvOS where I'm also cpu mining a while ago and it plays really nice with everything else on the distro. While at it I would suggest adding xmr-stak-nvidia I meant to test it when I had some cycles to spare, but since xmr-stak-cpu is on the radar, maybe we can also add it's nvidia cousin?

I integrated a slightly modified IAmNotAJeep_and_Maxximus007_WATCHDOG, fixed the typo in Maxximus007_AUTO_TEMPERATURE_CONTROL.

saflter your newest version of switch was causing problems when run with a monitor connected (LOCAL); I would recommend relying on the:

IAmNotAJeep_and_Maxximus007_WATCHDOG

to handle miner crashes / 0 hashrates.

I spent a couple hours testing this, and it is very effective; it is worth noting that it currently only works when the mining process is launched in a screen ( I will make it work for all the clients even when run locally soon: so don't spend a lot of time upgrading rigs with this)

Also even if your crashes are perfectly handled; if your OC is so high it crashes every 7 minutes or less: you are losing more time restarting the mining process then you are gaining with a slightly higher hashrate.

Use reasonable OC.

Please provide me with:

# IAmNotAJeep BTC address: <not yet provided>

# Maxximus007 BTC address: <not yet provided>

# _Parallax_ BTC address: <not yet provided>

It's great to see everyone get involved and speaking for myself, to feel like it's OK to contribute once in a while as well.Hats off to fullzero, Maxximus007 and _Parallax_!

I tried mining zec on slushpool, nice site, getting the workers to populate correctly with nvOC was frustrating, and the returns are not as high or consistent than other pools. However I did earn .33 zec when I normally earn .18 zec on their pool with 6.5k sols

What pools are you all using to mine ZEC currently

i was on nanopool but my payouts were lower than estimated by calculators. I've been on flypool for 9 days straight now, and it's been spot on.

I understood that you meant to add oneBash only for github. Look at the number of changes in this oneBash alone; and then consider how much more there would be to look at with input from even a few members. Until most of the features members want have a basic implementation; this is essentially only going to give me another thing I need to pay attention to.

Git suggestion was only to simplify the implementation of all changes and make easier to track what's changed.Using the script as a learning example is the point, but I also think that using bash loops is a better example than copy/paste style.Finally, oneBash is good, but I would split it into separate parts like overclocking, miner selection, watchdog, monero mining, etc to make easier to tune/restart some parts.

In any case, I really appreciate your efforts. I did not use nvidia GPU till now, and your distro was the best way to start using nvidia with Linux. Thank you for working on it and sharing.

fullzero - I just got the new TB250 12 x PCI slot mobo, testing 12 x Zotac Minis 1070s and Zotac 12 x 1060 Mining cards.I see the new bash file now goes up to 15 cards so it should run.Will post results and pix in a few days. Thanks

If I provided you good and useful info or just bring a smile to your day, consider sending me merit points to further validate this Bitcointalk account ~ useful for future account recovery...

I just want to say thank you. I've been using this for almost a month now with nearly zero issues. For some reason, the 378 drivers gave me terrible performance with 8 1060's. I rolled back to 375 and it's been running like a dream at 22+ per card on eth genoil. One quick question, are the default bitcoin and eth addresses your own valid ones? I'd like to mine for a day or two using your addresses as a thank you.

I've added my BTC address, if I run the oneBash with 'NICE_ETHASH' coin selection, which coin does it mines? (I know you said there is no coin selection/algos currently, just curious to know what it selects and mine) No matter what it mines, will it just coverts into BTC and pay to my BTC address?

I've tried it using my BTC address for a while, it has started mining but not sure what it was mining (it was using Genoil)!, but saw ETH share accepted message most of the times ("stratum+tcp://daggerhashimoto.usa.nicehash.com:3353")

Also where can I check how many shares per our stats related to my BTC address or Miner while mining with 'NICE_ETHASH'

Note that with supernova you need to set the workername beforehand, so I recommend changing the workername to whatever you have set already rather than making a new worker with the auto generated workername.

================================================================================Now it all make sense, lots of questions got answered from your replies. I really appreciate you for the time and effort.

& for the first question

Code:

SALFTER_NICEHASH_PROFIT_SWITCHING="YES"

# LOCAL will attach the mining process to the guake terminal# REMOTE will leave it unattached / ready for SSH LOCALorREMOTE="LOCAL" # LOCAL or REMOTE

CURRENCY=USDPOWER_COST=0.20MINIMUM_PROFIT=0# this is salfters BTC address:PAYMENT_ADDRESS=1QJ6j3fY6fCRsN1WJqZ65U52Et4TVL9e7PWORKER_NAME=$IP_AS_WORKER

m1@m1-desktop:~$ screen -r minerThere is no screen to be resumed matching miner.m1@m1-desktop:~$ screen -r minerThere is no screen to be resumed matching miner.m1@m1-desktop:~$

* Do i need to connect(turn on) monitor to do so? (I do have monitor connected to Main GPU, but always remove power once RIG is UP and Running)* What coin I need to select on top while having SALFTER_NICEHASH_PROFIT_SWITCHING="YES"? (NICE_ETHASH??)

I am guessing you haven't added the:

switch

file to the home directory.

If I am correct; and you download the newest oneBash and files and add them as the folder instructs this should work.

Yes, that is the problem, I have ran it later after copying the files, can see it working but crashed whole OS, I might need to use the latest files and give it a try again (now I'm sure it works with the latest fixes).

Also I'm seeing low hashrates sometimes while using 'NICE_ETHASH', dropping to 100 MH and going to 250 MH (saw that on nicehash portal, but on terminal it averages 185 MH always)

My OC settings cc-150 mc-1200 pl-95W (8 GTX 1060 6G on Z270P), does it have something to do with my OC settings? any idea?

#On one of the longest running rigs I got a message that I'm low on space . Around 600mb . I have a SSD on that RIG . Can the logs generated be that big ?

Claymore's logs are huge.

Quote

#Where can I find the claymore logs ? I can't see it in the 9.5 folder like on win

AFAIR, they are disabled with '-dbg -1' option. Change this if you need logs.

Quote

#In genoil ... how can I see the uptime of the rig ?

Rig or miner? Have no experience with genoil, but 'uptime' shell command can give you the rig uptime.

Thanks!Strange message for size issue . It was running for 200hours or so .

Wanted to ask about the uptime of the miner sorry .Want to know if it crashes and reboots...no idea if genoil can do that as I haven't used it until now but for 1060 I get about 11 more MH - 176 with less overclock then in Claymore where I get around 164-165 with more OC but both rigs that I used genoil on ... reported 0 hashrates (I could only see " - " in the section for that miner but it had average hasrate displayed ) but the miner looked to be running and I had the right address in place. If I changed to Claymore everything its fine.

Great job guys ... its developing very fast into something complex but easy to use for the average user . Not sure if its good or not if everybody mines ... but for me ... more people in crypto is + EV in the long run