Author

Topic: [ mining os ] nvoc - page 300. (Read 418549 times)

full member
Activity: 238
Merit: 100
July 10, 2017, 03:03:06 AM
Just tried nvOC v0017 on an ASROCK X370 Gaming K4 motherboard and it does not recognize the hardware.

I don't have a x370 mobo and haven't added support for the chipset. 

You can do this by:

Click Ubuntu button on top left and type:

u

Click on software updater

Install updates


If you can't get ubuntu to boot:

If the bios posts; you can access the grub loader menu by pressing

esc

continuously while booting (note holding it down doesn't usually work), then select boot in recovery mode. 

in recovery mode:

Enable networking

then install updates from the cmd prompt:
Code:
sudo apt-get update && sudo apt-get dist-upgrade --yes

and reboot

this should ensure your build has all known system files for your system.


Will give that a shot tonight. Appreciate it!  Wink
sr. member
Activity: 353
Merit: 251
July 10, 2017, 02:49:55 AM
How tricky would it be to use the nvidia-settings commands from within oneBash to run the following command recursively for each card that's detected when it runs, rather than setting a specific power limit or clock offset?

Enable PowerMizer (Prefer Maximum Performance)

nvidia-settings -a '[gpu:0]/GPUPowerMizerMode=1'


essentially this, but with more efficient code because I never was good at foreach loops and such...

if [ $POWERLIMIT == "NO" ]
then
sudo nvidia-settings -a '[gpu:0]/GPUPowerMizerMode=1'
sudo nvidia-settings -a '[gpu:1]/GPUPowerMizerMode=1'
sudo nvidia-settings -a '[gpu:2]/GPUPowerMizerMode=1'
sudo nvidia-settings -a '[gpu:3]/GPUPowerMizerMode=1'
sudo nvidia-settings -a '[gpu:4]/GPUPowerMizerMode=1'
sudo nvidia-settings -a '[gpu:5]/GPUPowerMizerMode=1'
fi

I was going to rewrite exactly these parts of script since I also don't like such code. But before doing so I asked (in another rxOC thread) to put oneBash files to GitHub repository, so such changes will not be like a monkey work to copy/paste a lot. Until that I feel no motivation since I have only couple of rigs with 1050 running nvOC. It might change when I receive 12 PCIe MOBO (waiting for Biostar board from Aliexpress). But I am pretty sure that git is the best way to handle a lot of change requests and integrate them into this great distro or run just own branch.

PS. I was talking about putting oneBash only to a repository, not about full distribution.
full member
Activity: 122
Merit: 100
July 10, 2017, 01:00:51 AM


Thanks for links.    Smiley

You bet..

If you get a second, i posted a while back about an issue I'm having in 0017 where one card runs at 66% capacity while the others are at 100%.  I'm just wondering if that's something you've seen before, and if there might be a straight forward solution to it.  If not, I'll probably just wait until I swap boards in a few days to mess with it since otherwise it's running solid as a rock with all 6 gpus.



Is the hashrate lower with the GPU running at 66%?

Hey FZ - just wanted to let you know I resolved the issue with my underpowered GPU... turns out having 2 risers on one SATA power line is frowned upon... once I put all the GPUs on their own lines the system is back up at 100%


With 1080 or 1080ti that is best; especially if they are AM models.  I haven't heard of anyone needing to do this with 1070s or 1060s; what type of GPUs are you using?


I've got:
2x asus dual 1070
3x EVGA superclock 1070
1x Nvidia 1070 FE in the x16 slot

Asrock z270 Killer SLI/AC mobo (no external power to mobo for pcie (no option for it))
dual 750w PSUs - 1x evga and 1x thermaltake
64gb USB 3 stick

No 1080s in this rig atm, though I had a 1080 ti in there yesterday in the x16 slot so no riser but the problems I've had arose with all 1070s

Before, I had it setup so that:
2 risers were powered on one molex power line
2 riser on 1 SATA lines
3x 1070 each on its own power line (450w); and
mobo/cpu all on the EVGA 750w psu; [all of that should be well within the acceptable range of draw from the PSU]

Then the other 3 1070 GPUs and 1 riser on molex were powered by the 750w thermaltake [again, well within the total power load taking overhead into account]

New setup splits the risers between the PSUs 2 go to separate lines on the EVGA, the other 3 on separate lines on the thermaltake, all on SATA power cables except 1 (though that shouldn't make a difference), and the risers are powered by the same PSU as the GPU main power is coming from whereas before they weren't.
the mobo/cpu are still on the primary EVGA PSU, and the thermaltake is connected by a Y splitter ATX cable.

The result is that the more even power load resolved the problem, though I can't be absolutely certain it was solved by splitting the risers to different lines exclusively.

Which driver version are you using?

Also do you know which GPU model was the one that was insufficiently powered?




I think driver 381.22 is installed right now.  The cards that were underpowered were EVGA superclock 1070s, I had two of them on one SATA power cable and neither one worked properly that way.  Once their risers were on their own lines they work great.  Now I'm not seeing any dips in power - all cards are 100% and pulling about 3.25 sol / watt.
newbie
Activity: 18
Merit: 0
July 09, 2017, 09:51:14 PM
Verge is looking really good, is there any way we can add it to the list? https://bitcointalksearch.org/topic/xvg-verge-powmultialgotori2pno-premineico-1365894
newbie
Activity: 26
Merit: 0
July 09, 2017, 09:07:33 PM
I think I've figured out why my profitability switcher was having problems with some coins.  I noticed it when I tried switching my rig from Genoil back to Claymore (I'm having trouble getting Genoil to run for more than 24 hours without crashing)...the script would run, and I'd end up with two or more instances of the Claymore miner running.

pgrep and pkill, when called with the -f option (to look at the whole command line), need to have "+" escaped for some reason...most likely the pattern is processed as a regular expression and not a simple string.  Any miner command string that included "stratum+tcp" (that's basically all of them except the equihash and Genoil daggerhashimoto miners) thus wasn't searchable or killable.

I've committed a fix that should take care of that.  It also prepends the search string with "^" to match on the miner process itself, not the screen process that spawned it.  (Killing the miner will automatically kill the parent screen process.)

Please test and ensure with confidence; that it is rock solid: then I will integrate these changes. 

It would be helpful if you did so with the integrated oneBash + switch version I made (swap the relevant part of switch with your updated code); so I can be sure it works as intended.

I will be glad to test, just not sure what needs to be changed Sad
full member
Activity: 122
Merit: 100
July 09, 2017, 07:01:25 PM


Thanks for links.    Smiley

You bet..

If you get a second, i posted a while back about an issue I'm having in 0017 where one card runs at 66% capacity while the others are at 100%.  I'm just wondering if that's something you've seen before, and if there might be a straight forward solution to it.  If not, I'll probably just wait until I swap boards in a few days to mess with it since otherwise it's running solid as a rock with all 6 gpus.



Is the hashrate lower with the GPU running at 66%?

Hey FZ - just wanted to let you know I resolved the issue with my underpowered GPU... turns out having 2 risers on one SATA power line is frowned upon... once I put all the GPUs on their own lines the system is back up at 100%


With 1080 or 1080ti that is best; especially if they are AM models.  I haven't heard of anyone needing to do this with 1070s or 1060s; what type of GPUs are you using?


I've got:
2x asus dual 1070
3x EVGA superclock 1070
1x Nvidia 1070 FE in the x16 slot

Asrock z270 Killer SLI/AC mobo (no external power to mobo for pcie (no option for it))
dual 750w PSUs - 1x evga and 1x thermaltake
64gb USB 3 stick

No 1080s in this rig atm, though I had a 1080 ti in there yesterday in the x16 slot so no riser but the problems I've had arose with all 1070s

Before, I had it setup so that:
2 risers were powered on one molex power line
2 riser on 1 SATA lines
3x 1070 each on its own power line (450w); and
mobo/cpu all on the EVGA 750w psu; [all of that should be well within the acceptable range of draw from the PSU]

Then the other 3 1070 GPUs and 1 riser on molex were powered by the 750w thermaltake [again, well within the total power load taking overhead into account]

New setup splits the risers between the PSUs 2 go to separate lines on the EVGA, the other 3 on separate lines on the thermaltake, all on SATA power cables except 1 (though that shouldn't make a difference), and the risers are powered by the same PSU as the GPU main power is coming from whereas before they weren't.
the mobo/cpu are still on the primary EVGA PSU, and the thermaltake is connected by a Y splitter ATX cable.

The result is that the more even power load resolved the problem, though I can't be absolutely certain it was solved by splitting the risers to different lines exclusively.
full member
Activity: 184
Merit: 101
July 09, 2017, 06:16:41 PM
How many NVIDIA GPUs does nvOC support on 1 mainboard?
hero member
Activity: 651
Merit: 501
My PGP Key: 92C7689C
July 09, 2017, 06:12:45 PM
I think I've figured out why my profitability switcher was having problems with some coins.  I noticed it when I tried switching my rig from Genoil back to Claymore (I'm having trouble getting Genoil to run for more than 24 hours without crashing)...the script would run, and I'd end up with two or more instances of the Claymore miner running.

pgrep and pkill, when called with the -f option (to look at the whole command line), need to have "+" escaped for some reason...most likely the pattern is processed as a regular expression and not a simple string.  Any miner command string that included "stratum+tcp" (that's basically all of them except the equihash and Genoil daggerhashimoto miners) thus wasn't searchable or killable.

I've committed a fix that should take care of that.  It also prepends the search string with "^" to match on the miner process itself, not the screen process that spawned it.  (Killing the miner will automatically kill the parent screen process.)
newbie
Activity: 53
Merit: 0
July 09, 2017, 02:50:34 PM
Hi!

Are you already discussed about "ERROR: Looks like GPU0 (or 1 or any) are stopped. Restart attempt" ?
I have this error on one of my 1050Ti cards in about 10 minutes after start Zcash mining.
No overclocking. Just as it is. And after card error all system hangs up deadly if I'm trying to close terminal window. If don't - mining continues but without one card.
And this rig works under win10 for days and weeks w/o problems!

So.. how to fix it?

What are is your powerlimit / mobo / CPU / all GPUs / what COIN are you mining / what mining client are you using?
All default. Didn't touch anything. Powerlimit 100, all GPUs, Zcash on EWBF 0.3.4b from github.
full member
Activity: 122
Merit: 100
July 09, 2017, 01:53:55 PM


Thanks for links.    Smiley

You bet..

If you get a second, i posted a while back about an issue I'm having in 0017 where one card runs at 66% capacity while the others are at 100%.  I'm just wondering if that's something you've seen before, and if there might be a straight forward solution to it.  If not, I'll probably just wait until I swap boards in a few days to mess with it since otherwise it's running solid as a rock with all 6 gpus.



Is the hashrate lower with the GPU running at 66%?

Hey FZ - just wanted to let you know I resolved the issue with my underpowered GPU... turns out having 2 risers on one SATA power line is frowned upon... once I put all the GPUs on their own lines the system is back up at 100%
full member
Activity: 122
Merit: 100
July 09, 2017, 11:41:27 AM


I had a problem with the fat32 partition on my images.  I just had to reimage it... use HDD Raw Copy.  It doesn't ALWAYS work, but it does most of the time.  Also, make sure your flash drive or hard drive is bigger than 16gb.  I ran into a problem with mine where the drive was just a hair shy of the required size for the image and that caused partition file table problems that made the first part unreadable.

You could also use gparted to try to repair the partition which works sometimes.  Or use TestDisk if you're savvy with partition file table manipulation at all.

http://www.cgsecurity.org/wiki/TestDisk_Download





It isn't important at all as you do image what software and in what operating system. At the first loading everything is read perfectly!
Important the fact that after incorrect completion of nvOC (for example the system is too overclocked) data on FAT32 /dev/sda1 are damaged and you are stimulated every time to repair this partition and to do mount, remount. look above how many restarts of nvOC at me happen in days. Every time is a potential problem of damage of FAT32. IMHO needs to refuse this partition, to transfer oneBash to other directory and to modify it, using gnome (local) or ssh, sftp (remote).

Of course I will try to find the stable and balanced configuration of my system. I plunge into Linux more and more and I look for analysis techniques of system dumps.
           All of good luck!
[/quote]

I don't disagree with you that oneBash on a fat32 part instead of exFat isn't ideal for a linux o/s to read.  I've run into problems today where my oneBash file was just empty entirely and so nvOC wouldn't boot.  

Copying oneBash to /home/m1/ on boot might be a more elegant solution to avoid these partition issues, or just avoid that partition entirely by downloading pastebin text directly to /home/m1.

Even windows doesn't like fat32 partitions that small... it forces you to format it in fat instead, so its no surprise that linux doesn't play nice with it I guess.

newbie
Activity: 53
Merit: 0
July 09, 2017, 06:13:41 AM
Hi!

Are you already discussed about "ERROR: Looks like GPU0 (or 1 or any) are stopped. Restart attempt" ?
I have this error on one of my 1050Ti cards in about 10 minutes after start Zcash mining.
No overclocking. Just as it is. And after card error all system hangs up deadly if I'm trying to close terminal window. If don't - mining continues but without one card.
And this rig works under win10 for days and weeks w/o problems!

So.. how to fix it?
full member
Activity: 378
Merit: 104
nvOC forever
July 09, 2017, 05:34:59 AM
I can't thank enough fullZero (Hero as always Smiley) for this really easy nvOC (valuable support) and other community members sharing their valuable time and info, it really really helped a lot of new miners like me to start and learn mining with out much hassle.
Although I've started mining very recently and mostly use google for all the information, it is going so far so good except for the following three things (tried googling but getting irrelevant information - all non nvOC stuff)

I would really appreciate your answers with explanation from our community.

1) Profitability switcher (from latest bash file)


I would like to know how it works? does it works with some particular coins only? What role Algo play in between and how to select a particular Algo?

for eg; in my case I'm mining ETH (dwarf pool) + SIA (Nano), does it help me to gain more with switching, if so can I get the code for it with little explanation.

I might consider myself noob in this case, But I would like to understand how it works and I would like to use it to increase my gains.

2) Using Nice Hash pools

How can I use Nice hash pools with nvOC?

I would like to mine DCR with "stratum+tcp://decred.eu.nicehash.com:3354", can someone please point me to right direction on how to mine and check shares per hour.

I think nice hash uses BTC address, I've tried it to mine with my BTC address (failed when I used DCR address), it was connecting fine and mining well but don't know how to check at what rate its mining (shares per hour etc).

3) DUAL Mining ETH_DCR

