FlamongOle

Thanks to @ich777 for the nvidia driver download script for complete driver version support.

This container will no longer be maintained or supported as of 23.07.2021. Fork it, modify it, do whatever with it if you need it. Docker container for Ethereum mining with CUDA (nsfminer) with Nvidia OC capabilities. This Docker container was inspired by the docker-nsfminer which was inspired by docker-ethminer. It uses the nsfminer with OC capabilities with the Nvidia driver. This docker will allow for over- and underclocking of Nvidia GPU's for Ethereum mining in a docker. One docker template per GPU. GitHub project: https://github.com/olehj/docker-nsfminerOC Questions about mining specific questions, workers and wallets will not be answered anymore. There's enough guides and information out there in the sky. Google it, please. Support here is limited to the docker container, where most is answered in this post below: Requirements Unraid 6.9+ NVIDIA drivers for your GPU installed* Docker is set to run in privileged mode, it is required for overclocking and for setting the drivers in persistence mode. GPU with at least 5GB memory or more (current requirement is above 4,2GB). *) Verified working Nvidia driver: v460.73.01 (Production Branch) - v465.X does not allow for overclocks with Unraid/docker combo for unknown reasons. Installation Install this docker container using CA (Community Applications), search for NsfminerOC and install! Configuration Variable Default Value Description ------------------------------------------------------------------------------------------- NSFMINER_GPU 0 Set GPU ID to use (open terminal and check "nvidia-smi") NSFMINER_GPUPOWERLIMIT 150 Set power limit for GPU in Watt (set this as low as you can with highest possible hashrates) NSFMINER_POWERMIZER 2 Set PowerMizer performance level (0=adaptive, 1=max performance, 2=auto) NSFMINER_GPUGFXCLOCKOFFSET 0 Set GPU graphics clock offset (under- or overclock your GPU in MHz offset) NSFMINER_GPUMEMCLOCKOFFSET 0 Set GPU memory clock offset (overclock your memory in MHz, NB! often these values are the double of what they are shown as in Windows so just crank it up!) NSFMINER_HWMON 2 Set Feedback level from nsfminer (feedback from the miner, 0=off, 1=temp+fan, 2=temp+fan+power) NSFMINER_TRANSPORT stratum1+ssl Set transport for worker NSFMINER_ETHADDRESS 0x516eaf4546BBeA271d05A3E883Bd2a11730Ef97b Set your worker ethereum address (or mine an hour or so for me if you wanna support my docker work ;) NSFMINER_WORKERNAME unraid-worker Set a worker name NSFMINER_ADDRESS1 eu1.ethermine.org Set address 1 for worker, both must be set NSFMINER_ADDRESS2 us1.ethermine.org Set address 2 for worker, both must be set NSFMINER_PORT1 5555 Set port for address 1 NSFMINER_PORT2 5555 Set port for address 2 NSFMINER_GPUFANCONTROLL 0 Set GPU fan controll, 0 will run auto and other fan settings are ignored. GPU MUST have exactly 2 fan controllers available, else this container will fail if this is used. NSFMINER_GPUFAN1 0 Set the FAN ID 1 of GPU (check fan ID with "nvidia-settings -q fans" in terminal) NSFMINER_GPUFANSPEED1 100 Set the speed in percent of FAN ID 1 NSFMINER_GPUFAN2 1 Set the FAN ID 2 of GPU (check fan ID with "nvidia-settings -q fans" in terminal) NSFMINER_GPUFANSPEED2 100 Set the speed in percent of FAN ID 2 Running View the logs for worker output Overclocking example Some cards will report that they are read-only when trying to overclock them, such as Quadro cards. This is normal behavior as they are factory locked. For on-demand overclocking, open the "Logs" to check the hashrates when the docker container is running. Then open "Console" to enter in tuning data manually to figure out the optimized mining values for your card. When all values are found, store them in the variables in the docker container edit in Unraid. The GPU ID is set to "0", adjust yours accordingly. The examples below is set for a GTX 1070. Set the PowerMizer mode to 0=adaptive, 1=max performance, 2=auto nvidia-settings -a [gpu:0]/GPUPowerMizerMode=1 Adjust the GPU Graphics clock offset on all performance levels, crank it up until it starts giving errors and then back up. If you are on a 3000-series card, you might want to underclock this one instead and save the power consumption (check example settings for other cards below). nvidia-settings -a [gpu:0]/GPUGraphicsClockOffsetAllPerformanceLevels=200 Adjust the GPU Memory clock offset, crank this one up until it gives errors, crashes or decreases in hashrates, then back it up to a stable value. nvidia-settings -a [gpu:0]/GPUMemoryTransferRateOffsetAllPerformanceLevels=800 Finally, adjust the power limit. Decrease this as much as possible until you hit a target where the hashrates fall. Optimally calculate how much power vs. hashrates you can squeeze out. Sometimes some fine tuning with less or more clocks and power draw can give you better profit. Slightly less hashrates with less power draw might be better profit! nvidia-smi -i 0 -pl 135 Other GPU value examples GPU PowerMizer GPU GFX GPU MEM Power limit Hashrates (~) Effective Score -------------------------------------------------------------------------------------------------- RTX 3080 1 (-300)-(-200) 2300-2500 230-235 97.0-98.5 MH/s 0,421-0,419 * RTX 3070 1 (-600)-(-550) 2300-2400 130-135 60.0-60.2 MH/s 0,462-0,446 * GTX 1070 Stock 1 200 800 135 28 MH/s 0,207 GTX 1070 OC 1 100 400 135 28 MH/s 0,207 Quadro P2000 1 0 0 65 15.6 MH/s 0,24 Some cards might have higher factory clocks in VBIOS like these GTX 1070 GPU's. One of these cards is an OC optimized VBIOS/card, the other one just a standard VBIOS/card with less cooling. The target to reach the hashrates might vary, don't use this table for your own input, this is just an example and might be slightly used for a reference of where it should be. The values might need slight tuning after a while as it might wear out the real top performance of the memory chips, or the ambient temperature simply rises etc. *) The effective score of the RTX 3000 cards shows that it might even be better to run at slightly lower hashrates and power limit, than trying to boost it all up, even with just 5 watts. Fan curves You can also play around with the fan curves, setting it low to reduce the noise can also impact the hashrates. But maybe you want to duplicate your docker container for a "optimized run mode" and a "night mode". Adjusting fan curves might require 2 fan controllers on the graphics card, if the docker container fails and the GPU has only one controller, use "auto" setting (default). Adjust fan controller, 0=auto, 1=manual nvidia-settings -a [gpu:0]/GPUFanControlState=1 Adjust speed for fan 1 (same procedure for fan 2, just replace the number with another fan ID), value in %: nvidia-settings -a [fan:0]/GPUTargetFanSpeed=80 Setting up multiple cards/containers root@Odin:~# nvidia-smi Tue Apr 6 15:06:36 2021 +-----------------------------------------------------------------------------+ | NVIDIA-SMI 460.67 Driver Version: 460.67 CUDA Version: 11.2 | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===============================+======================+======================| ID -> | 0 GeForce GTX 1070 On | 00000000:04:00.0 Off | N/A | | 51% 76C P2 135W / 135W | 4631MiB / 8119MiB | 100% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ ID -> | 1 Quadro P2000 On | 00000000:83:00.0 Off | N/A | | 92% 81C P0 65W / 75W | 4862MiB / 5059MiB | 100% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ ... The output of "nvidia-smi" in the terminal will show you each GPU ID, this ID you enter under NSFMINER_GPU variable. If you have multiple GPU's: Install first the NsfminerOC container via CA. Configure the first NsfminerOC Click "Add container" and select one of your NsfminerOC templates Configure your second container Repeat steps 1-4 for third, fourth etc...

