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

Also I have the error "Utilization is too low: restart 1bash" and multiple "Maxximus007_AUTO_TEMPERATURE_CONTROL" tabs. What it's mean? Maybe this is a reason of problem?


I'm trying to change COIN="ZEC" to COIN="ZCL", but I still have 0-50 Sol/s.

I'm using Intenso Ultra Line USB3.0 32GB.

I trying to add 1bash and files again, but result is same.

HDDRawCopy

fullzero, I just installed NvOc and I have a problem. For testing I installed 1 videocard 1080 Ti with Asus Prime Z270-A and connected monitor locally.
Every my attempt I have a error "Utilization is too low: reviving did not work so restarting system in 10 seconds", also EWBF showed 5-59 Sol/s on ZEC. Also user interface is very slow and lagging. In settings I can select only 1 resolution 2560x1440.
I'm use 018v with updated 1bash.
Maybe you have idea how can I fix it?

My apology.
Didn't know that LBRY and LBC same coin
thx for the answer!

Agree, there is no difference.
Developers are advised to make user settings in a separate file.

(I first announced this as an edit to an existing post, but it's probably easier to miss that than a new post.)

I've updated the switcher to accept either an integer or an array of integers for the various overclocking settings.  If you use arrays, you can provide custom settings to each card.

https://gitlab.com/salfter/nvoc-nicehash-switcher/commit/7480fc8c04622277fb638b46c5337c183908d855

The default configuration shows examples of both types.

U can dual ETH / LBRY, the coin name of LBRY is LBC, so just use DUAL_ETH_LBC.
Fullzero and the other primary free worker on this put a lot of work and have a lot to do. Read before ask ...

My apologies; I had done a quick test to see if this would happen: but I realize now I needed to do a test with a standard option windows install; as I have used custom partitions will all the windows installs I have.  

I will add a warning to the OP; and add more logic to 2unix for v0019.

hatch789 is correct in that if you used a standard windows partition set; your primary ( C Drive ) partition is still on that SSD.  



A longer way to recover it with minimal risk ( and also make a backup of the primary partition ) You will need 3 additional SSDs of the same or larger capacity to do this:



Get SSD to be used as the primary partition backup ready:

Attach an already 1st booted nvOC USB key (make sure it is one that has already 1st booted so the same thing doesn't happen twice) and

an SSD that is empty or has data / an install you are willing to delete.

Boot the pc; and press the key for the boot menu, select the nvOC usb and boot

when it starts close the mining process and ensure the watchdog isn't running in the guake terminal (if it is select the tab and press ctrl + c to kill it)

go to the top right ( click Ubuntu button ) and type:

Disks

you should see a Disks application; click it to open

you should see the USB key and the SSD populate in the Disks app

select the SSD (its background should become orange)

at the top right of the application there is an icon with 3 horizontal lines

click this icon

and select Format Disk

set Erase to:  Quick

set Partioning to:  MBR / DOS

and Format the ssd

when it is done: underneath the orange horizontal bar that depicts the disk partitions:

click the

 +

set Erase to:  Quick

set Partitioning to:  NTFS

click Create

when it is done shutdown the computer.





Make an iso Backup of the primary Windows partition:

Attach an already 1st booted nvOC USB key (make sure it is one that has already 1st booted so the same thing doesn't happen twice) and

the SSD that you just got ready and

the original SSD with the affected windows install.

Boot the pc; and press the key for the boot menu, select the nvOC usb and boot

when it starts close the mining process and ensure the watchdog isn't running in the guake terminal (if it is select the tab and press ctrl + c to kill it)

go to the top right ( click Ubuntu button ) and type:

Disks

you should see a Disks application; click it to open

you should see the USB key and two SSDs populated in the Disks app

select the SSD (its background should become orange)

look at its partitions; if there are multiple then it is the affected SSD

if not and you see the single bar; select the other ssd from the list on the left.

select the primary partition: the largest and most likely furtherest to the right (its background should become orange)

underneath the horizontal bar that depicts the disk partitions:

click the

gear

select:

Create Partition Image

enter a title for the partition backup image ( leave the .img extention )

Save in Folder: select the Other SSD we got ready earlier

start imaging / enter password to authorize when prompted.

When imaging is complete power down and remove the affected SSD, the SSD with the created image and the nvOC USB key  ( make sure you mark the SSD with the created image for reference )





Make an new Windows install:

make a new windows install on another SSD which is the same or larger capacity as the one with the lost first partition.

just the initial install (no need to update or anything); ensure the primary partition is same size or larger as the one on the disabled ssd

When this is done, power down the computer





Restore the iso Backup of the primary Windows partition over the new Windows installs Primary partition:

Attach an already 1st booted nvOC USB key (make sure it is one that has already 1st booted so the same thing doesn't happen twice) and

the SSD that you just created the image on

ensure the SSD you just installed Windows on is still attached.

Boot the pc; and press the key for the boot menu, select the nvOC usb and boot

when it starts close the mining process and ensure the watchdog isn't running in the guake terminal (if it is select the tab and press ctrl + c to kill it)

go to the top right ( click Ubuntu button ) and type:

Disks

you should see a Disks application; click it to open

you should see the USB key and two SSDs populated in the Disks app

select the SSD (its background should become orange)

look at its partitions; if there are multiple then it is the affected USB

if not and you see the single bar; select the other ssd from the list on the left.

select the primary partition: the largest and most likely furtherest to the right (its background should become orange)

underneath the horizontal bar that depicts the disk partitions:

click the

gear

select:

Restore Partition Image

Select the Created Image from the other SSD

Click:

Start Restoring

and enter password to authorize when prompted.

When restoration is complete power down and remove the SSD with the created image and the nvOC USB key




Boot the windows SSD and see if it is a working version of your original install.


There are faster ways to do this with less SSDs: this way should minimize errors and be safe.

Thank man I will appreciate this!
Can you also add Lbry for claymore dual mining?

You could try one of these solutions to read/write NTFS works https://www.howtogeek.com/236055/how-to-write-to-ntfs-drives-on-a-mac/ I have Paragon so I can read/write my BootCamp partition.

Why did my hash rate mining ETH on Claymore 9.7 go from 23.5 on Windows 7 down to 18.9 on nvOC?  I have the power set to 94 and the mc set to 825.  Is the latest driver that bad for 1060 cards? I am pretty sure I have the latest driver on Windows.

Does anyone have a problem with SRR?

Not sure what I'm doing wrong but my rig keeps reseting every 2 minutes.

I see SRR option was added to the bash script, does it replace the script that I'm suppose to download from the Simple mining website?

Hi fullzero, I cannot save modified 1bash on Mac because the usb key is formatted as NTFS, do you have a plan to change from NTFS to FAT32 to support Mac?

Does anyone know if there is a way to set temperature target for card instead of powerlimit? I have couple gtx 1060 cards that won't go below 97W when running in nvOC, which is 80% power limit, same thing is in windows no matter which tool I use, but when I use power target in windows and set it to ie.65C the cards power usage goes down to 80W. Unfortunately I wasn't able to find if there is a way to control temp target in linux. Any help would be greatly appreciated.

I always check the temperature of GPUs, but nvidia-smi shows too many useless infoes, so I create an alias, it's very helpful.

output looks like:

0, GeForce GTX 1050 Ti, 70
1, GeForce GTX 1060 6GB, 72
2, GeForce GTX 1050 Ti, 65
3, P106-100, 79
4, GeForce GTX 1060 6GB, 68
5, P106-100, 77
6, P106-100, 78
7, P106-100, 71
8, P106-100, 73

U can go to : https://www.ledgerwallet.com/products/ledger-nano-s is really good to private key never leave the device !

I've not gotten around to it yet, but I have an idea for how to enable per-card, per-algorithm settings.

I've updated the switcher to accept either an integer or an array of integers for the various overclocking settings.  If you use arrays, you can provide custom settings to each card.

https://gitlab.com/salfter/nvoc-nicehash-switcher/commit/7480fc8c04622277fb638b46c5337c183908d855

There is an idea how to more standartize the logs of programs for further processing them in scripts, notifications and monitoring:

I propose to do:

1) Create file  .screenrc in /home/m1 with content:
#
acladd root
multiuser on
logfile flush 1
log on
logfile /tmp/miner.output.tmp
caption always
caption string "%{= RW} $STY | host: %H | For return to terminal press: Ctrl+a d | %m/%d/%y %c:%s | go go to the mooooooon "
#

2) In the 1bash file, replace the line of the
screen -dmS miner $HCD -S $ETH_POOL -O $ETHADDR:x -U
on
/usr/bin/screen -c /home/m1/.screenrc -l -L -dmS miner $HCD -S $ETH_POOL -O $ETHADDR:x -U

For genoil, I use this script:
telegram.sh
#====================
#!/bin/bash

PATH=$PATH:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

/usr/bin/tee /tmp/totalhash.log < /dev/null
/usr/bin/tail -n 1 /tmp/miner.log | awk '{print $2}' >> /tmp/totalhash.log

TOKEN=YOU_TELEGRAM_BOT_TOKEN
TOTALHASH="$(/bin/cat /tmp/totalhash.log)"
TARGET="$(/bin/cat /home/m1/target.log)"

FAN=$(/usr/bin/nvidia-smi --query-gpu=fan.speed --format=csv | awk '{print $1}' | tr '\n' ','|sed -e 's/,/  /g' -e 's/, $/\n/')
WATT=$(/usr/bin/nvidia-smi --query-gpu=power.draw --format=csv | awk '{print $1}' | tr '\n' ','|sed -e 's/,/  /g' -e 's/, $/\n/')
TEMP=$(/usr/bin/nvidia-smi --query-gpu=temperature.gpu --format=csv | awk '{print $1}' | tr '\n' ','|sed -e 's/,/  /g' -e 's/, $/\n/')
UPTIME=$(/usr/bin/uptime -p)
sleep 2

if [[ $TARGET > $TOTALHASH ]]; then
    wget -O /dev/null "http://crierbot.appspot.com/${TOKEN}/send?message=Warning!!!
host $(cat /etc/hostname) too slow hash
ip: $(ifconfig | grep inet | grep -v inet6 | grep -v 127.0.0.1 | cut -d: -f2 | awk '{printf $1}')
$UPTIME
$FAN
$WATT
$TEMP
Total Hash: $TOTALHASH"
    else
        echo > /dev/null
fi

/usr/bin/tee /tmp/miner.log < /dev/null
/usr/bin/tail -n 10 /tmp/miner.output.tmp | grep MH/s | awk '{print $3, $9}' | tr -d MH/s >> /tmp/miner.log
/usr/bin/tee /tmp/miner.output.tmp < /dev/null
#=====================

I created the /home/m1/target.log file and entered the approximate value of HASH for RIG
In crontab, I added the line that is executed every 3 minutes
*/3 *   * * *    m1      /home/m1/telegram.sh

The script compares the value from the /home/m1/target.log file with the value that
the /tmp/totalhash.log receives from the file and if there is a difference, sends me a notification.

I hope that our community optimizes this script and writes more universal, which wil work with all mining programs.

Would this happen to be the problem where all the executables disappear, you can't log back in after logging out, etc.?  I noticed that earlier this week when I gave v18 a shot...something would happen after it had been running an hour or two to where it wouldn't respond to anything but either SysRq-B at the keyboard or a reset or power cycle.  Also, the GPUs appeared to still be under full load, but NiceHash reported no activity.  I still had v17 on its stick, so dropping back to it was no problem.

It is better to add in .bash_aliases