Jump to content

ich777

Community Developer
  • Posts

    15,758
  • Joined

  • Days Won

    202

Everything posted by ich777

  1. What router do you have? I know that the Fritzbox can‘t handle that but what Router do you have? Anyways in my oppinion it is better to avoid crashes instead of having traces… For what applicaiton(s) do you need static IP address(es)?
  2. I really can‘t tell whats the issue here, I‘ve now gone through the code and nothing should it prevent from working and the Kernel was only update from 6.1.36 (unRAID 6.12.2) to 6.1.38 (unRAID 6.12.3) which shouldn‘t affect anythig so I‘m not sure what‘s causing this on your system. Sadly enough I have no hardware on hand so that I could try it and reproduce the error. Maybe someone else is posting here too then it is worth creating an issue over here in the repository where my plugin is based of: Click
  3. Please uninstall GVT-g since it seems like you aren't using it and see if this makes a difference. Can you also post your docker run command from Plex? I have a i5-10600 here and everything is running smoothly with Emby and Jellyfin everything on ZFS but without snapshots. I see a lot of this messages in your syslog, are you sure that this is correct: Jul 15 16:07:04 Thor pulseway: Periodically collected data not ready yet for Types::Reporting::Data::CoreReportData Jul 15 16:07:04 Thor pulseway: No data for module 1 Jul 15 16:07:04 Thor pulseway: Periodically collected data not ready yet for Types::Reporting::Data::NetworksUsageData Jul 15 16:07:04 Thor pulseway: No data for module 3 Jul 15 16:07:04 Thor pulseway: Failed to get package list Jul 15 16:07:04 Thor pulseway: No data for module 6 Jul 15 16:12:20 Thor pulseway: Periodically collected data not ready yet for Types::Reporting::Data::CoreReportData Jul 15 16:12:20 Thor pulseway: No data for module 1 Jul 15 16:12:20 Thor pulseway: Periodically collected data not ready yet for Types::Reporting::Data::NetworksUsageData Jul 15 16:12:20 Thor pulseway: No data for module 3 Jul 15 16:12:20 Thor pulseway: Failed to get package list Jul 15 16:12:20 Thor pulseway: No data for module 6 Jul 15 16:17:37 Thor pulseway: Periodically collected data not ready yet for Types::Reporting::Data::CoreReportData Jul 15 16:17:37 Thor pulseway: No data for module 1 Jul 15 16:17:37 Thor pulseway: Periodically collected data not ready yet for Types::Reporting::Data::NetworksUsageData Jul 15 16:17:37 Thor pulseway: No data for module 3 Jul 15 16:17:37 Thor pulseway: Failed to get package list Jul 15 16:17:37 Thor pulseway: No data for module 6 Jul 15 16:22:53 Thor pulseway: Periodically collected data not ready yet for Types::Reporting::Data::CoreReportData Jul 15 16:22:53 Thor pulseway: No data for module 1 Jul 15 16:22:53 Thor pulseway: Periodically collected data not ready yet for Types::Reporting::Data::NetworksUsageData Jul 15 16:22:53 Thor pulseway: No data for module 3 I also see these lines in your go file: #Hardware video Transcode Enable and TMP File System modprobe i915 ***line removed*** #chmod -R 777 /dev/dri mkdir /tmp/PlexRamScratch chmod -R 777 /tmp/PlexRamScratch mount -t tmpfs -o size=32g tmpfs /tmp/PlexRamScratch Can you try to not use a tmpfs for Plex and transcode somewhere on a hard disk, maybe a spinning one? You also don't have to do the modprobe because unRAID is doing that for you and even if it wouldn't then Intel-GPU-TOP would do that for you. May I also ask why are you doing that: mount -o remount,size=1024m /var/log/ It seems that you have a lot customized maybe start pulling back a bit at least in terms of Plex and see if it does if you run it bare bones with the default transcoding directory and so on. EDIT: Please also consider upgrading the BIOS, the BIOS that you are running (Version: 0811) is the first one that was released for this Motherboard, the newest version is: 1801
  4. Are you sure that your power supply is still okay? Had a few users recently on the German sub forums where their BeQuiet power supplies caused the same thing on them and it took a long time to diagnose that.
  5. Can you be a bit more precise? Why do you think it is causing "hard reboots" what do you mean exactly with "hard reboots"? Please upload your Diagnostics? I just looked up the downloads for the plugin package for 6.12.3 and it was downloaded exactly 230 times, I think someone else would have reported that too if the plugin causes this.
  6. It seems that he just built it and it should be now safe to install the plugin again. 😉
  7. Please install the correct plugin, you need the RTL8125 plugin for your network card since it's a RTL8125 chip from what I see in your Diagnostics: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) Subsystem: Gigabyte Technology Co., Ltd RTL8125 2.5GbE Controller [1458:e000] Kernel driver in use: r8169 Kernel modules: r8169 However if you install this driver it can be the case that your server has a different IP afterwards because you are basically using a new driver. I've gone a bit more in depth into your Diagnostics and also saw that you have the GVT-g plugin installed, please remove it since it wont do anything for you because GVT-g is only supported up to 10th Gen Intel i-Core series CPUs. Wenn du Support auf Deutsch willst/brauchst, kannst du gerne einen Post im Deutschen Subforum machen und mich mit @ + meinem Usernamen markieren (nicht vergessen auch auf meinen Usernamen zu klicken). Bitte auch hier auf den Ton achten im Forum. Hoffe das hilft...
  8. Uninstall the SR-IOV plugin and reboot, the maintainer has not uploaded new packages which are required for 6.12.3 You can also go back to 6.12.2 and install the SR-IOV plugin again if you really need it and wait until the maintainer uploads the updated plugin packages so you can upgrade to 6.12.3 Something is also wrong with your modprobe.d files, you have a i915.conf and a i915.conf.conf where one is set up wrong: options i915 force_probe=4c8b options i915 enable_guc=2blacklist i915 Please also switch from MACVLAN to IPVLAN in your Docker settings, you have to stop the Docker service to change that setting.
  9. Yes, but I can't do anything about it since @zhtengw compiles the driver package on it's own and you have to wait for him to compile them. I contacted him back when he created the plugin if I should integrate the package build into my build toolchain but he doesn't wanted that and I'm also fine with that. I already saw you post here: For now you only can go back to 6.12.2 and wait until he compiled the drivers so that his plugin will work again.
  10. Why don‘t you use the official support thread for my container (click on the container icon on the Docker page and select Support)? Why do you need a MariaDB in the first place? You have to understand that 127.0.0.1 is localhost and you are dealing with two different containers. You have to use the real IP address from the MariaDB so that my container can connect to it since in my container there is no MariaDB installed and you have to connect it. I‘ll lock this topic now since you should really use the support thread from the container.
  11. All is workig fine over here. 👏😉😊
  12. Try to reboot, it should be safe anyways, the Nvidia Driver plugin should pull the update on a reboot anyways. Something really strange is going on on your system... Are you sure that you have enough free space on your USB Boot device? Can you post your Diagnostics? However it should be save to reboot but if possible pull the Diagnostics before the reboot. EDIT: I have now downgraded my test server to 6.11.5 to try it on my test server and everything is working as expected, I can only assume that you have to less free space on your USB Boot device:
  13. There is something really strange going on on your system, do you use any AdBlocking on your network, does the server have full access to the Internet and are you sure that you don't block access to the GitHub API? Please post the output from both commands from a Unraid Terminal: pcregrep -oM 'Linux kernel[\s\S]*?version\s+\K\d+(\.\d+)+' /boot/changes.txt | sort -V | tail -1 wget -qO- https://api.github.com/repos/ich777/unraid-nvidia-driver/releases/tags/6.1.38-Unraid | jq -r '.assets[].name' | grep -E -v '\.md5$' | grep "nvidia" | sort -V | tail -1
  14. Yes, if it did take about 20 seconds+ you should be now good to go to reboot. Check your notifications in Unraid, it should have populated them.
  15. You've had a old version from the Plugin-Update-Helper (which ships with third party plugins) installed which caused this message, this is now fixed if you have already rebooted.
  16. @serhan please open a Unraid terminal copy/paste this command and follow the instructions: wget -qO- https://raw.githubusercontent.com/ich777/unraid-plugin_update_helper/master/force_package_update | bash (please make sure that the Nvidia Driver plugin is still installed)
  17. Please give ma about 5 minutes, I'll post a command shortly that you have to execute from a Unraid Terminal that will ensure that the packages are download properly for the new Unraid version.
  18. Oh sorry, I could have been also a bit more precise, I've meant from which Unraid version are you trying to upgrade?
  19. From what version where you trying to upgrade?
  20. I don‘t think so since this is another product since you have to pay for it monthly or annually. What are the benefits from Pro compared to the Opensource version? I should have looked at the pricing first, there are the benefits... But I have to say I will stick to the Opensource version. Do they plan to deprecate the Opensource version? Confirmed by @sonic6 that it will be not deprecated because they list it on the pricing page as the 0,- tier. As you can see from the screenshot below my container is only for the 0,- tier, the Pro version that you are referring to are the paid tiers.
  21. You should never install anything manually, always search for it on the CA App, this will grantee that you have the latest version from the app installed.
  22. This is the old plugin, please uninstall your version and reinstall it from the CA App, also don't forget to configure it through the Settings page from the new plugin.
  23. @cshellen and this is exactly what is the case here, the Craftopia Dedicated Server app was not updated: (Source) There is nothing I can do about that, you have to wait until the developers from Craftopia update it.
  24. Please set the variable Validation to "true" (without double quotes) let the container fully start (open the logs and see if it pulls the update), after that go into the Docker template again, remove true from Validation and try again to connect. It can be also the case that the Craftopia team hasn't upgraded the server app yet and you simply have to wait or ask in their Discord/Support Forums.
  25. Can you be a bit more prescise what your exact issue is? This message is not an issue at all, this is just a warning and nothing more. The container works as intended at least over here.
×
×
  • Create New...