[OS] nvOC easy-to-use Linux Nvidia Mining

[Missing]

Hi, I am using Asus b250 mining expert with Zotac 1070z.   I had installed v0019-1.3 version.   I managed to bring 4 gpu to mine. If I plug in 5th, i will get error "unable to get temperature internal error 15" and the particular GPU is down and the rest of 4 are working. I did changed 5 gpu to another 5 set of gpu and still got same problem.

I had plus the monitor to PCIe 16x gpu and enable the CSM setting. 

 If I install more than 5 gpu, can't enter to OS.  Black screen after boots.   Please help

have you tried reseting the mothing to optimized settings and switching PCI riser card?

I tried all and still same problem

[MentalNomad]

It seems it only writes the 1hash file and nothing else. It splits the USD into two partitions, one contains the 1hash, and the other is "unformatted."

I'm sure, and kind of hoping that, I'm "missing some mundane detail." Does anyone have ideas what is going wrong?

Thanks

Joe

Mundane detail:

The image is a for a USB stick with two partitions:
1. A windows-readable partition with the 1bash file so you can pre-load it with your info from windows.
2. A linux-readable partition with everything else.

The linux-readable partition won't be recognizable to Windows, unless you install third-party software into Windows that allows it to work with EXT4 partitions. That's why fullzero made the two-partition system.

If you boot off that USB stick, on the first boot, it will copy that 1bash file into the /home/m1 directory (which is the "home" directory for the default "m1" account) and use it. Going forward, you'll need to make any edits to 1bash in place; it won't always copy the 1bash from the windows partition.

[MentalNomad]

Hi, I am using Asus b250 mining expert with Zotac 1070z.   I had installed v0019-1.3 version.   I managed to bring 4 gpu to mine. If I plug in 5th, i will get error "unable to get temperature internal error 15" and the particular GPU is down and the rest of 4 are working. I did changed 5 gpu to another 5 set of gpu and still got same problem.

I had plus the monitor to PCIe 16x gpu and enable the CSM setting.  

 If I install more than 5 gpu, can't enter to OS.  Black screen after boots.   Please help

have you tried reseting the mothing to optimized settings and switching PCI riser card?

I tried all and still same problem

Are you trying to power three risers from a single PCI power cable? That often causes problems for me - try to stick with two riser per power cable and see if that helps.

Also, try using different PCIe X1 slots on the mobo, instead, just in case one of those is trouble. (But always include one card plugged into the PCIe x16 slot, connect to your monitor.)

Also, if using two PSUs (A and B) with a single motherboard powered by PSU A, make sure that a graphics card powered by PSU B also has the riser powered by PSU B. I find that powering the GPU and riser from different PSUs leads to instability.

[Missing]

Hi, I am using Asus b250 mining expert with Zotac 1070z.   I had installed v0019-1.3 version.   I managed to bring 4 gpu to mine. If I plug in 5th, i will get error "unable to get temperature internal error 15" and the particular GPU is down and the rest of 4 are working. I did changed 5 gpu to another 5 set of gpu and still got same problem.

I had plus the monitor to PCIe 16x gpu and enable the CSM setting.  

 If I install more than 5 gpu, can't enter to OS.  Black screen after boots.   Please help

have you tried reseting the mothing to optimized settings and switching PCI riser card?

I tried all and still same problem

Are you trying to power three risers from a single PCI power cable? That often causes problems for me - try to stick with two riser per power cable and see if that helps.

Also, try using different PCIe X1 slots on the mobo, instead, just in case one of those is trouble. (But always include one card plugged into the PCIe x16 slot, connect to your monitor.)

Also, if using two PSUs (A and B) with a single motherboard powered by PSU A, make sure that a graphics card powered by PSU B also has the riser powered by PSU B. I find that powering the GPU and riser from different PSUs leads to instability.

1) all cable is limited at 2 riser only

2) all riser and gpu power are powered by same PSU.   If riser is psu B, then gpu is also psu B

3) if I use ethos, can get 12  gtx 1070 working. But NVoC is only 4

[papampi]

Just installed this nvoc on one of my rigs, looks good. So questions though (no, I did not read all the pages..):

