Happy Sunday to you, nvOC folks!  Long time no chat (I'm still on v017 over here, and haven't visited the thread in months since things have been running rock solid for me).

Is anyone out there using an Asus Z270-A (or Z270-AR) with 8-9 GPUs?  I'm running one of each mobos at the moment, with each rig hosting 7 GPUs (1070s).  I'm entertaining the idea of adding 2 more GPUs per rig using m.2 NGFF to PCI-E x4 adapters.  Is anyone out there running 9 GPUs on one of these boards, and if so which adapter make/model are you using?  Any pointers/thing to watch out for?  How stable has it been?

Thanks in advance.

Speaking of stability: OP, one of my rigs was up for 2 months straight.  nvOC has been working out exceedingly well for me.  Thanks once again for all your hard work! 

Yes, I posted about this earlier, but the concern is that would leave nvOC's SSH daemon open to the WAN running with a default password for those of us who don't have another SSH daemon on our LAN to use as an intermediary.  Someone could wreck all sorts of havoc if they had access to a linux box on your local network to use as a launching point, so I personally would want to have my own unique password set before I'll forward any ports to nvOC.  I have a feeling there would be some extra steps involved if one were to change the password for the m1 user on nvOC since oneBash runs commands that require escalation, but I'm not sure where oneBash gets the m1 user's password from when its executing commands.  I'm sure OP can clarify this when he gets caught up on posts.

PS, Fullzero, I'm really liking v0017 so far.  Excellent work!!

If your mobo is sitting out on a table/etc and isn't inside a case take a photo, upload it to imgur, and post it here.  That might help.

Off the top of my head: did you connect the 24 pin ATX power AND the 8 pin CPU power?  Are you sure you have your power switch connected to the proper headers/pins?  If you look closely at the motherboard front panel pins there's a legend to show which pins correspond to power, reset, HDD LED, etc.  Remove your front panel connectors/power switch and try taking a flathead screwdriver and touching it to the 2 power pins simultaneously for about a half second (creating a short between them which is what your power button does) and see if it powers up.

Last but not least... is the toggle switch on your power supply turned on?  Stranger things have happened

You could just use SSH for this if you don't want to setup a VPN server, as SSH also uses AES-256 encryption and is every bit as secure as VPN, plus it's already running!  The only config required would be to apply a static DHCP lease in your router so each miner always has the same LAN IP assigned to it, and to also forward appropriate port(s) in your router (i.e. you could for instance set am unused incoming WAN port like 2222 to forward all inbound traffic on that port to LAN port 22 (default SSH port) on LAN IP 10.20.30.40 if that were the LAN IP for your nvOC rig.  If you have multiple rigs 2222 forwards to port 22 on 10.20.30.40, WAN port 2223 forwards all incoming traffic to LAN port 22 on IP 10.20.30.41, etc).  My only concern here though is that I would want to change the default password (miner1) before opening up an outside port to nvOC's SSH daemon as a clever hacker might scan your WAN IP (which is a thing, bored people/malicious people do this) and find that open port and get lucky somehow by trying "miner1" as a password.  Changing the system password is as simple as running passwd from guake/SSH, but I wouldn't recommend doing that until OP can give some guidance on if that will cause problems within oneBash.  Most of the commands executed in oneBash require privilege escalation and I don't know where it finds the "miner1" password.

OP, can you shed any light on that?  Is it okay to change the password for the m1 user without editing anything else?  I don't see it inside oneBash itself.

If you want to monitor the mining process via screen you're going to have to kill the initial gnome-terminal.  There's no way around that, as screen can only reconnect to an existing screen session.

This shouldn't be a big deal if you have a stable rig.  You only need to do it once per reboot.  My process is:

1. From my desktop where I monitor my rigs I initiate a constant ping:
2. Boot the rig
3. Wait until I begin to get ping responses from the rig, thus indicating Ubuntu has booted and rig has network connectivity
4. SSH into the rig (user: m1  password: miner1)
5. Initiate a screen session:
6. Start nvidia-smi dmon to watch for mining process to begin (by waiting until this happens you know OC settings, fan speed settings, etc have been applied.  Running those commands from within screen isn't 100% consistent IME as I always see error messages when I tried it that way.  It's best to let those settings commands run from gnome-terminal as Ubuntu first boots IMO).
7. Wait until you see wattage go up and GPU utilization go up to 100% (which indicates that the oneBash script concluded and opened the mining process).  Exit nvidia-smi with CTRL + c
8. Find the PID for gnome-terminal.  
9. Kill it:
10. Restart mining:

It might seem like a lot of steps, but it takes all of 120 seconds and you shouldn't need to do it very often once your rig is dialed in.  You're losing maybe 1 minute's worth of hashes on avg of every week?  Pretty negligible considering the convenience of monitoring from another workstation, and you're not using up system resources by using Teamviewer.  This also lets you go completely headless if you buy a dummy HDMI plug.  I just updated from 16 to 17 and didn't need to haul my extra monitor upstairs to do it.  Easy peasy.

I went a step lower than Pentium on my 2 rigs and bought $50 G3930 Celeron processors since I am only GPU mining.  They run nvOC quite stably (I just returned from a 5 day vacation and both of my rigs that were running v0016 stayed up the entire time I was gone).  Granted, I am not using Teamviewer like some folks here.  That will consume more system resources.  I can do everything I need with SSH and the screen command if I'm at home.  I did leave one of my windows workstations online while I was gone so I could teamviewer into that and from there SSH into my rigs if necessary, but luckily I had no need to. 