I've been using DUAL mining from past month on Ubuntu (not on nvOC), I couldn't figure out how to use pools like suprnova "dcr.suprnova.cc:3252" pool for DCR while dual mining with ETHEREUM (nano)

I do have account on suprnova with worker setup, but not sure how do use that worker with nvOC, can someone please guide me through it.

I would really really appreciate your help regarding this.

Good luck with your mining Smiley

Thanks.



S9k
newbie
Activity: 26
Merit: 0
July 09, 2017, 05:03:05 AM
With the 12x biostar nearly here, I don't think this is the right change to make.  If the biostar can actually run 12x GPUs then I will for sure; not make this alteration.  If it can only support 9x or less GPUs then I will consider making the change.

Speaking of 12gpu motherboards, I've got an ASRock 13 GPU board arriving next week.  Any thoughts on how to configure nvOC with an ASRock to get as many as possible of the GPUs running NVidia?  (my current board is an ASRock z270 that loads 6 GPUs without too much trouble, but the new board is H110, not Z270)  I've got 9 GPUs on hand to try - 8 1070s and a 980 ti.

In theory v0017+ can support 14 GPUs (13 + 1 via m2 adapter with that ASRock mobo).

But the chipset might not currently be supported and there are likely other system changes needed.  I need one of those mobos to test.  Where did you order one from?



