Quote from: dbolivar on September 12, 2017, 05:00:13 AM

Quote from: dbolivar on September 12, 2017, 04:52:02 AM

Quote from: VoskCoin on September 12, 2017, 04:22:02 AM

Quote from: dbolivar on September 12, 2017, 04:17:29 AM

Quote from: VoskCoin on September 12, 2017, 03:48:38 AM

How can I edit nvOC and then use that as my nvOC baseline --- so I can flash it onto X hard drives and all I have to change is the worker name ?

After setting up the baseline nvOC installation, you could simply create a new image of the partitions (or entire disk), and use it to flash new disks. For that, you would need to boot from a different drive, as the disk you're going to image shouldn't be mounted. I personally like GParted Live and PartedMagic, as they are loaded with several utilities for that, but you could just use the "dd" utility that comes with every modern Linux basic installation.

So: boot GParted Live from USB stick; have the disk you are going to create the image from ready; have a disk where to save the image file ready; use a partition/disk cloning utility (or "dd") to create the image; use that image to flash new disks. Note that depending on your hard drive sizes, ideally you should create images with only the used space (some utilities allow that), as it doesn't make much sense to create a (say) 250 GB image with only 10 GB used.

Finally, I don't think you'd need to change anything on the newly-flashed nvOC disks, as it automatically adjusts the worker name based on the IP address (but of course you can), and the Xorg reconfiguration should be done automatically too.

previously the worker name did not work properly for me when it was set on the auto adjust setting, did anyone else have that problem and could that have been a conflict with my router/switch?

thank you for the quick reply, is it possible to do this on windows?

Is there any benefit to periodically putting a freshly flashed USB in as opposed to one thats been mining for months?

For Windows the process would be similar: let's say you have your notebook with Win10. Plug the source drive in one USB port, the destination drive in another USB port, and run a disk cloning utility. That same disk cloning utility should allow you to create an image file to save on your notebook itself, to flash future drives. Check this website for some disk cloning utilities for Windows:

http://lifehacker.com/5839753/the-best-disk-cloning-app-for-windows

Now for your other questions:

1) Never had this kind of problem. My setup uses DHCP but with static IP assignments configured in my router, so there's a consistent hostname.

2) You PMed me with this question, but I'll reply here for others: if I understood, you wanted to know if it's possible to clone the nvOC installation before booting it at least once. I don't think it's a good idea, as there's that process to copy 1bash between partitions, adjusting them etc. (not sure if it still applies to v019). So just to be sure, boot it once, make sure it's mining correctly, then shutdown, and clone this installation.

3) I don't think you need to replace your USB drives unless they are giving read/write errors. After flashing and setting up everything, there aren't many disk writes that could wear out the drive, as far as I know.

Or... just occured me: if you are sure your 1bash settings are correct and you don't need to change anything else, simply copy this file over to your next installations.

You will need to flash the nvOC img file anyways, would take about the same amount of time as cloning.

This whole process I mentioned is worth it only if you customize other things after booting nvOC, not just 1bash.

I figured if someone is editing more than 1bash; they already know how to make their own custom image (easiest way to do this for less experienced members is to use HDDrawCOPY)

Making a pastebin account then a paste with your configured 1bash will allow you to push updates to all your rigs by only editing the paste. This is the easiest method to configure multiple rigs with the same GPUs. Ensure:

Code:

GLOBAL_WORKERNAME="YES"

AUTO_WORKERNAME="HOST"

or

AUTO_WORKERNAME="MAC"

Code:

_Parallax_MODE="YES" # YES NO

pasteBASH="uZNXXJuE" ##ENSURE you change to the last section of your paste's url see the _Parallax_MODE guide link on the OP

upPASTE_TIMEOUT_IN_MINUTES=30

then your rigs will name themselves by host address or mac address ( I use a labelmaker to label all my rigs so I know which is which)
and check for changes to your paste every 30 minutes. If you make a change to the paste, it will update the 1bash on each rig with pasteBASH set to the paste.

As different GPUs have different OC settings; I use a different paste for each GPU type. If you have over 5 rigs this will save you so much time and effort.