I have dialed my 1070 FE cards back a bit in order to find higher stability.  My current settings below have been running on my 1070 FE rig for 121 hours (for ETH-only mining):

core OC: 0 (I see absolutely no hashrate increase when mining ETH and OCing core speed)
Mem OC: 1450

Power Limit: 120W

Fan speed 90% (these Founders Ed. cards run very hot compared to my EVGA and MSI cards.  I had one die on me a few days ago after running avg temps of 62C.  I don't know if it was heat-related, but I bumped up my fan speeds after that just in case).

To detach from a screen (i.e. you want to close the SSH connection while mining continues afterwards) it's

To reattach to a screen (resume connection) it's

If you can't remember what you named the session use:


If you're new to screen you may not know you can open a 2nd shell and switch back and forth (i.e. your miner is running on one shell and you open a 2nd to run nvidia-smi):

once in screen you create a 2nd shell (or 3rd, 4th, etc) with

To switch back and forth use:

Just got another notification.  EVGA has "B stock" 1070 SC GAMING cards in stock for $399/ea, limit 4 per household:

https://www.evga.com/products/Product.aspx?pn=08G-P4-6173-RX

Hope this helps someone out there.  FYI I own 2 of these GPUs and have them OC'd, hashing ETH at 29.5 MH/sec.  They might do better than that: they're in a frankenstein rig with 2 other variants of 1070 cards and I haven't tried individual OC settings.

Hey guys (and gals?), I normally wouldn't post something like this, but I know 1070s are getting quite hard to find and I know some of you might appreciate this info.  Dell has PNY 1070s on "sale" for $429 and they'll give you $25 in "rewards."

Not a stellar deal usually, but given the demand for GPUs right now I thought this might help someone out.

AFAIK this isn't a referral link.  I am copying and pasting from slickdeals.net.  I have no horse in this race so to speak, just trying to look out for my fellow nvOC users.

http://www.dell.com/en-us/member/shop/pny-technologies-geforce-gtx-1070-graphics-card-gf-gtx-1070-8-gb-gddr5-pcie-3-0-x16-dvi-hdmi-3-x-displayport/apd/490-bdnl/graphic-video-cards?prg=1&VEN1=10550055-4485850-b15b92ce5ab211e78f958e7a0d52cbc40INT&AID=4485850&dgc=CJ&DGSeg=DHS&cid=198375&lid=45846&acd=12309198375458460&VEN3=813103911618984054

I don't know if this is your issue or not, but worth giving it a shot:

I am mining ETH and am overclocked (~30.9 MH/sec on 1070 Founders Ed cards and ~29.5 MH/sec on a frankenstein rig with 3 different kinds of 1070 cards).

Ok, just checking. 

I'm having a problem with one of my 1070s (Gigabyte Founders Ed.) that was running at 62C.  It lights up at POST, but then after about 30 seconds the light goes out (though the fan stays on) and it's not recognized by claymore.  I pulled it for further testing.  Pretty sure it's failed based on first attempt to get it to start in another machine on my test bench (same behavior; it lights up and then after 30 secs the light goes out and I don't get video).  I'm thinking maybe it was heat, but even 62C isn't outrageous.

Anyone else managed to kill a 1070? 

What are your temps like on those 1070s?

Thanks for v0016, OP!  I'm running it on 1 of 2 rigs for now.  Definitely a big fan of the faster start time!

Refer to the untouched OneBash file for OP's wallet addresses to donate, or you can donate by running your rig with his address(es) still listed in the OneBash file.

Use all 3 of the x16 slots, then begin populating the x1 slots beginning with the one closest to the CPU and moving away from it.


http://i.imgur.com/lytgMw4.jpg

I will 2nd the props for lxde, I have used it on debian and ubuntu EC2 cloud builds (video CDN) and can attest that it is very light on resource usage.  It would likely be an excellent base for nvOC.

It's also fairly easy to use xrdp w/ lxde to run vnc over rdp so wind0ze users can connect via rdp and not have to install any 3rd party apps for remote access.  https://comtechies.com/how-to-set-up-gui-on-amazon-ec2-ubuntu-server.html

I have experienced that exact same issue and it was with 7x gpu (the 7x 1070  reference/founders rig).  I threw in a freshly imaged drive and it has not reoccurred.

If I run across a good deal on one I'll PM ya.  

Regarding EVGA 1070 FTW settings: I may have spoken prematurely.  I did experience a claymore reset overnight.  I will be trying an MC of 1050 and then 1000 if necessary to see if I can get it to run without anymore Claymore drops.  At least when it does drop it immediately resumes, so I'm only losing ~45 secs of hashing, but I know from a long term standpoint it's probably unwise not to address it, so I will dial it back just a bit to pursue 100% error-free operation.

I received my 14th card from Fedex this morning, so now both rigs are running 7 GPUs.  The newest addition is an MSI 1070 Armor.  It's been hashing along for 45m now along with it's EVGA 1070 FTW & SC cousins at the same -200/+1100/125W settings they use so off to a good start.  I do notice the MSI runs about 7-8C hotter than the EVGAs do (they average around 51C at 70% fan speed).

Also my HDMI dummies showed up today, so I can shut off these monitors and save a few watts of power now.