FlamongOle

Update 2021.09.17 Commit #172 - BUG: Javascript MIME type fixed (probably) for the locate script, some might have experienced the problem with Firefox. Commit #171 - SECURITY: Boring security update, fixed some SQL and javascript injection security issues.

You can already change the order, however, not after it is created by a simple click. But it should be fairly simple to just move over devices after adjusting the layouts. I might make it simpler in the future, but nothing I prioritize. If you want to move ex. layout 3 to 1, then copy the layout of the largest one, move the disks, then reduce the other one (if the sizes are different). If they're all the same, it's just a matter of reassigning the devices. Font colors should follow the unraid theme, not messing around with that (at least for now). Choose a better background color

This was the main intention from the start, but I can't find a proper good solution to this yet. "by-path" is fine for most cases (as far as I can see), but it seem to have problems addressing SSD's. I have one SATA SSD and two nVME SSD's it does not add into the path section, and I don't want to mix two different systems for organizing drives in Disk Location. Not sure if this is a kernel issue, never meant to be, or if there's another solution for this altogether. Command below will show devices with paths defined. Even if you would see your SSD's there, it will break many systems and can't be implemented now. ls -l /dev/disk/by-path/ | egrep -v "part|usb"

Update 2021.08.17 FEATURE: Added custom start number offset for trays other than 0 and 1. Also cleaned up the disk information tables a bit.

Update 2021.08.16 BUG: Removed "prettyname" variable as it wasn't allowed with special characters. Might fix issues where some people didn't see "Disk Location" in the menus. I have been busy for quite a while, but this update, thanks to @Squid pointing out the flaw, is probably fixed. Please go ahead and try it out. Thanks!

I haven't tried and likely won't. I'll leave the docker and the page up, but I will end the "support" now due to decreasing popularity in mining and the dockerhub won't build for free automatic anymore.

It sort of says it.. either lower mem clock, or increase power and/or fan speeds and see if that helps.. GPU's are individual, try different values..

Yes, but I'm lazy

Check first page, first post 😛

Don't use that version on the host (if you want to OC), haven't tried 470. The container handles the rest and are setup with default nvidia driver which will likely be replaced regardless - hence the missmatch. Nothing to worry about what's happening inside the container.

No

Front page updated with Nvidia driver version and the clock table with additional information below it.

If it requires additional start up flag, then probably not. If it just requires open ports/port mapping, you can set that up manually yourself in the template setup and check if you can connect to it. I won't be using more time with this docker container unless it stops working.

Ye, had the same experience here. Not so much I can do about it. Maybe there's some conflict with the 465 drivers between docker and unraid even if it's built from the same source, or just a bug. Won't use time to investigate this as it's probably at the near end of the ethereum mining era. Stable 460 drivers work, so I'll write a note about it at the front page. Thanks for the info trhough.

It should auto detect and install correct drivers. Maybe the location it download drivers from are down for maintenance or something. I can't check it now, but it worked for me yesterday.

Nice, decided to fiddle around with your numbers.. and should have done a bit more fiddling earlier.. ended up with these results on the RTX 3070: Power limit: 120W (seems to be the minimum allowed for my card) Clock offset: -550 Memory offset: 2300 Fan: auto Hashrate: 60.2 MH/s - so apparently very effective!

I have a RTX 3070 Gigabyte Gaming OC 8GB, but it sits inside a relatively hot server, so I expect some hashes might be lost just there. But it's important to compare with the same tools, maybe nicehash calculates hasrates differently as well. A fair comparison would be using nsfminer for windows and the one in linux/docker container, and then use nvidia-smi on both windows and linux to determine power usage (maybe also nvidia-smi shows the same clocks as well across platforms?).

This might be related and known: https://www.reddit.com/r/EtherMining/comments/7lfbe0/windows_vs_linux_which_is_more_power_efficient/ What I noticed with my RTX 3080, is that I get way more stales in Windows than in Linux. Windows is about 6-10% stales (always some stales), in Linux 0-1% (mostly no stales). There might be more things into these things which might be hard to answer.

And also, do you use the same tool to check the actual power usage, nvidia-smi? Some 3rd party tools might show different numbers, I dunno.. just a thought.

I have no idea, different drivers perhaps (windows and Linux drivers might behave differently for all i know). I haven't tried it myself, but ensure that the gpu and memory clock is exactly the same (the input is different from windows and Linux drivers)

Might work fine with one GPU, i didn't get any luck by trying to pass through more than one to a VM. Dunno why, but docker worked for me 😛

It should not matter, I have 3 GPU's running without display, the 4th GPU is running VM with mining inside it as I use it for multiple things. The configuration should ignore connected screens and create fake screens. But you can try with one connected, maybe a HDMI-dummy will fix the problem in that case.

Does the GPU run other tasks? Might be that plex blocks it or a VM obviously.

Just try to restart the container. I have it autostarted with some wait time at 10 seconds. Maybe the drivers didn't get loaded or something. Right now your card is likely running without overclocking. If a restart doesn't help, try to reinstall it/force update. Then check in the docker log after startup if the correct nvidia drivers are downloaded and installed (must match the drivers installed in unraid)

Ye, fan IDs increases by number of total fans, not limited per GPU. I did upgrade to 6.9.2 as well. Don't remember if i got the fatal error, but GPU ID might change maybe. Dunno.