https://www.aliexpress.com/item/New-in-BOX-ASRock-Technology-H110-PRO-BTC-H110-mining-board-support-13-graphics-card-DDR4/32822043486.html?spm=2114.13010608.0.0.GrsVzE

With the 12x biostar nearly here, I don't think this is the right change to make.  If the biostar can actually run 12x GPUs then I will for sure; not make this alteration.  If it can only support 9x or less GPUs then I will consider making the change.

Speaking of 12gpu motherboards, I've got an ASRock 13 GPU board arriving next week.  Any thoughts on how to configure nvOC with an ASRock to get as many as possible of the GPUs running NVidia?  (my current board is an ASRock z270 that loads 6 GPUs without too much trouble, but the new board is H110, not Z270)  I've got 9 GPUs on hand to try - 8 1070s and a 980 ti.

In theory v0017+ can support 14 GPUs (13 + 1 via m2 adapter with that ASRock mobo).

But the chipset might not currently be supported and there are likely other system changes needed.  I need one of those mobos to test.  Where did you order one from?

I got mine from Newegg.. according to ASRock, Newegg is expecting another shipment to arrive next week so you might want to setup an autonotify on the website.
He also did not provide any other distributors that I could check for stock, so newegg might be the only source for them right now.


https://www.newegg.com/Product/Product.aspx?Item=N82E16813157781

