I road DASH up and now switch over to ETH and a few others  Lets keep going up ETH! |
|
|
|
|
First time I have seen or heard this scam but honestly kinda ingenious and each day is something new lol.
|
|
|
|
|
Also with VER0017 is a single miner unlike claymore? (wanted to clarify)
|
|
|
|
Same question as before but with pictures, miner is hashing away when suddenly the whole OS slows down to a snail pace where i have to wait for 20 seconds for every action to go through and the hash rate is cut by 50% with the GPUs doing this strange hashing pattern:  Please advise, this happens on any pool i try, in both dual mining and ETH only mode, across multiple overclocks.. This is a soft crash; if you have already tried lower OC; it is most likely being caused by too low of a powerlimit. What GPUs / clocks / powerlimits are you using? 7 x gigabyte 1070 FE, each at 120 pl and clocked +200/+1600, turns out this also happens in ETH only mode, not just dual mining. any suggestions? If you want to keep that OC, you will need more power. 120 is not enough to maintain that OC (based on from my experience with my 1070s) I had to give them at least 135-145 to do +200/1600 solo mining ETH. |
|
|
|
I researched into it and from what people are reporting it is true. 1060 gets the best increase upwards of 15-30% (like you saw) Average hash from what people were reprtong was about 29-31MH/s for a 1060. while 1070 gets about 3-5% and 1080TI gets 2% |
|
|
|
I am trying to start using your operating system. Unfortunately I am not able to properly start it. This is what I am getting at login:  Got this error as well once, it was from a bad format of the USB and therefore was not bootable. Try re-imaging the flash drive using HDDRawcopy. |
|
|
|
Let me begin by joining the chorus of miners praising this effort. I spent a week working towards the same goal before finding this thread. I think you've probably saved me a month of evenings developing something similar. Sending some hashes your way as I test!
I'm using an msi z170a m5 with 4 Asus GTX 1060 6G GPUs on an 850w PSU. I'm also running a single gtx 1060 on a muuuuch older board Asus p5n-d (yes that old) and nvOC still works like a charm.
One thing I've noticed with nvOC versus my own Linux install is that I can't seem to get the same hashrate in nvOC. Even if I set the pl to 140 for the card, push memory all the way to 2000 and the GPU clock offset to 130, I can't break 21 MHS in nvOC. Comparatively, if I just load Ubuntu 16.04 with xorg, gnome and latest drivers with Claymore dual mining ETH and SC, I can sustain 23 MHS for days. Same if I put a card on my Win10 box and use MSI Afterburner to contro OC there. I've tried throwing configurations at my nvOC node manually with nvidia-settings -a and it just doesn't seem to get beyond 20 MHS. I can open the nvidia control panel and verify all the settings took. The only difference I can find so far between nvOC and my own build is that I was still using 375.66 version of the driver and nvOC appears to be using 378.13.
Anyone have any thoughts or suggestion of what else I could try? I'd love to switch all my gear to this but right now I'm getting better hash rates out of a 1060 in win10 and 1060s on Ubuntu not using nvOC. And across multiple 8 GPU rigs, the delta adds up.
Thanks!
From most data sets you will get slighly better hashrate from Windows still, even some 1070's I have seen pushing 31-33 while on Ubuntu I have only gotten 29-31. The biggest advantage though I will say is stability, Ubuntu has shown more constant and stable hashrate by far then any Windows PC (this is beyond the Win 10 auto update on home edition) |
|
|
|
|
Thought I would give an update. After adjusting the power settings and doing some specific troubleshooting I have gotten the rig stable for 24 hours.
I took fullzero and Maxximus007 suggestions on the power settings and give it a bit more with more modest OC. It seems to have resolved the issue, as well I have found that one of the cards was not liking bigger OC's while the other 5 worked fine.
This was the outcome.
ETH - Total Speed: 180.068 Mh/s, Total Shares: 2000, Rejected: 0, Time: 15:48
ETH: GPU0 30.198 Mh/s, GPU1 30.240 Mh/s, GPU2 30.186 Mh/s, GPU3 29.500 Mh/s, GPU4 30.086 Mh/s, GPU5 29.857 Mh/s
SC - Total Speed: 1200.451 Mh/s, Total Shares: 429, Rejected: 0
SC: GPU0 201.322 Mh/s, GPU1 201.599 Mh/s, GPU2 201.240 Mh/s, GPU3 196.667 Mh/s, GPU4 200.575 Mh/s, GPU5 199.048 Mh/s
GPU0 t=62C fan=75%, GPU1 t=48C fan=75%, GPU2 t=64C fan=75%, GPU3 t=61C fan=75%, GPU4 t=60C fan=75%, GPU5 t=49C fan=75%
As for the settings, I have the following settings:
5 cards:
Overclock
cc 100
mc 1275
Powerlimit: 125 watts
1 card:
cc -100
mc 1225
Powerlimit: 120 watts
(this card does not like OC had to tweak it some for it to not cause instability within the rig)
Total watts from the wall: 866/867
I am still taking fullzero advice and adding 4 GB more of RAM it will be here in the next few days.
Maxximus007 or fullzero if you have a BTC,ETH address I would like to send you a small thank you for the help on troubleshooting.
|
|
|
|
I'm really confused now, it just happened on VER15 within 15 minutes... With a different USB drive...
To my knowledge this should not be happening since these are 8GB cards and it will hit 3GB DAG file next year for ETH...
I've had these errors once too, but it was OC. Your temps are nice so that's not the issue. Lower both OC and MC with 100, see if it is stable then. If so, go up with 50, MC first. I would try Maxximus007's suggestion. Let me know if you keep getting these errors. It is also possible that having less free space contributes to these errors with claymore; I think I am going to increase the size of the primary partition to very close to 16gb for the next version for this reason. Optimally for claymore you should have up to 16gb of free space and use it as virtual memory, I am considering pushing the size to 32gb and implementing this in an alternative build for better ethash mining. I changed the OC by mem by 15 and it has been solid for the last 90 minutes. I just think it is very odd since it was on the OC for almost a week. I didn't know you changed the primary partition, I think many of us are using 32GB USB keys too. You can extend the primary partition on any key, by connecting it to a computer with nvOC that has already booted and clicking the ubuntu launcher at the top left and typing gp then click Gparted. Find the sdb drive select the larger partition; it it is mounted unmount it; then rightclick and select resize and set the max size. click the green checkmark to execute the change, wait for completion and it should be ~17gb larger. I will do this + add the cmds to enable Claymore to use 16gb VM in the next version. This is starting to be very frustrating overall, after 8 hours it just "froze" no crash, no failure just frozen... Had to hard reset it. Another question is, what is people's variance on hashrate? I have my go up and down quite often between 177-180. Sometimes goes down to 175. Anyone else have variance with mining? Is this caused by dual mining? I am starting to think a possible hardware failure somewhere with the lack of stability in the rig.. Dual mining is always less stable, especially with OC and powerlimit. What ram, PSU, and CPU are you using? Humm something to consider, when I use to do this dual mining wasn't even an option. Here is the info you requested: PSU: Seasonic 1050 CPU: Intel Celeron g3930 RAM: Crucial 4GB. Might be more stable with 16gb of virtual ram; Claymore intermittently uses the CPU intensively and 4GB might not always be enough of a buffer for your cards. To increase stability you could also try raising your powerlimit slightly and lowering dcri, I have raised the powerlimit on all the cards, which I think helped. Do you think adding more RAM would help it? Could get at least another 4GB DIMM. Most likely; but its one of those things that's almost impossible to isolate; so its hard to say what actually makes the difference. Well RAM is cheap it wouldn't hurt not including, can never have enough DIMMs sitting around lmao. Just ordered and will have it on Tuesday. Love amazon prime. Thanks fullzero  |
|
|
|
I'm really confused now, it just happened on VER15 within 15 minutes... With a different USB drive...
To my knowledge this should not be happening since these are 8GB cards and it will hit 3GB DAG file next year for ETH...
I've had these errors once too, but it was OC. Your temps are nice so that's not the issue. Lower both OC and MC with 100, see if it is stable then. If so, go up with 50, MC first. I would try Maxximus007's suggestion. Let me know if you keep getting these errors. It is also possible that having less free space contributes to these errors with claymore; I think I am going to increase the size of the primary partition to very close to 16gb for the next version for this reason. Optimally for claymore you should have up to 16gb of free space and use it as virtual memory, I am considering pushing the size to 32gb and implementing this in an alternative build for better ethash mining. I changed the OC by mem by 15 and it has been solid for the last 90 minutes. I just think it is very odd since it was on the OC for almost a week. I didn't know you changed the primary partition, I think many of us are using 32GB USB keys too. You can extend the primary partition on any key, by connecting it to a computer with nvOC that has already booted and clicking the ubuntu launcher at the top left and typing gp then click Gparted. Find the sdb drive select the larger partition; it it is mounted unmount it; then rightclick and select resize and set the max size. click the green checkmark to execute the change, wait for completion and it should be ~17gb larger. I will do this + add the cmds to enable Claymore to use 16gb VM in the next version. This is starting to be very frustrating overall, after 8 hours it just "froze" no crash, no failure just frozen... Had to hard reset it. Another question is, what is people's variance on hashrate? I have my go up and down quite often between 177-180. Sometimes goes down to 175. Anyone else have variance with mining? Is this caused by dual mining? I am starting to think a possible hardware failure somewhere with the lack of stability in the rig.. Dual mining is always less stable, especially with OC and powerlimit. What ram, PSU, and CPU are you using? Humm something to consider, when I use to do this dual mining wasn't even an option. Here is the info you requested: PSU: Seasonic 1050 CPU: Intel Celeron g3930 RAM: Crucial 4GB. Might be more stable with 16gb of virtual ram; Claymore intermittently uses the CPU intensively and 4GB might not always be enough of a buffer for your cards. To increase stability you could also try raising your powerlimit slightly and lowering dcri, I have raised the powerlimit on all the cards, which I think helped. Do you think adding more RAM would help it? Could get at least another 4GB DIMM. |
|
|
|
I'm really confused now, it just happened on VER15 within 15 minutes... With a different USB drive...
To my knowledge this should not be happening since these are 8GB cards and it will hit 3GB DAG file next year for ETH...
I've had these errors once too, but it was OC. Your temps are nice so that's not the issue. Lower both OC and MC with 100, see if it is stable then. If so, go up with 50, MC first. I would try Maxximus007's suggestion. Let me know if you keep getting these errors. It is also possible that having less free space contributes to these errors with claymore; I think I am going to increase the size of the primary partition to very close to 16gb for the next version for this reason. Optimally for claymore you should have up to 16gb of free space and use it as virtual memory, I am considering pushing the size to 32gb and implementing this in an alternative build for better ethash mining. I changed the OC by mem by 15 and it has been solid for the last 90 minutes. I just think it is very odd since it was on the OC for almost a week. I didn't know you changed the primary partition, I think many of us are using 32GB USB keys too. You can extend the primary partition on any key, by connecting it to a computer with nvOC that has already booted and clicking the ubuntu launcher at the top left and typing gp then click Gparted. Find the sdb drive select the larger partition; it it is mounted unmount it; then rightclick and select resize and set the max size. click the green checkmark to execute the change, wait for completion and it should be ~17gb larger. I will do this + add the cmds to enable Claymore to use 16gb VM in the next version. This is starting to be very frustrating overall, after 8 hours it just "froze" no crash, no failure just frozen... Had to hard reset it. Another question is, what is people's variance on hashrate? I have my go up and down quite often between 177-180. Sometimes goes down to 175. Anyone else have variance with mining? Is this caused by dual mining? I am starting to think a possible hardware failure somewhere with the lack of stability in the rig.. Dual mining is always less stable, especially with OC and powerlimit. What ram, PSU, and CPU are you using? Humm something to consider, when I use to do this dual mining wasn't even an option. Here is the info you requested: PSU: Seasonic 1050 CPU: Intel Celeron g3930 RAM: Crucial 4GB. |
|
|
|
I'm really confused now, it just happened on VER15 within 15 minutes... With a different USB drive...
To my knowledge this should not be happening since these are 8GB cards and it will hit 3GB DAG file next year for ETH...
I've had these errors once too, but it was OC. Your temps are nice so that's not the issue. Lower both OC and MC with 100, see if it is stable then. If so, go up with 50, MC first. I would try Maxximus007's suggestion. Let me know if you keep getting these errors. It is also possible that having less free space contributes to these errors with claymore; I think I am going to increase the size of the primary partition to very close to 16gb for the next version for this reason. Optimally for claymore you should have up to 16gb of free space and use it as virtual memory, I am considering pushing the size to 32gb and implementing this in an alternative build for better ethash mining. I changed the OC by mem by 15 and it has been solid for the last 90 minutes. I just think it is very odd since it was on the OC for almost a week. I didn't know you changed the primary partition, I think many of us are using 32GB USB keys too. You can extend the primary partition on any key, by connecting it to a computer with nvOC that has already booted and clicking the ubuntu launcher at the top left and typing gp then click Gparted. Find the sdb drive select the larger partition; it it is mounted unmount it; then rightclick and select resize and set the max size. click the green checkmark to execute the change, wait for completion and it should be ~17gb larger. I will do this + add the cmds to enable Claymore to use 16gb VM in the next version. This is starting to be very frustrating overall, after 8 hours it just "froze" no crash, no failure just frozen... Had to hard reset it. Another question is, what is people's variance on hashrate? I have my go up and down quite often between 177-180. Sometimes goes down to 175. Anyone else have variance with mining? Is this caused by dual mining? I am starting to think a possible hardware failure somewhere with the lack of stability in the rig.. |
|
|
|
I'm really confused now, it just happened on VER15 within 15 minutes... With a different USB drive...
To my knowledge this should not be happening since these are 8GB cards and it will hit 3GB DAG file next year for ETH...
I've had these errors once too, but it was OC. Your temps are nice so that's not the issue. Lower both OC and MC with 100, see if it is stable then. If so, go up with 50, MC first. I would try Maxximus007's suggestion. Let me know if you keep getting these errors. It is also possible that having less free space contributes to these errors with claymore; I think I am going to increase the size of the primary partition to very close to 16gb for the next version for this reason. Optimally for claymore you should have up to 16gb of free space and use it as virtual memory, I am considering pushing the size to 32gb and implementing this in an alternative build for better ethash mining. I changed the OC by mem by 15 and it has been solid for the last 90 minutes. I just think it is very odd since it was on the OC for almost a week. I didn't know you changed the primary partition, I think many of us are using 32GB USB keys too. |
|
|
|
|
Average temp of them are 50C and one in the center hottest it gets to is 58C.
|
|
|
|
|
I'm really confused now, it just happened on VER15 within 15 minutes... With a different USB drive...
To my knowledge this should not be happening since these are 8GB cards and it will hit 3GB DAG file next year for ETH...
|
|
|
|
|
This is quite odd, but after about 20 hours I received this error on the new ver16. Thinking it maybe a bad OC, I lowered it slightly however after 14 more hours it crashed again.
When it happens, I have to hard reset the miner to come back online.
To me this makes no sense since buffer for DAG errors should only be for 2GB cards and I have 6x 1070 on this rig :/
GPU 0, CUDA error 6- cannot write buffer for DAG
GPU 5, CUDA error 6- cannot write buffer for DAG
GPU 1, CUDA error 6- cannot write buffer for DAG
GPU 3, CUDA error 6- cannot write buffer for DAG
GPU 2, CUDA error 6- cannot write buffer for DAG
GPU 4, CUDA error 6- cannot write buffer for DAG
GPUmienr cu_k01 failed 6 the launch timed out and was terminted
I also get the failed message for all 6 GPUs on this rig.
For the time being I have rolled this rig back to ver15.
|
|
|
|
|
Fullzero,
I want to say that ver16 is much more stable then ver15 and great work on it overall!
Thank you so much for putting this together, disseminating it it and all the hard work you do!
|
|
|
|
Trying to set up my first rig with the Asus z270 series board, Ubuntu 16.04, and 7 1060's. Updated the bios, did all of the gen 2 switching ect yet still can't get more than 5 cards operating at once (It's random each time I reboot whether 4 or 5 seem to work). At first it was the cards with which I had individual sata riser power cables daisy chained (2 cards on each cable) but after unhooking everything and setting it back up that does not seem to be the issue. I have also tried swapping out risers in order to see if one had gone bad also with no luck, ditto with the graphics cards. I am kind of at a loss as what to try at this point in order to get all 7 operational at once.
Which Asus z270 board? Sorry, Prime Asus z270-A. We have the same board, if you see above that is my exact setup including which PCI lanes I am using along with a video with step by step instructions. Checked out that video earlier and made all of the bios changes (on 2 separate boards just in case one was failing) still the same issues. Kind of at a loss. Have you changed your PCI lanes you are using? And have your monitor output to the closest x16 to your CPU? |
|
|
|
Trying to set up my first rig with the Asus z270 series board, Ubuntu 16.04, and 7 1060's. Updated the bios, did all of the gen 2 switching ect yet still can't get more than 5 cards operating at once (It's random each time I reboot whether 4 or 5 seem to work). At first it was the cards with which I had individual sata riser power cables daisy chained (2 cards on each cable) but after unhooking everything and setting it back up that does not seem to be the issue. I have also tried swapping out risers in order to see if one had gone bad also with no luck, ditto with the graphics cards. I am kind of at a loss as what to try at this point in order to get all 7 operational at once.
Which Asus z270 board? Sorry, Prime Asus z270-A. We have the same board, if you see above that is my exact setup including which PCI lanes I am using along with a video with step by step instructions. |
|
|
|
|
Show Posts
