CHBMB

Community Developer
  • Posts

    10620
  • Joined

  • Last visited

  • Days Won

    45

Everything posted by CHBMB

  1. I haven't done this for a few years, but iirc I hosed everything except my user data and then used occ to scan everything back in after afterwards. Sent from my Mi A1 using Tapatalk
  2. If it were me, I'd first make sure stuff is backed up then try running the full upgrade from the CLI
  3. @levster What version were you on? Because if you were on 15 and trying to upgrade to 17 that would explain the error.
  4. If you're sure you're running the latest version of our container then it must be a sickchill issue as we're building from master and it's up to date. https://github.com/SickChill/SickChill/commits/master https://github.com/linuxserver/docker-sickchill/releases/tag/2c72459d-ls28
  5. This might be helpful..... https://forums.unraid.net/topic/54248-hardware-recommendations-for-unraid-servers-with-vms/?do=findComment&comment=629673
  6. Nextcloud is an exception for technical reasons. Sent from my Mi A1 using Tapatalk
  7. If you read the first post, this is discussed with links. Sent from my Mi A1 using Tapatalk
  8. You haven't mentioned your card. Probably hardware restriction on Nvidias part. Try and include relevant information next time you post and it'll help get a better answer. Sent from my Mi A1 using Tapatalk
  9. Here's the commands to run. Please try this those of you that are seeing the nvidia-smi stuff and let me know if it fixes it, my suspicion is it will.
  10. There probably is, but I don't know how. I still think it's a client side issue tbh.
  11. Yeah, if the plugin is installed but you haven't 1. Downloaded the custom Nvidia build & 2. Rebooted You will see nvidia-smi errors as the plugin parses the installed cards at boot using nvidia-smi then writes that info to a temp file which is then utilised from then on. Problem is, for everyone posting that nvidia-smi error it doesn't really mean anything as all it says to me is "At the time of boot, when nvidia-smi was run, a card wasn't able to be found" That's not to say the card didn't load the kernel drivers later in the boot cycle and would work perfectly regardless I'll put the beast to bed then post a command for people to test the theory. Why this is suddenly an issue, no idea.... Sent from my Mi A1 using Tapatalk
  12. That's very kind of you, thank you. Sent from my Mi A1 using Tapatalk
  13. That's an error with LetsEncrypt, nothing to do with Nextcloud. You're not going to be able to get any further until you sort that out. Suggest you post in the LetsEncrypt support thread, including the above log and with your docker run command (see the docker faq to find out how to get that) and screenshots of your port forwards in your router/firewall.
  14. Thanks for confirming, I'll be interested to see your findings on v6.8.0 final.
  15. So it's working? Sent from my Mi A1 using Tapatalk
  16. Then it may just be nvidia-smi isn't supported. Try to transcode with it anyway. Nvidia-smi is a CLI tool for interacting with the card, not necessary for it's use. Have you used previous versions of the Unraid plugin without issue? Or is this the first time you've tried? Sent from my Mi A1 using Tapatalk
  17. Is the P600 supported by this driver version? Sent from my Mi A1 using Tapatalk
  18. That thread is in reference to the desktop client. libgnome-keyring is a Linux desktop package for the Gnome desktop. So basically nothing related to your problem with Windows clients
  19. Try the terminal, it's more reliable in general.
  20. Docker run command for both is required. You can see how by either turning on signatures in the forum, and the link is in mine, or by reading the docker faq. Sent from my Mi A1 using Tapatalk
  21. You could always submit a pull request to change it.
  22. You're not changing the port in the webui are you? Otherwise as @trurl says, post your docker run command.
  23. Technically you can. 1. Install all the required dependencies. 2. Recompile the Linux kernel including any OOT drivers 3. Install more dependencies, including compiling some Nvidia dependencies from source like Go, which takes an age. 4. Compile the Nvidia drivers, there's a tiny bit of hackery here as there's no desktop environment by default in Unraid so it fails without (iirc it's something to do with the GTK toolkit, I can't remember how I fixed it in the end, I think I removed part of the Slackbuild to skip that bit as we don't need it) 5. Compile the Nvidia docker runtime and libseccomp 6. Change the docker daemon json config 7. Pull apart Unraid to it's component files, install all the bits and bobs then put it back together. Before we made this everyone was asking for the Nvidia drivers, problem is, that doesn't solve the problem of utilising them in the docker containers, actually compiling the drivers and making Slackware packages is the easy bit of the whole thing, problem is if you install at boot time like many other slackware packages you get a kernel panic. (Probably because it's too late in the boot process) In fact, when I started this process, that was the approach I initially took, install everything at boot time. To put it into perspective, we have scripted this whole process and using 24 threads on my server, with 32GB of RAM, it still takes ~ 30-40 minutes to get through the whole thing.
  24. The decision is down to you, but I doubt many of us use s3 sleep so you're probably going to be by yourself figuring it out.....
  25. @Nimrad Don't restart via the webui, restart the docker container via the Unraid interface.