Thanks for links.    Smiley

https://cryptomined.com/index.php?main_page=product_info&cPath=240_276&products_id=269  SUPX LIMITED EDITION B250 12-GPU MOTHERBOARD
https://www.youtube.com/watch?v=exjRTIZu89Q  How to Build a 12 GPU Mining Rig   Wink
S9k
newbie
Activity: 26
Merit: 0
July 09, 2017, 04:50:30 AM
First off thanks for all the work Fullzero!  

I've been fighting with Win10 on my rig for a month.  Can't get it to recognize any more than 3 of my 1070 cards, and one always is disabled with an error.  So I've decided to dump Win10.

I've just got nvoc 0017 running with my old USB 2.0 stick on my ASUS Prime Z270-A with 6 Geforce GTX 1070s rig and I am not sure now how to get the mining started.  

I guess I was under the impression that it would start automatically on boot but I must have missed something in the setup.  It's just sitting there with the terminal screen open.  

Also in the Nvidia X server settings it's also only recognizing 3 of the 1070 gpus.  I'm hoping this is something that can be easily worked out as I'd hate to think that 3 of the 6 1070's I have only had for a month are bad.

Thanks in advance for any help.

If you had the same problem with windows only recognizing 3 out of 6 GPUs; this indicates there is most likely a hardware problem.