- Is there a way to limit telegram messages to be sent only when there is something wrong, i.e. reboot of server or miner is needed ?
- My rig has some stability issues, I am mining Ethereum with ethminer. In order to track the GPUs causing problems they would have to be run as separate instances/sessions, (xmos does this by default). Any plans for implementing such feature? If not maybe I try with claymore or plug in xmos USB stick, adjust overclock settings and copy them to nvOC.

--
Tigel

I suggest you to read the notes and comments on /home/m1/kk003_telegram and see if its ok for your needs.
Or you can go here:
https://pastebin.com/vPnb6TKn

and see.

I guess if you leave empty var USER_CUSTOM_TIMES_TO_SEND_TELEGRAM you'll get only warnings (including warnings from IAmNotAJeep_and_Maxximus007_WATCHDOG).

Form:

Code:

USER_CUSTOM_TIMES_TO_SEND_TELEGRAM=("12:00" "18:00" "21:32")

To:

Code:

USER_CUSTOM_TIMES_TO_SEND_TELEGRAM=()

I did not do this check, hope it works for you (I think so).
Let me know if it does not and I'll fix it.

You may too set USER_CUSTOM_TIMES_TO_SEND_TELEGRAM like this:

Code:

USER_CUSTOM_TIMES_TO_SEND_TELEGRAM=("18:00")

to get a telegram once a day at 18:00 (or any other time/s of day you want)

Here is the warnings list (most of them):

Code:

# Some warning you can choose to get via telegram or not 
SEND_WARNING_SYSTEM_RESTARTED="YES" # YES or NO
SEND_WARNING_XORG_RESTARTED="YES"   # YES or NO
SEND_WARNING_LOAD_AVERAGE="YES"     # YES or NO
SEND_WARNING_CHECK_DISPLAY="YES"    # YES or NO
SEND_WARNING_WHEN_NO_L_ON_SCREEN="YES"  # YES or NO     YES send a telegram when screen is not starting miner with -L (create log file)

And some info you may choose to get or not in your telegram msg:

Code:

# some information you can choose to receive or not on your telegram msg
SEND_REBOOT_REQUIRED="YES"      # YES or NO
SEND_WORKERNAME="YES"           # YES or NO
SEND_MINING_COIN="YES"          # YES or NO
SEND_MINING_ADDRESS="YES"       # YES or NO
MASK_MINING_ADDRESS="YES"       # YES or NO
SEND_MINER_EXEC_NAME="YES"      # YES or NO
SEND_MINER_EXEC_PATH="YES"      # YES or NO
SEND_MINER_UP_TIME="YES"        # YES or NO
SEND_PRIVATE_IP="YES"           # YES or NO
SEND_PUBLIC_IP="YES"            # YES or NO
MASK_PUBLIC_IP="NO"             # YES or NO
SEND_SSHD_PORT="YES"            # YES or NO
SEND_UP_SINCE="YES"         # YES or NO
SEND_UP_TIME="YES"          # YES or NO
SEND_RAM="YES"              # YES or NO
SEND_CPU_MODEL="YES"            # YES or NO
SEND_LOGGED_USERS="YES"         # YES or NO
 
CUSTOMIZE_SYSTEM_NAME=""        # "PRIVATE_IP" or "PUBLIC_IP" or "AnY CusTom nAme you want here", if empty it uses the system's hostname
                    # This is the main header you'll get in your telegram message
                    # PRIVATE_IP will use your private ip/s (remenber you may have more than one)
                    # PUBLIC_IP will use your public ip

Warnings auto-clear when system gets back to normal.

I try to read your huge script and i think you're a very experienced scripter. Thank for it.

But i see multiple auto_gram openden when WTM restart 3main at each switching coin. and i get en ps error but i don't know how.
I will post tomorrow in this thread about that

That "ps ... " error is  when miner restarted and script cant catch miner up time, you can ignore it.


I changed WTM  auto switch so it dont restart 3main and only start miner, you can test new version in z_papampi_versions

First copy PAPAMPI_WTM,  WTM_AUTO_SWITCH from /home/m1 to a new folder to keep my old version, then copy and replace my versions from  z_papampi_versions to /home/m1/

