ljm42

Administrators
 View Profile  See their activity

  • Posts

    4379

  • Joined

  • Last visited

  • Days Won

    27

 Content Type 

Everything posted by ljm42

  1. ljm42
    Please retest in 6.12.3-rc3, it includes several changes to networking that should help: https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-6123-rc3-available-r2572/ If there are still issues please restate the problem as it exists in 6.12.3-rc3 and provide fresh diagnostics. Thanks! Keep in mind that it is very difficult to resolve multiple problems in one thread/topic. Also, there is nothing actionable in a post that says "Same" without providing diagnostics. (These are just general statements, not calling anyone out specifically)
  2. ljm42
    The first one is macvlan, our best solution for macvlan issues at this point is mentioned in the 6.12.0 release notes: https://docs.unraid.net/unraid-os/release-notes/6.12.0#known-issues I know some folks aren't happy with that solution, believe me if we get something better we will not forget to put it in the release notes : ) The second post is a mix of topics that is really hard to follow. In general, I would expect networking to be better with this RC. If there are still issues we need new diagnostics showing the issue.
  3. ljm42
    Unraid 6.12.3-rc3 is now available which should resolve issues related to IPv6: https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-6123-rc3-available-r2572/
  4. ljm42
    I don't think I've seen anyone else report that, pls upload your diagnostics.zip (from Tools -> Diagnostics) after the problem happens
  5. ljm42
    I'm afraid I don't know what could be wrong with Plex, but I can help prevent unclean shutdowns, see: https://forums.unraid.net/topic/141479-6122-array-stop-stuck-on-retry-unmounting-disk-shares/#comment-1283203
  6. ljm42
    Were these diagnostics taken while the problem was happening? It doesn't look like any errors were logged. Try bringing up the Javascript Console in your browser and see if there are errors. CTRL-SHIFT-I works on most browsers, or you can try right click -> Inspect -> Console Also, if you have browsers/tabs left open on phones/tablets/other computers, close them all. Some people have issues with tabs being backgrounded and not properly letting go of resources.
  7. ljm42
    Unraid 6.12.3-rc3 is now available which should prevent issues stopping the array: https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-6123-rc3-available-r2572/
  8. ljm42
    Hi folks, there is a lot going on in this thread, and there are likely a lot of different root causes for Samba issues in the four years since this thread was created. If you are having SMB issues in 6.12.0 - 6.12.2, please check out 6.12.3-rc3, available here: This release has networking updates which could affect SMB If that release doesn't help, please review this recent thread, which covers a number of potential problems: If that doesn't help, go ahead and start a new thread with diagnostics and a clear description of the problems that you are seeing. Just to mention it... posts that say "Same" or don't have diagnostics aren't actionable and aren't going to lead to a solution any faster.
  9. ljm42
    Update - if the array can't stop due to "Retry unmounting shares" in 6.12.0 - 6.12.2, the quick fix is to open a web terminal and type: umount /var/lib/docker The array should then stop and prevent an unclean shutdown. (It is possible the array won't stop for other reasons, such as having a web terminal open to a folder on the array. Make sure to exit any web terminals or SSH sessions in this case) We have a fix in the 6.12.3-rc3 prerelease, available here: The fix is in the 6.12.3 release, available here: It would be helpful if some of the folks who have been having an issue stopping the array could upgrade and confirm the issue is resolved in this version. No need, this fix is confirmed. Thanks to everyone who helped track this down!
  10. ljm42
    The 6.12.3-rc3 release is a bug fix release that we'd like feedback on before releasing it as 6.12.3. This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip. Upgrade steps for this release As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Update all of your plugins. This is critical for the NVIDIA and Realtek plugins in particular. If the system is currently running 6.12.0 - 6.12.2, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type: umount /var/lib/docker The array should now stop successfully (This issue is resolved with this release) Go to Tools -> Update OS, change the Branch to "Next". If the update doesn't show, click "Check for Updates" Wait for the update to download and install If you have any plugins that install drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. Reboot Networking This release has fixes for networking, particularly as it relates to IPv6. A side effect is that this will resolve an issue where the webgui won't load in certain instances. Note: If you have code in your go script to disable IPv6, remove that and disable it via the Settings -> Network Settings page instead. Disabling IPv6 by manually running commands will cause conflicts. Docker This release resolves an issue where Docker doesn't properly stop when the array stops, which can result in an unclean shutdown. Known Issues Please review the known issues for 6.12: https://docs.unraid.net/unraid-os/release-notes/6.12.0#known-issues If Docker containers have issues starting after a while, and you are running Plex, go to your Plex Docker container settings, switch to advanced view, and add this to the Extra Params --no-healthcheck Feedback / bugs This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip. Changes vs. 6.12.2 Bug fixes and improvements rc.docker: revised docker daemon running check rc.library: code optimization for ipv6 max/min support ipv4 mapped addresses rc.nginx: explicit ipv4/ipv6 selection on lo interface shfs: correct share size calculation when zfs is one of the volumes webgui: VM settings page: fixed typo webgui: Share Edit page: make minimum free space settings always available Linux kernel Added support to monitor and also limit power on Intel Core (2nd Gen+) CPU models. version 6.1.38 CONFIG_POWERCAP: Generic powercap sysfs driver CONFIG_INTEL_RAPL: Intel RAPL Support via MSR Interface CONFIG_IDLE_INJECT: Idle injection framework Base Distro firefox: version 115.0.r20230710165010 (AppImage)
  11. ljm42
    T-Mobile uses CGNAT, which means you can't forward a port. That prevents Unraid Connect Remote Access from working and limits what you can do with WireGuard. I haven't used Tailscale, but if it makes a permanent connection to some other server when it starts then I can see how it might work with CGNAT
  12. ljm42
    It probably depends on what driver the mobo's onboard NIC uses, if you upload your diagnostics.zip with the plugin uninstalled someone can take a look. TBH if you are buying a new card I would go for Intel rather than Realtek. Intel cards work out of the box with Linux
  13. ljm42
    See this to prevent another unclean shutdown: https://forums.unraid.net/topic/141479-6122-array-stop-stuck-on-retry-unmounting-disk-shares/#comment-1281063
  14. ljm42
    Thank you JorgeB for the incredible support you provide to our community!
  15. ljm42
    Let's keep things friendly please : ) Unraid is not Ubuntu. It is by far a best practice to do this sort of thing in a Docker container, they have very low overhead. You are of course welcome to do whatever you would like with your system, but the more low level customization you do the harder it will be to upgrade and you will more or less be on your own to work through any issues.
  16. ljm42
    I have a feeling everything is fine and we're just confusing each other : ) At one point you said you had uninstalled the plugin, but then after that you asked more questions about stdout.log so I thought you reinstalled it. If the plugin is uninstalled then the log should not grow. Unless you are seeing something else happen, I think we're done here : )
  17. ljm42
    Why does a Plex Docker container have access to the server's /tmp directory?
  18. ljm42
    Are you saying the /var/log/unraid-api/stdout.log continues to grow after uninstalling the plugin? It should not. If so, please show me the output of this command ps -ef | grep unraid-api Edit: actually, please upload your current diagnostics too
  19. ljm42
    Sorry, I'm confused. If you uninstall the Unraid Connect plugin then the sign in box will be removed from the upper right corner of the page and you won't be able to sign in to Unraid Connect from within the webgui. Uninstalling the Unraid Connect plugin will have no effect on logging in to the webgui as root. If that doesn't answer your question, please show a screen shot to help me understand the issue
  20. ljm42
    It is actually up to the container, depends on whether it has code to run healthchecks. I don't know if the other containers you mentioned have code to run healthchecks, don't think I have seen anyone suggest disabling it on them. But it shouldn't hurt to disable it. I don't yet know if everyone should disable healthchecks on Plex, but if they are having issues with containers not being able to restart I will suggest it. For anyone else reading this, if you have the NVIDIA plugin installed be sure it is up to date. Plex healthchecks with older versions versions of the NVIDIA plugin will definitely cause issues. Unraid-api will log activity to help with troubleshooting, the logging shouldn't be a problem (just to repeat for anyone else who stumbles on this - the unraid-api currently logs up to 10MB before rolling the log, in the future that limit will be reduced. Alone it is not enough to fill the 128MB log partition on Unraid) Based on that log snippet I'd suggest signing out of Unraid Connect and then signing back in. If you have further questions about the actual contents of the log, please go to Settings -> Management Access -> Unraid Connect and see the section about Unraid-api logs. They could have confidential information so I'd suggest not posting them publicly.
  21. ljm42
    We are working on issues related to ipv6. For now I'd recommend going to Settings -> Network and configuring the system for ipv4 only Also, it looks like you might be having issues when stopping the array. See https://forums.unraid.net/topic/141479-6122-array-stop-stuck-on-retry-unmounting-disk-shares/#comment-1281063
  22. ljm42
    The unraid-api/stdout.log grows to 10MB and then is rolled. In the next Connect plugin release we're going to reduce the size it can grow to, but even so there is no way that by itself it will fill the 128MB log partition. But why don't you go ahead and uninstall the Unraid Connect plugin for now, just to rule it out TBH if there are any other plugins you can live without, it may help to simplify the system by removing as many as you can. You run Plex right? Go into your Plex Docker container settings, switch to advanced view, and add this to the Extra Params --no-healthcheck
  23. ljm42
    When you run losetup, does /dev/loop1 point to /boot/bzfirmware? If so, that does *not* need to be unmounted to stop the array (and it shouldn't be). Same with /boot/bzmodules. The one loopback that does need to be unmounted is docker.img
  24. ljm42
    Please see https://forums.unraid.net/topic/141479-6122-array-stop-stuck-on-retry-unmounting-disk-shares/#comment-1281063
  25. ljm42
    This test will be improved. But you can prevent the warning in the meantime by deleting config/vsftpd.user_list from your flash drive.