Sorry I don't have so much time for support atm. but create a diagnostic file and attach it here after installing the plugin. Make sure you are using Unraid 6.9.0 or above and not the developer edition (which is not supported at all).

Try to delete the database file, and then reinstall the plugin. Make sure to wait until the plugin installation is done, it might take some time.

That's entirely up to you, but Unraid is rather a continuous beta where versions doesn't really matter

Rather create a common group for the 5*3.5" boxes. 5 columns and 3 rows and own group for the 2.5", guess that's the best you can do for now.

Update 2021.03.03 Commit #161 - FEATURE: Formatting of the comment field has been added, read "Help" for more information under the "Tray Allocations" tab. @shEiD Commit #158 - BUG: NVME drives not detected with Unraid 6.9 because of changes in the output of lsscsi. From now on only Unraid 6.9 and above is supported. Older releases has to use the developer build without nvme support or previous Disk Location version. @Woutch @lovingHDTV

This has been requested earlier, and there's no way I can make a layout that will match all the various builds out there. There's also no focus on removable media as this isn't really any intention of this plugin. In best case I might add some custom labeling on empty slots - someday.

Can probably accept some easy formatting tools there for the future, but I am way too busy these days. So just stay tuned I guess 😛

You do select a group ID as well? It requires both.

It might be related. Anyway, a good place to start is "Force scan all" and if that does't work: delete the database and reinstall the plugin. And -wait- until the plugin says it's installed/done. It may take some time depending on how many drives it needs to check and wake up from standby.