My new version just restart miner and wdog (to prevent wdog from catching gpu under utilizations) and get faster switch (under 30 seconds with 7 cards)
If you add any new coins or edit miners in 3main you should do the same in wtm-miner,
The new version doesnt work with damNmad OC, so you should disable it.

[papampi]

Just installed this nvoc on one of my rigs, looks good. So questions though (no, I did not read all the pages..):

- Is there a way to limit telegram messages to be sent only when there is something wrong, i.e. reboot of server or miner is needed ?
- My rig has some stability issues, I am mining Ethereum with ethminer. In order to track the GPUs causing problems they would have to be run as separate instances/sessions, (xmos does this by default). Any plans for implementing such feature? If not maybe I try with claymore or plug in xmos USB stick, adjust overclock settings and copy them to nvOC.

--
Tigel

I suggest you to read the notes and comments on /home/m1/kk003_telegram and see if its ok for your needs.
Or you can go here:
https://pastebin.com/vPnb6TKn

and see.

I guess if you leave empty var USER_CUSTOM_TIMES_TO_SEND_TELEGRAM you'll get only warnings (including warnings from IAmNotAJeep_and_Maxximus007_WATCHDOG).

Form:

Code:

USER_CUSTOM_TIMES_TO_SEND_TELEGRAM=("12:00" "18:00" "21:32")

To:

Code:

USER_CUSTOM_TIMES_TO_SEND_TELEGRAM=()

I did not do this check, hope it works for you (I think so).
Let me know if it does not and I'll fix it.

You may too set USER_CUSTOM_TIMES_TO_SEND_TELEGRAM like this:

Code:

USER_CUSTOM_TIMES_TO_SEND_TELEGRAM=("18:00")

to get a telegram once a day at 18:00 (or any other time/s of day you want)

Here is the warnings list (most of them):

Code:

# Some warning you can choose to get via telegram or not 
SEND_WARNING_SYSTEM_RESTARTED="YES" # YES or NO
SEND_WARNING_XORG_RESTARTED="YES"   # YES or NO
SEND_WARNING_LOAD_AVERAGE="YES"     # YES or NO
SEND_WARNING_CHECK_DISPLAY="YES"    # YES or NO
SEND_WARNING_WHEN_NO_L_ON_SCREEN="YES"  # YES or NO     YES send a telegram when screen is not starting miner with -L (create log file)

And some info you may choose to get or not in your telegram msg:

Code:

# some information you can choose to receive or not on your telegram msg
SEND_REBOOT_REQUIRED="YES"      # YES or NO
SEND_WORKERNAME="YES"           # YES or NO
SEND_MINING_COIN="YES"          # YES or NO
SEND_MINING_ADDRESS="YES"       # YES or NO
MASK_MINING_ADDRESS="YES"       # YES or NO
SEND_MINER_EXEC_NAME="YES"      # YES or NO
SEND_MINER_EXEC_PATH="YES"      # YES or NO
SEND_MINER_UP_TIME="YES"        # YES or NO
SEND_PRIVATE_IP="YES"           # YES or NO
SEND_PUBLIC_IP="YES"            # YES or NO
MASK_PUBLIC_IP="NO"             # YES or NO
SEND_SSHD_PORT="YES"            # YES or NO
SEND_UP_SINCE="YES"         # YES or NO
SEND_UP_TIME="YES"          # YES or NO
SEND_RAM="YES"              # YES or NO
SEND_CPU_MODEL="YES"            # YES or NO
SEND_LOGGED_USERS="YES"         # YES or NO
 
CUSTOMIZE_SYSTEM_NAME=""        # "PRIVATE_IP" or "PUBLIC_IP" or "AnY CusTom nAme you want here", if empty it uses the system's hostname
                    # This is the main header you'll get in your telegram message
                    # PRIVATE_IP will use your private ip/s (remenber you may have more than one)
                    # PUBLIC_IP will use your public ip

Warnings auto-clear when system gets back to normal.

I try to read your huge script and i think you're a very experienced scripter. Thank for it.

But i see multiple auto_gram openden when WTM restart 3main at each switching coin. and i get en ps error but i don't know how.
I will post tomorrow in this thread about that

