Stubo
Member
Offline
Activity: 224
Merit: 13
|
|
November 23, 2017, 09:50:49 AM |
|
I need help. I imaged 19-1.4 to an SSD but when I boot the 1bash file in /media/ isn't there. And when I edit the one in /home/ with my changes they get overwritten when I launch bash. Otherwise, Ubuntu is booting and running just fine. Thanks!
Unfortunately, the 1bash in /media does not work. What I do with a fresh 19-1.4 image is this sequence of steps: 1) Boot for first time and wait on first reboot. Then you should see that it comes up and starts mining on ZEC (although I don't know for who) on attached display. 2) Fix the issue with hostname being 19_1_4 by editing /etc/hostname (e.g., sudo vim /etc/hostname, change 19_1_4 to m1-desktop). 3) Deploy edited 1bash via WinSCP or edit existing locally to make changes for my coin, pools, etc. Reboot. This is the minimal that I do with new rigs to get them up and running. Hope this helps.
|
|
|
|
|
|
|
|
You get merit points when someone likes your post enough to give you some. And for every 2 merit points you receive, you can send 1 merit point to someone else!
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
Stubo
Member
Offline
Activity: 224
Merit: 13
|
|
November 23, 2017, 10:02:13 AM |
|
Hello, have some newbie questions.
1) Is ZM's miner not working in nv0019-1.3? EWBF works great but every time I attempt to use the dstm it doesn't work. Either it says "this screen is terminating" and then it eventually reboots from low gpu utilization or it says "no miner has been attached to this screen."
2) Is there a way to execute setting changes done in 1bash without rebooting?
Thank you
Regarding 1, as best I recall, there was a problem with ZM in 19.1.3 where either the location or the name of the ZM miner in /home/m1/zec/zm was out of sync with what is being called in 3main. I don't have that version handy or else I would check for you. If you go back several pages in this forum, I am sure it is discussed in detail there. As for 2, the way I do it is to kill the miner screen and wait on the watchdog to see that and kill/restart 3main. However, that can take about as long as rebooting depending upon if you are on USB or SSD. Hope this helps.
|
|
|
|
Rumo
Newbie
Offline
Activity: 41
Merit: 0
|
|
November 23, 2017, 10:33:58 AM |
|
Hello, have some newbie questions.
1) Is ZM's miner not working in nv0019-1.3? EWBF works great but every time I attempt to use the dstm it doesn't work. Either it says "this screen is terminating" and then it eventually reboots from low gpu utilization or it says "no miner has been attached to this screen."
2) Is there a way to execute setting changes done in 1bash without rebooting?
Thank you
Regarding 1, as best I recall, there was a problem with ZM in 19.1.3 where either the location or the name of the ZM miner in /home/m1/zec/zm was out of sync with what is being called in 3main. I don't have that version handy or else I would check for you. If you go back several pages in this forum, I am sure it is discussed in detail there. As for 2, the way I do it is to kill the miner screen and wait on the watchdog to see that and kill/restart 3main. However, that can take about as long as rebooting depending upon if you are on USB or SSD. Hope this helps. I'm not sure if i doing it right but the fastest way i know is just close the console and start a new one. Not the green Guake terminal. The black standard terminal. It kills the miner and restarts mining.
|
|
|
|
papampi
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
November 23, 2017, 03:59:09 PM |
|
Hello, have some newbie questions.
1) Is ZM's miner not working in nv0019-1.3? EWBF works great but every time I attempt to use the dstm it doesn't work. Either it says "this screen is terminating" and then it eventually reboots from low gpu utilization or it says "no miner has been attached to this screen."
2) Is there a way to execute setting changes done in 1bash without rebooting?
Thank you
Regarding 1, as best I recall, there was a problem with ZM in 19.1.3 where either the location or the name of the ZM miner in /home/m1/zec/zm was out of sync with what is being called in 3main. I don't have that version handy or else I would check for you. If you go back several pages in this forum, I am sure it is discussed in detail there. As for 2, the way I do it is to kill the miner screen and wait on the watchdog to see that and kill/restart 3main. However, that can take about as long as rebooting depending upon if you are on USB or SSD. Hope this helps. I'm not sure if i doing it right but the fastest way i know is just close the console and start a new one. Not the green Guake terminal. The black standard terminal. It kills the miner and restarts mining. If local easiest way to restart miner and 3main is what Rumo said, if remote and with ssh: pkill- e screen pkll-f 3main
|
|
|
|
Temporel
|
|
November 23, 2017, 04:07:33 PM |
|
Hello, have some newbie questions.
1) Is ZM's miner not working in nv0019-1.3? EWBF works great but every time I attempt to use the dstm it doesn't work. Either it says "this screen is terminating" and then it eventually reboots from low gpu utilization or it says "no miner has been attached to this screen."
2) Is there a way to execute setting changes done in 1bash without rebooting?
Thank you
Regarding 1, as best I recall, there was a problem with ZM in 19.1.3 where either the location or the name of the ZM miner in /home/m1/zec/zm was out of sync with what is being called in 3main. I don't have that version handy or else I would check for you. If you go back several pages in this forum, I am sure it is discussed in detail there. As for 2, the way I do it is to kill the miner screen and wait on the watchdog to see that and kill/restart 3main. However, that can take about as long as rebooting depending upon if you are on USB or SSD. Hope this helps. I'm not sure if i doing it right but the fastest way i know is just close the console and start a new one. Not the green Guake terminal. The black standard terminal. It kills the miner and restarts mining. If local easiest way to restart miner and 3main is what Rumo said, if remote and with ssh: pkill- e screen pkll-f 3main is CTRL-C in the remote screen that bad ?
|
|
|
|
Rumo
Newbie
Offline
Activity: 41
Merit: 0
|
|
November 23, 2017, 04:29:54 PM |
|
is CTRL-C in the remote screen that bad ?
with CTRL-C you can stop the miner or other scripts but you can not restart 3main or kill the screen as far as i know.
|
|
|
|
Stubo
Member
Offline
Activity: 224
Merit: 13
|
|
November 23, 2017, 06:34:18 PM |
|
is CTRL-C in the remote screen that bad ?
with CTRL-C you can stop the miner or other scripts but you can not restart 3main or kill the screen as far as i know. I do ctrl-C in the miner screen all of the time to restart it. I said kill the miner in my previous post, I just didn't say how. Either way, the watchdog detects low utilization and restarts 3main eventually.
|
|
|
|
Rumo
Newbie
Offline
Activity: 41
Merit: 0
|
|
November 23, 2017, 06:47:07 PM |
|
is CTRL-C in the remote screen that bad ?
with CTRL-C you can stop the miner or other scripts but you can not restart 3main or kill the screen as far as i know. I do ctrl-C in the miner screen all of the time to restart it. I said kill the miner in my previous post, I just didn't say how. Either way, the watchdog detects low utilization and restarts 3main eventually. That's right. But it takes time for the watchdog to detect the problem and restart 3main. If you restart the console its instant.
|
|
|
|
sikke1
Jr. Member
Offline
Activity: 44
Merit: 18
|
|
November 23, 2017, 07:46:40 PM |
|
Thanks for great miner ********************* ZM 0.5.4 in nvOC 13x Asus Strix 1070 The rig is with AsRock H110 PRO BTC+ & Intel Pentim G4400 & 4GB RAM Pulling 2080W from wall. With 2x 1200W ATX PSU OS with 16GB class6 microSD card in USB adapter <--- some might say unrealiable but I have them plenty and ready provisioned for swap if fail. Done +2months no fail. ********************** Fans at 50% ZEC POWERLIMIT_WATTS=140 __CORE_OVERCLOCK=80 MEMORY_OVERCLOCK=1000 ********************** GPU0 57C Sol/s: 464.9 Sol/W: 3.36 Avg: 468.4 I/s: 250.1 Sh/s: 0.043 + GPU1 55C Sol/s: 470.0 Sol/W: 3.38 Avg: 471.6 I/s: 251.5 Sh/s: 0.014 GPU2 63C Sol/s: 462.5 Sol/W: 3.33 Avg: 464.8 I/s: 246.8 Sh/s: 0.000 GPU3 63C Sol/s: 468.4 Sol/W: 3.32 Avg: 464.3 I/s: 246.7 Sh/s: 0.029 GPU4 58C Sol/s: 457.9 Sol/W: 3.35 Avg: 466.9 I/s: 249.4 Sh/s: 0.014 GPU5 53C Sol/s: 460.0 Sol/W: 3.30 Avg: 460.9 I/s: 247.7 Sh/s: 0.014 GPU6 57C Sol/s: 463.2 Sol/W: 3.31 Avg: 462.3 I/s: 248.2 Sh/s: 0.014 GPU7 51C Sol/s: 469.5 Sol/W: 3.35 Avg: 467.1 I/s: 249.1 Sh/s: 0.057 GPU8 47C Sol/s: 474.4 Sol/W: 3.43 Avg: 478.1 I/s: 254.1 Sh/s: 0.014 GPU9 63C Sol/s: 465.1 Sol/W: 3.30 Avg: 460.4 I/s: 245.4 Sh/s: 0.014 GPU10 63C Sol/s: 451.8 Sol/W: 3.26 Avg: 454.5 I/s: 244.7 Sh/s: 0.071 + GPU11 56C Sol/s: 461.3 Sol/W: 3.34 Avg: 465.7 I/s: 249.0 Sh/s: 0.029 + GPU12 53C Sol/s: 478.5 Sol/W: 3.37 Avg: 470.5 I/s: 251.5 Sh/s: 0.014 ========= Sol/s: 6047.6 Sol/W: 3.34 Avg: 6055.5 I/s: 3234.3 Sh/s: 0.329 If I drop the powerlimit to 130W I get aroud 3.7 Sol/W ~5800sols with same OC settings, but I like 6000 sol more round number. ********************** ZM 0.5.4 in nvOC 4x Asus Strix A 1070 TI POWERLIMIT_WATTS=130 __CORE_OVERCLOCK=120 MEMORY_OVERCLOCK=1200 GPU0 62C Sol/s: 501.2 Sol/W: 3.92 Avg: 508.6 I/s: 270.8 Sh/s: 0.030 GPU1 58C Sol/s: 503.2 Sol/W: 3.95 Avg: 511.4 I/s: 272.8 Sh/s: 0.090 + GPU2 56C Sol/s: 508.3 Sol/W: 3.93 Avg: 509.5 I/s: 272.3 Sh/s: 0.050 + GPU3 53C Sol/s: 505.1 Sol/W: 3.93 Avg: 509.5 I/s: 271.6 Sh/s: 0.040 ========= Sol/s: 2017.8 Sol/W: 3.93 Avg: 2039.0 I/s: 1087.4 Sh/s: 0.210 The Asus "binned" TI GPU stand more OC and hashes ok with 130W too. Will make 13x TI rig next. Same powerdraw more sols per W. Should be ~6600 sols with 2kw.
|
|
|
|
Temporel
|
|
November 23, 2017, 10:27:57 PM |
|
is CTRL-C in the remote screen that bad ?
with CTRL-C you can stop the miner or other scripts but you can not restart 3main or kill the screen as far as i know. I do the changes in 1bash and then I use CTRL-C in "screen -r miner" instead of rebooting the rig. Same thing if I edit 3main. I never had a single problem doing this (using v19)
|
|
|
|
thaelin
Newbie
Offline
Activity: 64
Merit: 0
|
|
November 24, 2017, 07:10:08 AM |
|
While running a check on my ETH payouts on EtherScan today , I noticed that a transfer from someone of a token for ZENON worth 79.00 was sent. I have no idea of what this is or why. Can someone enlighten me on what it means? I am just mining coins and happy at that. Not really into the buying and selling end.
thanks thay
|
|
|
|
Godm0de
Newbie
Offline
Activity: 12
Merit: 0
|
|
November 24, 2017, 08:12:14 AM |
|
While running a check on my ETH payouts on EtherScan today , I noticed that a transfer from someone of a token for ZENON worth 79.00 was sent. I have no idea of what this is or why. Can someone enlighten me on what it means? I am just mining coins and happy at that. Not really into the buying and selling end.
thanks thay
Sometimes some coins make an airdrop to random addresses.
|
|
|
|
WaveFront
Member
Offline
Activity: 126
Merit: 10
|
|
November 24, 2017, 09:59:49 AM Last edit: November 24, 2017, 11:25:23 AM by WaveFront |
|
Quick question. Which processor do you install in your rigs? I use the i3 7100T (2 cores 3.4 Ghz), but I think it's overkill since the CPU load is always below 20% Originally I wanted to have a margin of manoeuvring in case I change configuration or if I decide to turn the rigs into standard servers.
|
|
|
|
Zucca
Newbie
Offline
Activity: 79
Merit: 0
|
|
November 24, 2017, 12:02:24 PM |
|
I tried the default 1bash in 19-1.4 and seemed fine, I changed for ETH and enabled teamviewer, then this happend: https://imgur.com/a/iY5NLDo you think is a image problem?
|
|
|
|
siikfo
|
|
November 24, 2017, 12:16:04 PM |
|
I tried the default 1bash in 19-1.4 and seemed fine, I changed for ETH and enabled teamviewer, then this happend: https://imgur.com/a/iY5NLDo you think is a image problem? Yes must be it
|
|
|
|
WaveFront
Member
Offline
Activity: 126
Merit: 10
|
|
November 24, 2017, 12:40:10 PM |
|
Whats the deal? I have this issue with every rig thats more than 3 cards on nvOC
gigabyte 270 d3 mobo g4400 or g4400t cpu ddr4 4 gb ram risers 6x 1080 TI dual psu
I have had this problem on 4 6 card builds and a 12 card with the h110 . .smOS works perfect on the same rigs
Screen resolution is messed up and mining never begins
Hi VoskCoin, This is strange, as I have nvOC v0019-1.4 running on a h110 mobo with 12 GTX1060 flawlessly. Your monitor output should be connected to the GPU on the main PCIe x16 slot (the larger one). Did you edit the 3main file? Must be nice T_T No just the 1bash Are you editing your 1bash on your PC or on the actual rig? Both. I edit 1bash most of the time through an ssh connection with the nano editor. Occasionally I edit 1bash with gedit if I am in front of the rig (in the unlikely occasion if a monitor/keyboard/mouse are connected to the rig) or connected with TeamViewer.
|
|
|
|
WaveFront
Member
Offline
Activity: 126
Merit: 10
|
|
November 24, 2017, 12:41:59 PM |
|
One of my rigs just failed. I suspect it was one of the cables that got stuck into the CPU fan. Motherboard and processor seem completely dead. I checked the PSU with the paper clip method and it looks like it is working. If it was really a cable that blocked the CPU fan, is the CPU unrecoverable? (I was convinced that most processors had a protection mechanism of some sort) I have never seen a hot CPU die. Typically, it just crashes and restarts. What you did is not much different that trying to OC a CPU beyond its thermal limits and I never killed one that way. If you haven't already, start with the basics - mobo with only power and front panel connectors - no cards in slots or other cables and troubleshoot from there. Hope this helps. Hi Stubo, You were right. It's the motherboard that gave up. The CPU is perfectly fine. :-)
|
|
|
|
dartec
Newbie
Offline
Activity: 24
Merit: 0
|
|
November 24, 2017, 07:56:08 PM |
|
is CTRL-C in the remote screen that bad ?
with CTRL-C you can stop the miner or other scripts but you can not restart 3main or kill the screen as far as i know. I do the changes in 1bash and then I use CTRL-C in "screen -r miner" instead of rebooting the rig. Same thing if I edit 3main. I never had a single problem doing this (using v19) The way that I restart the miner after a config change is the following: Ssh into the rig run the command "pkill -e miner" (without the quotes). This kills the mining process/es. Watchdog will pick up that utilization is low and restart the miner automatically. Works just fine for me. ...
|
|
|
|
Stubo
Member
Offline
Activity: 224
Merit: 13
|
|
November 24, 2017, 09:53:28 PM |
|
One of my rigs just failed. I suspect it was one of the cables that got stuck into the CPU fan. Motherboard and processor seem completely dead. I checked the PSU with the paper clip method and it looks like it is working. If it was really a cable that blocked the CPU fan, is the CPU unrecoverable? (I was convinced that most processors had a protection mechanism of some sort) I have never seen a hot CPU die. Typically, it just crashes and restarts. What you did is not much different that trying to OC a CPU beyond its thermal limits and I never killed one that way. If you haven't already, start with the basics - mobo with only power and front panel connectors - no cards in slots or other cables and troubleshoot from there. Hope this helps. Hi Stubo, You were right. It's the motherboard that gave up. The CPU is perfectly fine. :-) Good to know. I have never seen a mobo fail from CPU heat but I have fried my fair share of them doing other stupid things. <- Don't Ask.
|
|
|
|
WaveFront
Member
Offline
Activity: 126
Merit: 10
|
|
November 24, 2017, 10:58:45 PM |
|
One of my rigs just failed. I suspect it was one of the cables that got stuck into the CPU fan. Motherboard and processor seem completely dead. I checked the PSU with the paper clip method and it looks like it is working. If it was really a cable that blocked the CPU fan, is the CPU unrecoverable? (I was convinced that most processors had a protection mechanism of some sort) I have never seen a hot CPU die. Typically, it just crashes and restarts. What you did is not much different that trying to OC a CPU beyond its thermal limits and I never killed one that way. If you haven't already, start with the basics - mobo with only power and front panel connectors - no cards in slots or other cables and troubleshoot from there. Hope this helps. Hi Stubo, You were right. It's the motherboard that gave up. The CPU is perfectly fine. :-) Good to know. I have never seen a mobo fail from CPU heat but I have fried my fair share of them doing other stupid things. <- Don't Ask. I won't ask :-D
|
|
|
|
|