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

If still problem after settings per phil's post below, try -lidag
Assuming your GPU has more than 2GB mem

if claymore 8   -ethi 4   should fix it

-ethi 8 is stock

you can try 7 then 6 if it crashes then 5 then 4

you will lose a little hash with 4,5,6,7  settings



my eth  for my pandaminer which has the exact issue as you  due to weak cpu

-epool stratum+tcp://us1.ethpool.org:3333 -ewal 0x3ef297e47404a771139472b93621f82c8a832857.Simple2 -esm 0 -epsw x -allpools 1 -mport -3333 -ethi 4


pandaminer on 4



i get 228mh  no crash
on 7 i get 230 mh crash
pn 8 the stock setting I get 231 same crash as you

Nope, i will start thinking about that not sooner than in 4 months.

2 GB memory in gpus ?

Setting DAG epoch #109 for GPU #1
Create GPU buffer for GPU #1
OpenCL error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
Setting DAG epoch #109 for GPU #0
Create GPU buffer for GPU #0
OpenCL error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
Setting DAG epoch #109 for GPU #2
Create GPU buffer for GPU #2
OpenCL error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
ETH: 03/05/17-08:32:13 - New job from pool.bitclouder.co:3333
ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
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
Setting DAG epoch #109 for GPU #4
GPU 4, OpenCL error -38 - cannot write buffer for DAG
Setting DAG epoch #109 for GPU #3
GPU 3, OpenCL error -38 - cannot write buffer for DAG
Setting DAG epoch #109 for GPU #0
GPU 0, OpenCL error -38 - cannot write buffer for DAG
Setting DAG epoch #109 for GPU #1
GPU 1, OpenCL error -38 - cannot write buffer for DAG
Setting DAG epoch #109 for GPU #2
GPU 2, OpenCL error -38 - cannot write buffer for DAG
GPU0 t=17C fan=67%, GPU1 t=18C fan=67%, GPU2 t=18C fan=67%, GPU3 t=30C fan=67%, GPU4 t=20C fan=67%
WATCHDOG: GPU error, you need to restart miner
Binary file (standard input) matches
Close

Hey tytanick, do you plan to support nvidia gpu's anytime soon?

Update v1073
- claymore-zec v12.2 fix memory leak
note. it will start using this after reload

oops my bad on the usr vs user syntax

great mining!

T,

URGENT - Can help recompile Claymore ZEC Miner v12.2. Thanks

v12.2 had a memory leak issue and Claymore fixed it and asked everyone to redownload v12.2.

===
Re: Claymore's ZCash AMD GPU Miner v12.2 (Windows/Linux)
Today at 01:35:02 PM
...

Windows Miner v12.2 has a memory leak 700mb per day, 5gb per week.

yes, this is true. Claymore can you fix this?

Confirmed, fixed. I can re-upload v12.2 or I can include this fix in next update which will be available in a few days.

 12.21 then do the update next week as 12.3

Also please allow -i 8 again on nanos. No reason to disable it!

Memory leak: just redownload v12.2, see note in OP.
-i 8: done, you can use it already.

Claymore - this revised 12.2 is only applicable for Windows version correct ? -- Linux version no impact??

Linux is affected too.
===

Thank you very much for all that information. We learned the hard way to manage rigs with ethOS with SSH connections. We successfully connected to our rigs with that infos.

I just would like to point out that it didnt work for us at first.

nano /mnt/usr/config.txt didnt work, it would open an empty config.txt, but this one worked: nano /mnt/user/config.txt  ==== https://www.dropbox.com/s/y1rnxxc6mp1jwx8/Capture4.PNG?dl=0

We had to look around in the drive to discover that! Our rig is now mining under our wallet address. Maybe it would be a good idea to add these troubleshooting steps in case this happens to someone else.

Cheers!

Cpu mining will be only as an option to mine as fee for me.
There wont be mining for cpus as there is no sense of doing that.

Tytus, any plans on using the CPUs in the rigs as an option for mining? Hard thing to code or easy to do?
Since at most times it makes no sense to mine the same coin / algo as your GPUs.. maybe with a seperate group in the GUI?

I use WINSCP (also from putty suite) in Windows
then go to /mnt/user/
Edit the config.txt
change email (I also add in the first comment R9 or  Rx so i can know what kind of release im editing, and rig identificator for my location)
and just wait like 10 sec, then the rig automagically changes from one panel to the other.
Of course the rig keep doing the same stuff until you reset miner or reboot rig.