Thx  . I don't have a nvoc 19+ installed. The script was tested on nvoc 19 stable so I don't know yet how to get it working with WMT switch.
If some one have WMT switch working on Nvoc 19 stable and want to share a how to I'll be happy to modify the script.
Post what you have anyway.

Let me know what you need from WTM and I provide it for your telegram
These are the additional info WTM gives:

Code:

BTC Price:: 7111 USD
WTM Current Profitabilty: HUSH:113 % ETH:100 % ZEN:95 % ZEC:94 % 
WTM Current USD Revenue: HUSH:14.82 ETH:13.15 ZEN:12.49 ZEC:12.39 
WTM 24H Average Revenue: 14.8939 USD 

[papampi]

I just noticed BTCZ in 1bash, what is it ?
when it came out ?
Whats the difference BTCZ and BTCG ?

[elsystem]

On several occasions the OS crashes with kernel issues (cannot start init etc.) on nvOC 19-1.4 on an MSI Z170A M5 with 7 1070 GPUs, running on a 32gb USB drive. I've had to rewrite the OS several times. It works fine for a couple of days and then I get the same message again.

Any ideas what could the issue be?

First thing is to set up nvOC on USB only for testing purposes ... not for long run.
Get a 30$ SSD, and check again.

USB keys are good for testing different versions; or for trying out nvOC for the first time.  But in the long run an SSD will likely outlast multiple USB keys.

We miners are spending thousands on our rigs and when it comes to stability and life span we forget the most important part and thats where the OS is installed on, we think small and go cheap with a 5-10$ USB when we can have much smoother system with a 30$ SSD.

Using USB as daily use is not recommended in any distro, The most important  difference other than USB read/write limit is there's no way for a USB drive to mark bad cells as 'do not use'  whereas the SSD may develop bad areas it can ignore them. With a USB drive one cell goes bad and the whole drive is useless.

I'm Not saying that you shouldn't use a USB for bootable OS, just that it's not a good idea to have it as your main boot drive and only use them for diagnostic / testing purposes.
No mining system should be run from USB as a daily hardcore mining system, but run it on usb, test OS and see if you like it, then install it on SSD.

I think mining with nvOC on USB is only good for those who want to mine when their pc is not in use, so they boot with usb, mine for a while then reboot back to their main OS...

I got the same error on my SSD several times and that's why I switched to a USB drive. I don't have these issues with the same spec rig with 6 1070 GPUs only. Can the number of GPUs affect performance on the MSI Z170A M5? I'll switch back to an SSD and see how it goes.

[papampi]

On several occasions the OS crashes with kernel issues (cannot start init etc.) on nvOC 19-1.4 on an MSI Z170A M5 with 7 1070 GPUs, running on a 32gb USB drive. I've had to rewrite the OS several times. It works fine for a couple of days and then I get the same message again.

Any ideas what could the issue be?

First thing is to set up nvOC on USB only for testing purposes ... not for long run.
Get a 30$ SSD, and check again.

USB keys are good for testing different versions; or for trying out nvOC for the first time.  But in the long run an SSD will likely outlast multiple USB keys.

We miners are spending thousands on our rigs and when it comes to stability and life span we forget the most important part and thats where the OS is installed on, we think small and go cheap with a 5-10$ USB when we can have much smoother system with a 30$ SSD.

Using USB as daily use is not recommended in any distro, The most important  difference other than USB read/write limit is there's no way for a USB drive to mark bad cells as 'do not use'  whereas the SSD may develop bad areas it can ignore them. With a USB drive one cell goes bad and the whole drive is useless.

I'm Not saying that you shouldn't use a USB for bootable OS, just that it's not a good idea to have it as your main boot drive and only use them for diagnostic / testing purposes.
No mining system should be run from USB as a daily hardcore mining system, but run it on usb, test OS and see if you like it, then install it on SSD.

I think mining with nvOC on USB is only good for those who want to mine when their pc is not in use, so they boot with usb, mine for a while then reboot back to their main OS...

I got the same error on my SSD several times and that's why I switched to a USB drive. I don't have these issues with the same spec rig with 6 1070 GPUs only. Can the number of GPUs affect performance on the MSI Z170A M5? I'll switch back to an SSD and see how it goes.