Have you tried swapping your risers?

How are you powering your risers?

What kind of risers are you using?

If you run with only 3x GPUs and it works:

swap out the 3 working GPUs with the 3 that aren't being recognized and see if they work.


Actually hardware wise I've already change motherboards thinking it was the MSI Z170A SLI Plus that I started out with.  I sent it back to Amazon earlier this week and ordered the Asus.

The risers are directly powered by the SATA cable from the PSU.  These are the risers... https://www.amazon.com/Extender-Powered-Extension-Adapter-Card-Currency/dp/B072MFBYCM/ref=sr_1_10?s=electronics&ie=UTF8&qid=1499386958&sr=1-10&keywords=PCIe%2BPowered%2BRiser%2BAdapter%2BCard%2B-%2BUSB%2B3.0%2BPCIe%2B1x%2Bto%2B16x%2BExtender%2BCard%2B-%2B6-Pin%2BPCI-E%2Bto%2BSATA%2BPower%2BCable&th=1

Yes I have swapped them around many time, but when I was on win10, haven't yet with nvoc as I just got it going tonight.  All of them worked in that testing.

Just a side note here....  I shut down the rig after I posted the first post and just powered it back a few mins ago.  Getting this scrolling on the terminal now...

bash: /media/m1/1263-A96E/oneBash: Permission denied
dos2unix: /media/m1/1263-A96E/oneBash: No such file or directory
dos2unix: Skipping /media/m1/1263-A96E/oneBash, not a regular file.

I have to laugh at myself cause I've obviously dorked something up I guess.

This usually means there is a problem with the image.

I would re image the USB key.

Let me know if that works.

hi, it is not problems of image.
these are problems of the FAT32 file system which falls after each incorrect reset. You can find such line in dmesg:

120.350515] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
I don't trust FAT32 and have transferred oneBash to other place.
At me it is impossible to stabilize my system in any way. I observe a large number of restarts which I can't analyse.
Syslog doesn't contain anything useful.

m1@m1-desktop:~$ last reboot
reboot   system boot  4.4.0-83-generic Sun Jul  9 04:36   still running
reboot   system boot  4.4.0-83-generic Sun Jul  9 00:00   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 17:50   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 15:31   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 14:56   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 14:48   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 12:58   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 10:10   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 09:54   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 08:27   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 03:16   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 23:31   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 22:52   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 20:02   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 16:26   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 10:00   still running


I need methodology of a solution. How to find the reason of a collapse of an operating system and restart. What video card exceeds admissible values and is unstable? I think it it will be interesting to many. Thank you very much!


I had a problem with the fat32 partition on my images.  I just had to reimage it... use HDD Raw Copy.  It doesn't ALWAYS work, but it does most of the time.  Also, make sure your flash drive or hard drive is bigger than 16gb.  I ran into a problem with mine where the drive was just a hair shy of the required size for the image and that caused partition file table problems that made the first part unreadable.

