mcai3db3

Members
  • Content Count

    56
  • Joined

  • Last visited

Community Reputation

1 Neutral

About mcai3db3

  • Rank
    Newbie

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I mean, whatever you need to do to achieve it would be great. I have zero understanding of the technicalities involved in this, so I would appreciate anything you can conjure up!
  2. Unfortunately you can't do anything other than power limit natively. And nothing in this Docker that allows you to set anything else... currently. @birdwatcher posted above about the NSFMiner Docker having these settings, but I had no joy getting that to work. As far as running the script each time you restart Unraid goes, I just have it run as a script within the 'User Scripts' plugin, and tell it to run every time the server starts up. IMO the best route at the moment to maximize MH/efficiency/temps is to create a Windows VM and host your miner there. But
  3. Run ‘nvidia-smi -pm 1’ first to enable persistence mode. Then run your power limit command as above.
  4. Apologies, I hadn't read the responses when I made my post. I looked at the docker you mentioned, but had several issues attempting to get it to run, due to driver incompatibilities (as you mentioned). Additionally it doesn't appear to want me to use the GPU in my Plex Docker. I think it is also far from ideal to need to install a docker for each card just to configure these settings. I'm still running this PTRFRLL Docker, as it allows me to mine with my Plex card, but for the rest of my cards, in my opinion, it is far more advantageous to run them in a VM a
  5. All you can do in unraid is limit the power with a nvidia-smi command. So 'nvidia-smi -pl xx' where xx is the power percentage. This is why I moved my setup to a Windows VM. For all cards other than the one I use for Plex transcoding.
  6. Thank you for the guide @dboris, I'm about to try this myself. I was wondering what happens if I just load the default NH image rather than opening up the file and tweaking the BTC address. Is there no way to just update this in the OS itself? Apologies for the laziness/naivety, I'm just curious.
  7. Update: I "inspected" the HTML source in Firefox, removed the Regex validation, and got my dockers started without issue. So something is awry with that forms validation... (edit: or I'm doing something that I'm not supposed to be doing?)
  8. I updated to 6.9.0, and now when I go to start Docker (having stopped it to install the Nvidia plugin, ala what SpaceInvader told me to do), all that happens is the Docker vDisk Location field goes red, despite the contents ending in .img "/mnt/cache/Docker/docker4.img". I haven't changed any of the settings. Any ideas? I'm hoping this is a stupid typo, but right now it is immensely frustrating. Edit: to add, I have tried in multiple browsers, same issue. Nothing is logged when I click Apply, as the button is just disabled by this delightful form validation.
  9. I had the same issue. I replaced pretty much all my hardware since, and I haven’t seen the issue since. Idk but maybe it’s a network driver issue or something, all I know is that it annoyed me to the point of spending hundreds of dollars on a new mobo/cpu/ram.
  10. Did you ever work this out? I'm having similar issues and it's obscenely frustrating. I've attached diagnostics, but basically my docker/plugins/main/dashboard pages either time out, or load exceptionally slowly. And several of my dockers are performing terribly too. On 6.8.3. I've tried several things, like reinstalling Unraid files, changing docker image, removing a bunch of plugins/dockers. And no improvement. Aug 9 12:35:45 xxx nginx: 2020/08/09 12:35:45 [error] 17148#17148: *20054 upstream timed out (110: Connection timed out) while reading upstream, client: xxx, se
  11. Consider me a +1 on this one. I can't use the TVHProxy plugin because of the requirement to set IP addresses for each Docker. This would be great.
  12. So basically, does anyone have a suggestion on how to force phaze plugins to wait until the SSD is ready before trying to start up? Is there a way of putting a forced delay in? (I'm not even sure if this'll work, given it could delay UD too). Thanks! Anyone have any suggestions?
  13. This is a crosspost, as I'm not sure if it's an Unassigned Devices issue, or a plugin issue (of which all of my plugins are Phaze plugins), so here goes: http://lime-technology.com/forum/index.php?topic=45807.msg465130#msg465130 So basically, does anyone have a suggestion on how to force phaze plugins to wait until the SSD is ready before trying to start up? Is there a way of putting a forced delay in? (I'm not even sure if this'll work, given it could delay UD too). Thanks!
  14. By plugin's, do you mean Plugins or Docker Applications? If docker Applications, then you have to stop and start the entire docker service in order for any apps to see any mountings that UD performs (6.1.x) If you're under 6.2, then you can modify your volume mountings to use the new "slave" option which should fix this up for you. Just plugins I'm afraid. I've never ventured into the world of Docker.
  15. Howdy all... I'm hoping this is a common issue, or me being stupid somehow, but here goes: My setup is basically that I have 1 "unassigned device" SSD, and on that disk, I install my various plugins (sabnzbd et al.) But I'm having this issue where every single time I restart the server/array, the plugins all run their annoying "wizards" as they are failing to read the config folder held on my SSD. I can see in my logs that the SSD (sdd1) is not mounting until after the plugins have tried to install. So basically, how do I force UD to mount this disk before the plugins try a