As said before, I do not support alpha/beta/rc versions. Mainly only the current stable (after I bother installing it myself obviously).

That might be it, I'll have a look when Unraid 6.9 is stable

Did you do a "Force Scan All"? Else I see no reason why it shouldn't work.

Use "Purchased date" for that instead if you wanna adjust for warranty by the manufacturer date. Choose whatever makes it useful for you. Where I live, it's irrelevant what the manufacturer date is and what warranty they give as it's overruled by the laws here. Some others has to rely on the manufacturer date, so use that date instead of "purchase date". I won't add more as it will make the plugin itself more untidy 😛

Problem is likely to be with "smartctl" not recognizing the drive. If "Force scan all" doesn't work, then only a new version will. Else not supporting non-stable Unraid releases.

Probably a good idea

check if you have permission to write in that folder, else no idea

Did you install the drives after the plugin? In case try to "Force scan all" to see if they get detected. Else they must be detected via "lsscsi -u -g" command and have SMART data output from "smartctl" command from the device detected by "lsscsi". If it's a new drive, it might need a newer version of smartctl, which comes with a new version of Unraid. Currently only "stable" is supported.

Honestly don't care if you choose to use it or not, but I tried multiple browser in both Linux and Windows and different size settings without getting any results of what you show here. That the devices need to be scrolled to the side when viewing the "Device" tab is simply because it does -not- auto scale and uses fixed pixel size which you can configure yourself. It's not intended to be auto scaled, and it won't be either. The Dashboard is scaled by a set fraction (default divided by 10) of the regular sizes. Make sure to not use any custom CSS or browser extensions that might change the look, or maybe an unofficial Unraid template. I don't know, I use the stock dark theme with everything running default when it comes to looks - and I can't reproduce the misalignment you are seeing here based upon the little information I have for this issue. And so far no one else complains about it, I won't even start debugging it. Of course you are free to delete the plugin, but don't act upon like I loose a customer, because no one has to pay for this and I just use my spare time to share something that I don't even need to do. I just created this for my own purpose, and chose to share it with the community. It's even GNU GPL licensed, so you can fork it yourself and make a better version and share it, so rather do that and STFU, you have the choice.

Check if you don't have any extensions installed that messes up the layout. Haven't heard about this problem before, and I tested here with both Firefox, Chrome and Vivaldi. Try another browser for debugging. The sizes adjust well here for the Device tab, including the dashboard. I'm afraid I don't have a solution for you.

What browser are you using? Not supporting anything else than Chrome and Firefox (and engines used by these). Also only support the latest Unraid stable release with the newest update of Disk Location. The size of the drives can be specified in the configuration, the width and height of the full size per array, and the divider for the small dashboard size(s).

Then the other question is: did you type in the date manually by text? Or did you let the HTML5/web browser enter it for you by clicking the dates? The dates must be stored as ISO YYYY-MM-DD in the unraid variable. If somehow this got typed in manually, the database won't understand the input date.

Next time, attach the screenshots directly to your post. And when using links, format it as such. Copypasta links are annoying. For the problem; did you "Force Scan All" after setting the dates? Do you see the dates under Settings -> Tray Allocations?

As I said, avoid overrides. Create another group instead.