You could also use gparted to try to repair the partition which works sometimes.  Or use TestDisk if you're savvy with partition file table manipulation at all.

http://www.cgsecurity.org/wiki/TestDisk_Download





It isn't important at all as you do image what software and in what operating system. At the first loading everything is read perfectly!
Important the fact that after incorrect completion of nvOC (for example the system is too overclocked) data on FAT32 /dev/sda1 are damaged and you are stimulated every time to repair this partition and to do mount, remount. look above how many restarts of nvOC at me happen in days. Every time is a potential problem of damage of FAT32. IMHO needs to refuse this partition, to transfer oneBash to other directory and to modify it, using gnome (local) or ssh, sftp (remote).

Of course I will try to find the stable and balanced configuration of my system. I plunge into Linux more and more and I look for analysis techniques of system dumps.
           All of good luck!
full member
Activity: 122
Merit: 100
July 09, 2017, 03:59:29 AM
First off thanks for all the work Fullzero!  

I've been fighting with Win10 on my rig for a month.  Can't get it to recognize any more than 3 of my 1070 cards, and one always is disabled with an error.  So I've decided to dump Win10.

I've just got nvoc 0017 running with my old USB 2.0 stick on my ASUS Prime Z270-A with 6 Geforce GTX 1070s rig and I am not sure now how to get the mining started.  

I guess I was under the impression that it would start automatically on boot but I must have missed something in the setup.  It's just sitting there with the terminal screen open.  

Also in the Nvidia X server settings it's also only recognizing 3 of the 1070 gpus.  I'm hoping this is something that can be easily worked out as I'd hate to think that 3 of the 6 1070's I have only had for a month are bad.

Thanks in advance for any help.

If you had the same problem with windows only recognizing 3 out of 6 GPUs; this indicates there is most likely a hardware problem.

Have you tried swapping your risers?

How are you powering your risers?

What kind of risers are you using?

If you run with only 3x GPUs and it works:

swap out the 3 working GPUs with the 3 that aren't being recognized and see if they work.


Actually hardware wise I've already change motherboards thinking it was the MSI Z170A SLI Plus that I started out with.  I sent it back to Amazon earlier this week and ordered the Asus.

The risers are directly powered by the SATA cable from the PSU.  These are the risers... https://www.amazon.com/Extender-Powered-Extension-Adapter-Card-Currency/dp/B072MFBYCM/ref=sr_1_10?s=electronics&ie=UTF8&qid=1499386958&sr=1-10&keywords=PCIe%2BPowered%2BRiser%2BAdapter%2BCard%2B-%2BUSB%2B3.0%2BPCIe%2B1x%2Bto%2B16x%2BExtender%2BCard%2B-%2B6-Pin%2BPCI-E%2Bto%2BSATA%2BPower%2BCable&th=1

Yes I have swapped them around many time, but when I was on win10, haven't yet with nvoc as I just got it going tonight.  All of them worked in that testing.

Just a side note here....  I shut down the rig after I posted the first post and just powered it back a few mins ago.  Getting this scrolling on the terminal now...

bash: /media/m1/1263-A96E/oneBash: Permission denied
dos2unix: /media/m1/1263-A96E/oneBash: No such file or directory
dos2unix: Skipping /media/m1/1263-A96E/oneBash, not a regular file.

I have to laugh at myself cause I've obviously dorked something up I guess.

This usually means there is a problem with the image.

I would re image the USB key.

Let me know if that works.

hi, it is not problems of image.
these are problems of the FAT32 file system which falls after each incorrect reset. You can find such line in dmesg:

120.350515] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
I don't trust FAT32 and have transferred oneBash to other place.
At me it is impossible to stabilize my system in any way. I observe a large number of restarts which I can't analyse.
Syslog doesn't contain anything useful.

m1@m1-desktop:~$ last reboot
reboot   system boot  4.4.0-83-generic Sun Jul  9 04:36   still running
reboot   system boot  4.4.0-83-generic Sun Jul  9 00:00   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 17:50   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 15:31   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 14:56   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 14:48   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 12:58   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 10:10   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 09:54   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 08:27   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 03:16   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 23:31   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 22:52   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 20:02   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 16:26   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 10:00   still running


I need methodology of a solution. How to find the reason of a collapse of an operating system and restart. What video card exceeds admissible values and is unstable? I think it it will be interesting to many. Thank you very much!