Dont think so
I have exactly an MSI Z170A M5 with 7x1070 gigabyte, and working with no problems
Have you updated the bios to latest version and set above 4g (mining) in bios?

But I have another mobo z170A carbon or some thing like that, that I can not make 7x1070 cards with it , tested many cpu, and every thing bios
The minute I add 7th, one of the cards wont fully utilize.

[TAKCuCT]

I have 3 rigs on Asrock h110 BTC+ nvidia based (1070 + 1060) on different PSU's and connected to different routers. All of them has very unpleasant problem: once or twice or thrice per day the system hangs and hangs the entire network. This happens only on nvOC, on smos or on ubuntu 16.04 - ok about 2 days. Tried: disable (and remove) dhcp, another router, disable network manager, usb-lan but problem still here. Any thoughts?

[Stubo]

I have 3 rigs on Asrock h110 BTC+ nvidia based (1070 + 1060) on different PSU's and connected to different routers. All of them has very unpleasant problem: once or twice or thrice per day the system hangs and hangs the entire network. This happens only on nvOC, on smos or on ubuntu 16.04 - ok about 2 days. Tried: disable (and remove) dhcp, another router, disable network manager, usb-lan but problem still here. Any thoughts?

You say "the system hangs and hangs the entire network" yet you also say you have 3 rigs. Do you have any idea which system is responsible for a particular "hang"? Also, how do you fix the hang? You also mention disabling usb-lan so how are the rigs connected to the network - wired, wireless, or?

You may want to look for errors/issues in in each rigs /var/log/syslog.

[TAKCuCT]

I have 3 rigs on Asrock h110 BTC+ nvidia based (1070 + 1060) on different PSU's and connected to different routers. All of them has very unpleasant problem: once or twice or thrice per day the system hangs and hangs the entire network. This happens only on nvOC, on smos or on ubuntu 16.04 - ok about 2 days. Tried: disable (and remove) dhcp, another router, disable network manager, usb-lan but problem still here. Any thoughts?

You say "the system hangs and hangs the entire network" yet you also say you have 3 rigs. Do you have any idea which system is responsible for a particular "hang"? Also, how do you fix the hang? You also mention disabling usb-lan so how are the rigs connected to the network - wired, wireless, or?

You may want to look for errors/issues in in each rigs /var/log/syslog.

Rigs are in different places but with the same symptoms. Connected by wire. Hangs only can be fixed by reset button or power switch.

[Stubo]

I have 3 rigs on Asrock h110 BTC+ nvidia based (1070 + 1060) on different PSU's and connected to different routers. All of them has very unpleasant problem: once or twice or thrice per day the system hangs and hangs the entire network. This happens only on nvOC, on smos or on ubuntu 16.04 - ok about 2 days. Tried: disable (and remove) dhcp, another router, disable network manager, usb-lan but problem still here. Any thoughts?

You say "the system hangs and hangs the entire network" yet you also say you have 3 rigs. Do you have any idea which system is responsible for a particular "hang"? Also, how do you fix the hang? You also mention disabling usb-lan so how are the rigs connected to the network - wired, wireless, or?

You may want to look for errors/issues in in each rigs /var/log/syslog.

Rigs are in different places but with the same symptoms. Connected by wire. Hangs only can be fixed by reset button or power switch.

Ok. Thanks for the clarification. What do you see in /var/log/syslog at around the time of the hangs? There should be some clues in there.

[Temporel]

I have 3 rigs on Asrock h110 BTC+ nvidia based (1070 + 1060) on different PSU's and connected to different routers. All of them has very unpleasant problem: once or twice or thrice per day the system hangs and hangs the entire network. This happens only on nvOC, on smos or on ubuntu 16.04 - ok about 2 days. Tried: disable (and remove) dhcp, another router, disable network manager, usb-lan but problem still here. Any thoughts?

I have one of those motherboard on nvOC but with 10 GTX-1070 + 2 GTX-1080 Ti and I never had your problem. Im still on v19 though.
The only downtime I ever had was 2 weeks ago when the Nvidia drivers tried to autoupdate.

Please make sure to report back if you ever find the problem.

TYIA

[kk003]

Just installed this nvoc on one of my rigs, looks good. So questions though (no, I did not read all the pages..):

