Topic: [ mining os ] nvoc - page 130. (Read 418546 times)

have you tried other usb or ssd ?
I think your usb has reached end of its life, get a 30$ SSD and save yourself.

fullzero and the gang - thanks for making this an easy distribution for mining. I have been using v19 for the past few months and have now attempted to move to 19-1.4.

Motherboard is an Asrock H110 BTC.

I've recently flashed v19-1.4 to my sandisk ultra fit usb 3.0 drive and even after numerous attempts I am unable to get it to work. v19 was running fine off it.

On the first boot it ends up with the screen:

BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built in commands.

(initramfs)

---

After which when I reboot, it goes straight to bios.

Tried this on a couple of different usb drives and the results are the same. Is there a specific setting that I'm missing here?

Thanks and advance

The pastebin.com script is already doing this. I have setup unique url for each miner and then edit in browser. Miner updates itself automatic. Or you can force reboot with ssh.

Would it be a bad idea or difficult to enable ftp server on these nvOC machines?

As I get more and more running it seems it would be nice to be able to blast a 1bash file with all my settings to them. None of my machines have monitors or keyboards.

I guess it could be done with scp but that is kind of slow and clunky.

I won't ask :-D

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.

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. ...

Hi Stubo,
You were right. It's the motherboard that gave up. The CPU is perfectly fine. :-)

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.

Yes must be it

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/iY5NL

Do you think is a image problem?

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.

Sometimes some coins make an airdrop to random addresses.

   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

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)

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.

That's right. But it takes time for the watchdog to detect the problem and restart 3main. If you restart the console its instant.

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.

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.

is CTRL-C in the remote screen that bad ?