I use this way when are trying new configs, so i can move just 1 rig to that email panel and do the tests without affecting the rest, and work flawlessly.

You need to login to the panel of the new email and set the OPTIONS : wallets miner selection.
Just like you did with your first rig, because is a new account.

If above answer wont help, please write to me at [email protected]
I need to check it.
Also you are saying that few rigs are already working and mining to your wallet but only some are not ?
I can see whats going on remotly, just need access to windows tema viewer that is on the same network as those rigs and i need rigs ip.
Write email , not here ofcourse

can you SSH into the rig's IP address?

if yes, logon as miner, password miner

at linux prompt, type :

nano /mnt/usr/config.txt

see if your email is there, if not change it to your own.

save file using control-x, confirm file name and press return

lastly type:

sudo reboot



Afternotes:
btw, your need to change this email address BEFORE you boot it up with your rig.
If you boot up and see it running with Tytanick's email -- that means you email was not saved correctly.
So the simplest way to fix this is do to the SSH way, i describe above.
I use this method all the time to move certain rigs.
I assume you know what is SSH, if not google "puTTY" a simple Windows SSH client to log into Linux systems.
nano is popular file editor in Ubuntu -- smOS has this nice editor already so its handy.

Hey,

We are currently encountering a problem with the initial setup with our rigs. We can see the config.txt file and we did change the email inside and save.

After that we put it on the rig, it starts mining on your wallet like you said, but it's staying there forever after.

We spent hours to reformat, tried different ways, we always edit the config.txt with our email address and it's still mining to your address. Normally, we can see the added rig after few minutes, but it's also not showing up in the interface at all.

What else should we do?

Thanks

its too complicated for me to do undervolting tool
I would need low level programmer or perhaps i can buy this tool from someone but i suppose it will  cost too much if even possible to buy.
If there would be public tool i would implement it for sure but there is not

About auto updates.
Auto updated cant be stopped, i need them to mantain consisten system.
If i will implement new feature and update server but your rigs wont update then reading stats or chaning settings wont work.
I can minimalize this in future and make betatest updates like with the kernel one.
Anyway i cant do this right now, it would create too much work for me.
But be sure that if i want release production update then i am testing it first on my development rig.
So right now i wont stop auto-updates but in future i will try to figure something out.
Anyway thing i wont do:
- reload or reboot someones rig without permision.
- so i wont reload miner if new miner version comes out - you need to do it yourself and check if new miner version doesnt cause any problems

The system with non-auto updates is ethOS.
My idea is to make all rigs consistent and up to date.
I am nod bad guy and i wont make your rigs zombiee or mining for me - that you can be certain.

sounds decent. my rig has only a G1840, most rigs probably have something similar.

i dont use smOS, never tried it, i have only one dedicated rig on win7 so its easy to manage. might try it though.

one question, probably answer is already in the thread (sorry). can you NOT have rigs auto update unless given permission. something like "update available, proceed? (Y/n)". reason is mainly i DO NOT like auto updates in a production rig, especially something that may have around 2 grand in hardware sitting in it. i prefer to wait a bit and monitor forums to make sure there are no surprises. might be new mining software pushes a card past its bios mod (claymores has done this), more power draw on systems near its max, temp issues etc. all are fine if someone is there to initiate the update and watch it for a bit.

Last year, I did explore ethOS too when my team decided to move away from Windows - but we didn't like the interface and the way it was licensed. Most of all, they were very slow in updating latest release of popular miners.

smOS is perfect way to manage farms, and works either ways for a few rigs too.

Tytanick just added and updated Claymore ZEC v12.2 and Optiminer 1.7 recently and it was very well timed when ZEC when crazy in the last 24 hours. He is usually very fast in the updates -- this is crucial to catch the uptrend moments in the crypto-mining world.

I only have 33 rigs to manage (thats the max number I can afford for power).

Now, 30 rigs are on smOS since January and very stable - especially if it was stable under Windows, then it should be on smOS. I sleep better at night too. The other 3 rigs are test rigs on 2 x Windows and 1 x LDW Linux -- they mine too when not in test/dev mode.

With SRR system in place, I hope the farm will auto-manage itself and further increases its productivity and reduced downtime, resulting in more consistent mining revenue and operations.

Good luck in your farm.