- Is there a way to limit telegram messages to be sent only when there is something wrong, i.e. reboot of server or miner is needed ?
- My rig has some stability issues, I am mining Ethereum with ethminer. In order to track the GPUs causing problems they would have to be run as separate instances/sessions, (xmos does this by default). Any plans for implementing such feature? If not maybe I try with claymore or plug in xmos USB stick, adjust overclock settings and copy them to nvOC.

--
Tigel

I suggest you to read the notes and comments on /home/m1/kk003_telegram and see if its ok for your needs.
Or you can go here:
https://pastebin.com/vPnb6TKn

and see.

I guess if you leave empty var USER_CUSTOM_TIMES_TO_SEND_TELEGRAM you'll get only warnings (including warnings from IAmNotAJeep_and_Maxximus007_WATCHDOG).

Form:

Code:

USER_CUSTOM_TIMES_TO_SEND_TELEGRAM=("12:00" "18:00" "21:32")

To:

Code:

USER_CUSTOM_TIMES_TO_SEND_TELEGRAM=()

I did not do this check, hope it works for you (I think so).
Let me know if it does not and I'll fix it.

You may too set USER_CUSTOM_TIMES_TO_SEND_TELEGRAM like this:

Code:

USER_CUSTOM_TIMES_TO_SEND_TELEGRAM=("18:00")

to get a telegram once a day at 18:00 (or any other time/s of day you want)

Here is the warnings list (most of them):

Code:

# Some warning you can choose to get via telegram or not 
SEND_WARNING_SYSTEM_RESTARTED="YES" # YES or NO
SEND_WARNING_XORG_RESTARTED="YES"   # YES or NO
SEND_WARNING_LOAD_AVERAGE="YES"     # YES or NO
SEND_WARNING_CHECK_DISPLAY="YES"    # YES or NO
SEND_WARNING_WHEN_NO_L_ON_SCREEN="YES"  # YES or NO     YES send a telegram when screen is not starting miner with -L (create log file)

And some info you may choose to get or not in your telegram msg:

Code:

# some information you can choose to receive or not on your telegram msg
SEND_REBOOT_REQUIRED="YES"      # YES or NO
SEND_WORKERNAME="YES"           # YES or NO
SEND_MINING_COIN="YES"          # YES or NO
SEND_MINING_ADDRESS="YES"       # YES or NO
MASK_MINING_ADDRESS="YES"       # YES or NO
SEND_MINER_EXEC_NAME="YES"      # YES or NO
SEND_MINER_EXEC_PATH="YES"      # YES or NO
SEND_MINER_UP_TIME="YES"        # YES or NO
SEND_PRIVATE_IP="YES"           # YES or NO
SEND_PUBLIC_IP="YES"            # YES or NO
MASK_PUBLIC_IP="NO"             # YES or NO
SEND_SSHD_PORT="YES"            # YES or NO
SEND_UP_SINCE="YES"         # YES or NO
SEND_UP_TIME="YES"          # YES or NO
SEND_RAM="YES"              # YES or NO
SEND_CPU_MODEL="YES"            # YES or NO
SEND_LOGGED_USERS="YES"         # YES or NO
 
CUSTOMIZE_SYSTEM_NAME=""        # "PRIVATE_IP" or "PUBLIC_IP" or "AnY CusTom nAme you want here", if empty it uses the system's hostname
                    # This is the main header you'll get in your telegram message
                    # PRIVATE_IP will use your private ip/s (remenber you may have more than one)
                    # PUBLIC_IP will use your public ip

Warnings auto-clear when system gets back to normal.

I try to read your huge script and i think you're a very experienced scripter. Thank for it.

But i see multiple auto_gram openden when WTM restart 3main at each switching coin. and i get en ps error but i don't know how.
I will post tomorrow in this thread about that

Thx  . I don't have a nvoc 19+ installed. The script was tested on nvoc 19 stable so I don't know yet how to get it working with WMT switch.
If some one have WMT switch working on Nvoc 19 stable and want to share a how to I'll be happy to modify the script.
Post what you have anyway.

Let me know what you need from WTM and I provide it for your telegram
These are the additional info WTM gives:

Code:

