Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

ich777

Community Developer
  • Joined

Everything posted by ich777

  1. Nope, that's not how it works and that wouldn't work because when the driver is installed (really early in boot) your cache driver is not even close from being mounted. Transfering licenses is really easy, buy a new USB Flash devices (something reliable, I always recommend Transcend 32GB USB 2.0 Flash devices - please don't buy a USB 3.0 or even 3.1), Format it as FAT32, give it the Label: UNRAID, COPY everything from your old flash device to your new device (with that you still have your old flash devices if something goes wrong), execute make_bootable.bat as Administrator, boot from your new flash device, Unraid will say that there is an issue with your license on the top right corner, go to Tools -> Registration, there you should be able to transfer the license, after that you can start the Array, or even better download the Nvidia driver and reboot to be safe that everything is working.
  2. It seems you ran out of space on your boot device: /dev/sda1 1.9G 1.7G 233M 88% /boot From what I see your USB Boot device is only about 2GB, please consider a new USB Boot device if possible. The driver needs between 300 and 450MB of free space on your Boot Device and 233MB is simply too less. If you want to fix that, you can delete the folder /boot/previous which contains the last Unraid version which most likely is exactly what you need.
  3. Please upgrade to 7.2.4, otherwise you won't get a newer driver.
  4. Yes, exactly. However I need always your Diagnostics, I can't tell what's going on on your system without them.
  5. My I ask why? You have to delete the steamapps folder inside your palworld directory not the steamcmd folder, but of course first stop the container, then start it again and it should pull the update.
  6. Do you have any logs? What update? Did the game had an update? Did you try to restart the container and see if it pulled the update too in the log?
  7. Can you please specify what "older" version you need? But in general no. Sorry, but I don't think that this is the culprit from the issue and why should the new driver shouldn't support compute? Can you please first show your docker run commands for the containers? With which containers do you you have trouble?
  8. If you are searching something cheap then please look maybe for a Nvidia T400/T600/T1000, you could also get away with a Intel Arc Card even an A380 will do the job just fine and the A380 is also capable of transcoding AV1, as long as the software you are using is capable of transcoding AV1, with the benefit of not having to install a driver. However the idle power draw is a bit higher in idle with the Intel card from what I know.
  9. May I ask for what do you use the card actually? And yes, currently the old legacy driver doesn't compile against recent Kernels which all currently available Unraid versions are using. However there is a patch out there for the old legacy driver to make them work again, however I already tested that and I'm pretty certain you don't want to crash your server often correct? These patches make the driver work but the server becomes completely unstable. Sorry but the blame goes to Nvidia since they now deprecated these cards.
  10. Aloft is Windows only and AFAIK only ships with the game itself so it would be really hard to create a game server for that specific game.
  11. Yes, because the container downloads the game files on first start, that's pretty normal. I still support the container but time is very limited. So to speak this will take some time. However most of the times it should be enough to manage the server through the game or at least for now you have to do it that way since if you add your SteamID as the server owner you can do that when joining the game.
  12. Update for the dedicated server. No, the container tries to open the console when you click on WebUI, however have you tried to enter commands in the console form the screenshot above. Maybe it works however, it was working back when I added that feature but over here I can't even get the container to work properly anymore.
  13. Is this the Log or the WebUI? If it doesn't work anymore I can't do anything since they broke a lot in one of the last updates and since this is running through WINE this complicates things further.
  14. Sure, click on the container icon and select WebUI. This should be also be mentioned in the Description from the container if I'm not mistaken.
  15. Sorry, I missed your message, however it seems your card is bound to VFIO, please unbind it an reboot: Feb 13 17:00:16 Tower kernel: NVRM: GPU 0000:03:00.0 is already bound to vfio-pci. Feb 13 17:00:16 Tower kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s). Feb 13 17:00:16 Tower kernel: NVRM: This can occur when another driver was loaded and Feb 13 17:00:16 Tower kernel: NVRM: obtained ownership of the NVIDIA device(s). Feb 13 17:00:16 Tower kernel: NVRM: Try unloading the conflicting kernel module (and/or Feb 13 17:00:16 Tower kernel: NVRM: reconfigure your kernel without the conflicting Feb 13 17:00:16 Tower kernel: NVRM: driver(s)), then try loading the NVIDIA kernel module Feb 13 17:00:16 Tower kernel: NVRM: again. Feb 13 17:00:16 Tower kernel: NVRM: No NVIDIA devices probed. Feb 13 17:00:16 Tower kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 239
  16. Most of the times it is simply enough to Uninstall the GPU Statistics plugin or set the query interval to something reasonable like 5000ms or even 10000ms. Please go also yourself through your syslog, it seems you have a massive issue with the UPS plugin too.
  17. Sorry, not from my side. However isn't TS3 fully compatible with TS6, at least for voice, chat is saved on their servers IIRC or did that change?
  18. You can already do that but that is pretty manual. Create the Container as usual, move the rootfs folder from this container wherever you want (obviously the container should be stopped), the config file must remain in place where it is and point the rootfs path in the config file to wherever the rootfs is located afterwards, but please keep the backing filesystem in mind that it should match or you have to manually change it.
  19. Sorry, but this has nothing to do with the Nvidia Driver since if you are using it in a VM it is actually discouraged to install the Nvidia Driver Plugin (also see the first page).
  20. Please post your Diagnostics after your GPU is "forgotten".
  21. I think your issue is that you have to use lower case: -modifier raids less -modifier portals casual -modifier resources muchmore -modifier deathpenalty veryeasy -modifier combat easy and this goes in your GAME_PARAMS
  22. Yes, this was the download on boot, maybe you had no GitHub Tokens left or some kind of network issue occurred when doing the update. Glad to hear that it works. :)
  23. Please try to reboot, the plugin should try to download the driver on boot too. However the driver for 7.2.3 should be available, maybe there is some issue on your network, please check if you are maybe blocking access to the GitHub API. If the plugin doesn't work after the reboot, please try to uninstall the plugin, rebooting and installing the plugin again.
  24. This is a common issue with steamcmd: Stop the container Delete the steamapps folder in the game directory Start the container After that steamcmd should pull the update.
  25. Yes, Terraria pulls the files directly from terraria.org Does the update not work? I think the latest version is 1.4.5.4 Have you yet tried this version?

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.