ljm42

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:

Thanks for all of your help testing the rc series, Unraid 6.12.4 is now available! Changes from rc19 are pretty minor, but if you are running one of the RCs please do upgrade as it simplifies support to have everyone on a stable release.

Thanks for all of your help testing the rc series, Unraid 6.12.4 is now available! Changes from rc19 are pretty minor, but if you are running one of the RCs please do upgrade as it simplifies support to have everyone on a stable release.

It is easy for things to get lost in these release threads. I'd recommend following the guidance from the first post:

So far nobody else has reported anything like this. If you are able to reproduce this in 6.12.4 stable, please create a new thread with as much detail as you can give, perhaps even screenshots, along with diagnostics. Thanks!

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.

This sounds like something strange with your browser, perhaps extreme privacy settings or ad blocking software that is getting confused and breaking things. Try a different browser, preferably with a blank profile that has no browser extensions

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.

According to your screenshot, you have disabled bridging. In 6.12.4-rc18+, when you do this the system automatically enables macvlan and the ipvlan option is removed. In this mode macvlan should be safe to use, we would need to see logs from a crash to figure out what happened. But if you are fine using ipvlan, then you can use the default settings that Unraid ships with instead: * Settings -> Network Settings -> eth0 -> Enable Bridging = Yes * Settings -> Docker -> Docker custom network type = ipvlan

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.

Please take another look at the 6.12.4-rc18 announce post, the whole goal of the changes in this release is to allow users to enable macvlan. If you are fine using ipvlan, then you can use the default settings that Unraid ships with: * Settings -> Network Settings -> eth0 -> Enable Bridging = Yes * Settings -> Docker -> Docker custom network type = ipvlan If ipvlan doesn't work for you (some example reasons are in the announce post) then you can enable macvlan by using the new settings from the announce post. It is difficult to guess why the system crashed, I'd recommend enabling this: Settings -> Syslog Server -> Mirror syslog to flash. If there is a crash you will find the syslog in the logs folder on your flash drive. Note that you should not run in this mode long term as it does increase writes to the flash drive. Please upload both the diagnostics and that syslog if there are issues.

We figure if you want them to stay on screen for longer than a minute then you should just disable auto close by setting the value to zero.

Can you please provide screenshots showing the issue? Also diagnostics.

Would you please provide diagnostics? Also, what is the filesystem on the disk in question?

Good catch, those are the same. We'll remove one for the stable release notes.

We've got a new RC with some nice fixes for the weekend