BTC Price:: 7111 USD
WTM Current Profitabilty: HUSH:113 % ETH:100 % ZEN:95 % ZEC:94 % 
WTM Current USD Revenue: HUSH:14.82 ETH:13.15 ZEN:12.49 ZEC:12.39 
WTM 24H Average Revenue: 14.8939 USD 

I got it thanks

[Moordact]

forgive me for not looking through whole thread, is BitcoinZ minable?

[Temporel]

forgive me for not looking through whole thread, is BitcoinZ minable?

yes

[papampi]

I have 3 rigs on Asrock h110 BTC+ nvidia based (1070 + 1060) on different PSU's and connected to different routers. All of them has very unpleasant problem: once or twice or thrice per day the system hangs and hangs the entire network. This happens only on nvOC, on smos or on ubuntu 16.04 - ok about 2 days. Tried: disable (and remove) dhcp, another router, disable network manager, usb-lan but problem still here. Any thoughts?

You say "the system hangs and hangs the entire network" yet you also say you have 3 rigs. Do you have any idea which system is responsible for a particular "hang"? Also, how do you fix the hang? You also mention disabling usb-lan so how are the rigs connected to the network - wired, wireless, or?

You may want to look for errors/issues in in each rigs /var/log/syslog.

Rigs are in different places but with the same symptoms. Connected by wire. Hangs only can be fixed by reset button or power switch.

Ok. Thanks for the clarification. What do you see in /var/log/syslog at around the time of the hangs? There should be some clues in there.

Usually when the whole network hangs its a sign of network, mac address or ip conflict.

I had same issue once with my home NAS, when I connect its both lans to switch all my network was freezing.
I couldnt even connect to router, until I found the problem

[Temporel]

I have 3 rigs on Asrock h110 BTC+ nvidia based (1070 + 1060) on different PSU's and connected to different routers. All of them has very unpleasant problem: once or twice or thrice per day the system hangs and hangs the entire network. This happens only on nvOC, on smos or on ubuntu 16.04 - ok about 2 days. Tried: disable (and remove) dhcp, another router, disable network manager, usb-lan but problem still here. Any thoughts?

You say "the system hangs and hangs the entire network" yet you also say you have 3 rigs. Do you have any idea which system is responsible for a particular "hang"? Also, how do you fix the hang? You also mention disabling usb-lan so how are the rigs connected to the network - wired, wireless, or?

You may want to look for errors/issues in in each rigs /var/log/syslog.

Rigs are in different places but with the same symptoms. Connected by wire. Hangs only can be fixed by reset button or power switch.

Ok. Thanks for the clarification. What do you see in /var/log/syslog at around the time of the hangs? There should be some clues in there.

Usually when the whole network hangs its a sign of network, mac address or ip conflict.

I had same issue once with my home NAS, when I connect its both lans to switch all my network was freezing.
I couldnt even connect to router, until I found the problem

and what was the problem ?

[papampi]

I have 3 rigs on Asrock h110 BTC+ nvidia based (1070 + 1060) on different PSU's and connected to different routers. All of them has very unpleasant problem: once or twice or thrice per day the system hangs and hangs the entire network. This happens only on nvOC, on smos or on ubuntu 16.04 - ok about 2 days. Tried: disable (and remove) dhcp, another router, disable network manager, usb-lan but problem still here. Any thoughts?

You say "the system hangs and hangs the entire network" yet you also say you have 3 rigs. Do you have any idea which system is responsible for a particular "hang"? Also, how do you fix the hang? You also mention disabling usb-lan so how are the rigs connected to the network - wired, wireless, or?

You may want to look for errors/issues in in each rigs /var/log/syslog.

Rigs are in different places but with the same symptoms. Connected by wire. Hangs only can be fixed by reset button or power switch.

Ok. Thanks for the clarification. What do you see in /var/log/syslog at around the time of the hangs? There should be some clues in there.

Usually when the whole network hangs its a sign of network, mac address or ip conflict.

I had same issue once with my home NAS, when I connect its both lans to switch all my network was freezing.
I couldnt even connect to router, until I found the problem

and what was the problem ?

Synology updated firmware and after that I can not connect both lan ports to same network any more
5-10 minutes after I connect both my whole network freezes.