I had a problem with the fat32 partition on my images.  I just had to reimage it... use HDD Raw Copy.  It doesn't ALWAYS work, but it does most of the time.  Also, make sure your flash drive or hard drive is bigger than 16gb.  I ran into a problem with mine where the drive was just a hair shy of the required size for the image and that caused partition file table problems that made the first part unreadable.

You could also use gparted to try to repair the partition which works sometimes.  Or use TestDisk if you're savvy with partition file table manipulation at all.

http://www.cgsecurity.org/wiki/TestDisk_Download



S9k
newbie
Activity: 26
Merit: 0
July 09, 2017, 02:44:14 AM
First off thanks for all the work Fullzero!  

I've been fighting with Win10 on my rig for a month.  Can't get it to recognize any more than 3 of my 1070 cards, and one always is disabled with an error.  So I've decided to dump Win10.

I've just got nvoc 0017 running with my old USB 2.0 stick on my ASUS Prime Z270-A with 6 Geforce GTX 1070s rig and I am not sure now how to get the mining started.  

I guess I was under the impression that it would start automatically on boot but I must have missed something in the setup.  It's just sitting there with the terminal screen open.  

Also in the Nvidia X server settings it's also only recognizing 3 of the 1070 gpus.  I'm hoping this is something that can be easily worked out as I'd hate to think that 3 of the 6 1070's I have only had for a month are bad.

Thanks in advance for any help.

If you had the same problem with windows only recognizing 3 out of 6 GPUs; this indicates there is most likely a hardware problem.

Have you tried swapping your risers?

How are you powering your risers?

What kind of risers are you using?

If you run with only 3x GPUs and it works:

swap out the 3 working GPUs with the 3 that aren't being recognized and see if they work.


Actually hardware wise I've already change motherboards thinking it was the MSI Z170A SLI Plus that I started out with.  I sent it back to Amazon earlier this week and ordered the Asus.

The risers are directly powered by the SATA cable from the PSU.  These are the risers... https://www.amazon.com/Extender-Powered-Extension-Adapter-Card-Currency/dp/B072MFBYCM/ref=sr_1_10?s=electronics&ie=UTF8&qid=1499386958&sr=1-10&keywords=PCIe%2BPowered%2BRiser%2BAdapter%2BCard%2B-%2BUSB%2B3.0%2BPCIe%2B1x%2Bto%2B16x%2BExtender%2BCard%2B-%2B6-Pin%2BPCI-E%2Bto%2BSATA%2BPower%2BCable&th=1

Yes I have swapped them around many time, but when I was on win10, haven't yet with nvoc as I just got it going tonight.  All of them worked in that testing.

Just a side note here....  I shut down the rig after I posted the first post and just powered it back a few mins ago.  Getting this scrolling on the terminal now...

bash: /media/m1/1263-A96E/oneBash: Permission denied
dos2unix: /media/m1/1263-A96E/oneBash: No such file or directory
dos2unix: Skipping /media/m1/1263-A96E/oneBash, not a regular file.

I have to laugh at myself cause I've obviously dorked something up I guess.

This usually means there is a problem with the image.

I would re image the USB key.

Let me know if that works.

hi, it is not problems of image.
these are problems of the FAT32 file system which falls after each incorrect reset. You can find such line in dmesg:

120.350515] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
I don't trust FAT32 and have transferred oneBash to other place.
At me it is impossible to stabilize my system in any way. I observe a large number of restarts which I can't analyse.
Syslog doesn't contain anything useful.

m1@m1-desktop:~$ last reboot
reboot   system boot  4.4.0-83-generic Sun Jul  9 04:36   still running
reboot   system boot  4.4.0-83-generic Sun Jul  9 00:00   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 17:50   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 15:31   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 14:56   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 14:48   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 12:58   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 10:10   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 09:54   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 08:27   still running
reboot   system boot  4.4.0-83-generic Sat Jul  8 03:16   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 23:31   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 22:52   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 20:02   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 16:26   still running
reboot   system boot  4.4.0-83-generic Fri Jul  7 10:00   still running


I need methodology of a solution. How to find the reason of a collapse of an operating system and restart. What video card exceeds admissible values and is unstable? I think it it will be interesting to many. Thank you very much!
full member
Activity: 122
Merit: 100
July 09, 2017, 01:07:02 AM


Thanks for links.    Smiley

You bet..

