ljm42
Administrators
-
Joined
-
Last visited
Everything posted by ljm42
-
Upgrade first
-
Switching to ipvlan should prevent crashes related to macvlan, because macvlan won't be in use. If you ever have unexplained crashes, go to Settings -> Syslog Server and temporarily enable "Mirror syslog to flash", then after a crash you'll find the syslog on the flash drive in the logs folder. That syslog will be useful in determining what happened. Don't leave this setting enabled long term though, as it adds a lot of writes to the flash drive. There are several ways to do bonding, and some require special configuration of your switch. I recommend avoiding those because it is very difficult for anyone to provide remote support without fully understanding your network.
-
The url on your screenshot is a local url, not a remote access url. That one won't work outside of your network I'd suggest running through the instructions here: https://docs.unraid.net/connect/remote-access/
-
We haven't found any downsides to enabling macvtap, as mentioned it may even be faster Bond doesn't matter, disable bridge to enable macvtap
-
Yep! Config changes are just for folks who want to use macvlan EDIT: To be more clear... if you already have ipvlan enabled, and are happy with that, then no config changes are needed after upgrading
-
There seemed to be some confusion, so I have updated the 6.12.4 release notes to make it clear that the new macvlan solution does work with bonding: https://docs.unraid.net/unraid-os/release-notes/6.12.4/
-
I have updated the 6.12.4 release notes to make it clear that the new solution does work with bonding: https://docs.unraid.net/unraid-os/release-notes/6.12.4/
-
There is no need to segment docker traffic to a second nic to avoid the macvlan problem. You can still do that, but there isn't really any benefit. Far simpler to do everything on a single nic. I would not recommend mixing solutions, so either use the previous 2 nic solution OR use the new solution mentioned here.
-
Unraid 6.12.4 is now available, with a solution for the macvlan issues! We highly recommend that everyone upgrade:
-
Unraid 6.12.4 is now available! The release notes detail a different solution to this macvlan problem, the method detailed in this guide is no longer needed.
-
Docker containers in bridge or host mode will always use Unraid's main IP. This guide is specifically to deal with containers that have a dedicated IP on a custom network.
-
The 6.12.4 release includes a fix for macvlan call traces(!) along with other features, bug fixes, and security patches. All users are encouraged to upgrade. Please refer also to the 6.12.0 Announcement post. 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.3, 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 was thought to be resolved with 6.12.3, but some systems are still having issues) Go to Tools -> Update OS. 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 3rd party drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. Reboot Special thanks to all our contributors and beta testers and especially: @bonienl for finding a solution to the macvlan problem! @SimonF for bringing us the new System Drivers page 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.
-
If you have any unassigned devices, remove them, activate the Basic license and upgrade. Otherwise, contact support https://unraid.net/contact
-
You can't really have two nics on the same network like that. Each nic will get its own IP and then the network won't know which one to use to contact your server. If you have the Fix Common Problems plugin installed it will warn about this: https://forums.unraid.net/topic/120220-fix-common-problems-more-information/page/2/#comment-1100014 Your best bet in this case is to use the 10GbE nic for everything. First make a backup of your flash drive (Main -> Boot -> Flash -> Flash Backup), then go to Settings -> Network Settings -> Interface Rules and adjust things until the 10GbE nic is eth0, then reboot. Note: it is best to have a local keyboard/monitor connected when making a change like this so you can see what IP is assigned at boot, in case it is something unexpected.
-
Thanks for mentioning this. We are going to improve how this is handled in a future release. If someone misses the recommendation in the release notes it isn't the end of the world, they will just need to ask for help if they want to delete the Docker directory and start over before we release an update that includes the improvements. The default of using a btrfs vDisk for Docker data is still the best option for most people.
-
Looks like you are running Unraid 6.12.2, you'll want to upgrade to 6.12.3. See the announce post for help stopping the array:
-
Your logs show that disk1 is in use when the array tries to stop: Aug 28 09:56:09 Excalibur emhttpd: Retry unmounting disk share(s)... Aug 28 09:56:14 Excalibur emhttpd: Unmounting disks... Aug 28 09:56:14 Excalibur emhttpd: shcmd (161854): umount /mnt/disk1 Aug 28 09:56:14 Excalibur root: umount: /mnt/disk1: target is busy. Aug 28 09:56:14 Excalibur emhttpd: shcmd (161854): exit status: 32 The most common reason for this is having a terminal window open and sitting in the /mnt/disk1/ directory structure. When stopping the array you need to be sure that no bash terminals are cd'd to /mnt Another option is to install the Dynamix Stop Shell plugin, which will automatically kill any bash shells that are open to /mnt when stopping the array.
-
Nothing was taken away when Connect was added. You can still do manual flash backups on Main -> Boot -> Flash -> Flash Backup. Anything you did there would likely be in the Downloads folder on your computer. Other than that I don't know what you mean by "I set up the Unraid flash backup a while ago" if you don't mean My Servers / Unraid Connect.
-
Thank you for the feedback on the previous rc release, we have one more small set of updates to test before releasing 6.12.4. Highlights include: Resolved an issue with VMs on the macvtap interface not being able to connect to the Internet Additional IPv6 improvements The delay before auto-closing notifications is now configurable (see Settings/Notification Settings) Fix the custom network DHCP subnet options on the Settings/Docker Settings page If you are already on 6.12.4-rc18 this should be a simple update, no need to change any settings. If you are coming from an earlier release please see the 6.12.4-rc18 announce post for info on how to solve macvlan issues and other changes. 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 was resolved with 6.12.3) 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 Known Issues Please see the 6.12.4-rc18 release notes Rolling Back Please see the 6.12.4-rc18 release notes Changes vs. 6.12.4-rc18 docker: add routing when shim or macvtap network is used docker: fix routing when "host access" is enabled docker: remove IPv6 from shim/vhost interface (some routers are incompatible) New notification option: auto-closure time New notification option: notification life time Set default notifications life time to 5 seconds network: print public ipv6 address network: shim interface gets MAC address of parent, no need to generate one Docker settings: fix subnet sizes CSS: set overflow-x to 'auto' Helptext: fix typo Linux kernel version 6.1.47
-
There isn't a lot to go on here, maybe run through the release notes again and see if you missed any steps? After making these changes, only eth0 should be in use, any other nics should be unplugged and nothing should be referencing them. If you think everything is correct please show screenshots of Settings -> Networking -> eth0 and Settings -> Docker, as well as upload your diagnostics.zip (from Tools -> Diagnostics) If you expect a crash, you'll also want to go to Settings -> Syslog Server and enable "Mirror syslog to flash". This will save a copy of your logs on the flash drive so we can see the last thing written if there is a crash. Note this is not something you want to keep enabled long term as it puts extra wear and tear on the flash drive.
-
see https://docs.unraid.net/unraid-os/manual/security/#securing-webgui-connections-ssl
-
If I am understanding you correctly, everything works when you are not using Tailscale. For issues related to that plugin you'd want to use its support thread: https://forums.unraid.net/topic/136889-plugin-tailscale/#comment-1244161 (Plugin authors typically watch their support thread for issues and not the whole forum)
-
Hmm, let's see what is going on: stop the array to reproduce the problem (don't do a full shutdown because you won't be able to grab diagnostics) show the output of `losetup` so we can see what /dev/loop2 points to on your system. run `umount /dev/loop2` to resolve the issue and let the array stop generate and upload your diagnostics.zip (from Tools -> Diagnostics) so we can see logs of the problem happening feel free to start the array again
-
It looks like DNS Rebinding is enabled for your network, so the myunraid.net url will not work. Using SSH, Telnet, or a local keyboard/monitor, type: use_ssl no Then you should be able to access the webgui using: http://192.168.50.254
-
Please uninstall Tailscale to simplify your system. Any change? If not please post updated diagnostics without Tailscale.