If you get a second, i posted a while back about an issue I'm having in 0017 where one card runs at 66% capacity while the others are at 100%.  I'm just wondering if that's something you've seen before, and if there might be a straight forward solution to it.  If not, I'll probably just wait until I swap boards in a few days to mess with it since otherwise it's running solid as a rock with all 6 gpus.



Is the hashrate lower with the GPU running at 66%?

yeah by about 100 sol/sec or so

EDIT: actually by about 130 sol/sec, and the power going to the card is only 2/3 most of the time... 145-150w for other cards, and only 85-110w for that one.
newbie
Activity: 13
Merit: 0
July 09, 2017, 12:34:34 AM
First off thanks for all the work Fullzero!  

I've been fighting with Win10 on my rig for a month.  Can't get it to recognize any more than 3 of my 1070 cards, and one always is disabled with an error.  So I've decided to dump Win10.

I've just got nvoc 0017 running with my old USB 2.0 stick on my ASUS Prime Z270-A with 6 Geforce GTX 1070s rig and I am not sure now how to get the mining started.  

I guess I was under the impression that it would start automatically on boot but I must have missed something in the setup.  It's just sitting there with the terminal screen open.  

Also in the Nvidia X server settings it's also only recognizing 3 of the 1070 gpus.  I'm hoping this is something that can be easily worked out as I'd hate to think that 3 of the 6 1070's I have only had for a month are bad.

Thanks in advance for any help.

If you had the same problem with windows only recognizing 3 out of 6 GPUs; this indicates there is most likely a hardware problem.

Have you tried swapping your risers?

How are you powering your risers?

What kind of risers are you using?

If you run with only 3x GPUs and it works:

swap out the 3 working GPUs with the 3 that aren't being recognized and see if they work.


Actually hardware wise I've already change motherboards thinking it was the MSI Z170A SLI Plus that I started out with.  I sent it back to Amazon earlier this week and ordered the Asus.

The risers are directly powered by the SATA cable from the PSU.  These are the risers... https://www.amazon.com/Extender-Powered-Extension-Adapter-Card-Currency/dp/B072MFBYCM/ref=sr_1_10?s=electronics&ie=UTF8&qid=1499386958&sr=1-10&keywords=PCIe%2BPowered%2BRiser%2BAdapter%2BCard%2B-%2BUSB%2B3.0%2BPCIe%2B1x%2Bto%2B16x%2BExtender%2BCard%2B-%2B6-Pin%2BPCI-E%2Bto%2BSATA%2BPower%2BCable&th=1

Yes I have swapped them around many time, but when I was on win10, haven't yet with nvoc as I just got it going tonight.  All of them worked in that testing.

Just a side note here....  I shut down the rig after I posted the first post and just powered it back a few mins ago.  Getting this scrolling on the terminal now...

bash: /media/m1/1263-A96E/oneBash: Permission denied
dos2unix: /media/m1/1263-A96E/oneBash: No such file or directory
dos2unix: Skipping /media/m1/1263-A96E/oneBash, not a regular file.

I have to laugh at myself cause I've obviously dorked something up I guess.



As fullzero mentioned the image or partioning on your USB stick may have issues.   Depends on how you installed the image.  I used Etcher in Ubuntu and had no problems (yes having Linux on another box saves you a lot of trouble).  When I installed nvOC 17 on my SSD, I had to change the 2Unix file.  By default the oneBash sits on the 9Gig partition.  I copied over to the home directory where the 2unix file sits and just changed the 2Unix file pointing it to the new location.  Problem solved.

Swapping out my MSI Z170 Gaming M5 boards for the ASUS Z270 Prime-A boards solved a lot of instability problems that I thought were riser related.  Additionally these boards are awesome for running 9 GPUs or more.  I have 9 x 1050Tis (1506 Boost Clock versions) running solid on these boards (0 Core OC, 1550 Mem OC, power limit 65, 133 MH/s per rig).
full member
Activity: 122
Merit: 100
July 08, 2017, 11:34:21 PM


Thanks for links.    Smiley

You bet..

If you get a second, i posted a while back about an issue I'm having in 0017 where one card runs at 66% capacity while the others are at 100%.  I'm just wondering if that's something you've seen before, and if there might be a straight forward solution to it.  If not, I'll probably just wait until I swap boards in a few days to mess with it since otherwise it's running solid as a rock with all 6 gpus.

Jump to: