Jump to content

ljm42

Administrators
 View Profile  See their activity

  • Posts

    4,427

  • Joined

  • Last visited

  • Days Won

    27

 Content Type 

Posts posted by ljm42

    Unraid OS version 6.12.4 available

    in Announcements

    Posted

    17 hours ago, Revan335 said:

    With IPvlan no Config changes required?

     

    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

    [指南] 如何解决自定义网络上容器的 macvlan 和 ipvlan 问题

    in Docker Containers

    Posted

    4 hours ago, TRaSH said:

    In my current setup i use bonding (Mode 4 (802.3ad)), main reason was because when I'm doing heavy traffic up/download, i got issues during plex playback because my nic was fully saturated.

    With these changes i have the feeling i will go back to the same issues before i decided to bond them.

     

    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/

    Unraid OS version 6.12.4 available

    in Announcements

    Posted

    2 minutes ago, Chunks said:

    Can I ask for a little clarity on this statement?

     

    Is it recommended to revert from using 2 nic's to 1? Or just, running only 1 is an option now?

     

    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.

    [指南] 如何解决自定义网络上容器的 macvlan 和 ipvlan 问题

    in Docker Containers

    Posted

    1 hour ago, Chunks said:

    When moving Dockers from a single interface (eth0) to a new dedicated one (eth1).... I had no problems when the dockers were swapped from br0 to eth1 networks. But I have a whole bunch of dockers using just "bridge". These get the IP address of the host system, the main unraid IP (eth0).

     

    For example:

     

    image.png.a30b21962704a04e47b298bbc2db6303.png

     

    Is the fix to make all of these eth1 as well? If so, what IP do I use? Can I create a single new address that they all can share, or is this the whole point of removing bridging? Or did I miss something/mess something up? 

     

     

    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.

    • Like 1

    Unraid OS version 6.12.4 available

    in Announcements

    Posted

    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

    1. As always, prior to upgrading, create a backup of your USB flash device:  "Main/Flash/Flash Device Settings" - click "Flash Backup".
    2. Update all of your plugins. This is critical for the NVIDIA and Realtek plugins in particular.
    3. 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)

    4. Go to Tools -> Update OS. If the update doesn't show, click "Check for Updates"
    5. Wait for the update to download and install
    6. 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. 
    7. 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.

    • Like 14
    • Thanks 7

    Multiple NICs - Same LAN

    in Hardware

    Posted

    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.

    Unraid OS version 6.12.3 available

    in Announcements

    Posted

    On 7/22/2023 at 1:36 PM, Revan335 said:

    The new recommended docker Path is on the 6.12 Documentation/Release Notes -> Docker /mnt/user/docker not /mnt/system/docker on ZFS with special Config.

    https://docs.unraid.net/unraid-os/release-notes/6.12.0

     

    Can you change the default Docker Path and his configuration to this?

     

    Then have new Installations the new Path and Config without reading the Release Notes. When 6.13 or higher released "nobody" read this old Release Notes/Documentation.

     

    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.

    • Like 1
    • Thanks 1

    [6.12.2] Array stop stuck on "Retry unmounting disk share(s)"

    in General Support

    Posted

    34 minutes ago, kn0wt said:

    having the same issue as @falkfyrebeard on 6.12.3, I attached my diagnostics and the output of `losetup`.. hopefully it'll help as well? ive had it happen to me the last 2 times ive stopped the array.. 1st time i waitied 20-30 min and then just hard rebooted the server. then just did it again and had the same issue.. 

    root@Excalibur:~# losetup
NAME       SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE                           DIO LOG-SEC
/dev/loop1         0      0         1  1 /boot/bzfirmware                      0     512
/dev/loop2         0      0         1  0 /mnt/disk1/system/docker/docker.img   0     512
/dev/loop0         0      0         1  1 /boot/bzmodules                       0     512
root@Excalibur:~# /etc/rc.d/rc.docker status
status of dockerd: stopped
root@Excalibur:~# umount /dev/loop2
root@Excalibur:~#

     

    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.

     

     

     

    [指南] 如何解决自定义网络上容器的 macvlan 和 ipvlan 问题

    in Docker Containers

    Posted

    2 hours ago, TheBroTMv2 said:

    Nope wanted to spin finally up again my lancache as i also use swag and hat the crash some hours later. No response only hard reset possible seems not fixed :/

     

    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.

    [6.12.2] Array stop stuck on "Retry unmounting disk share(s)"

    in General Support

    Posted

    1 hour ago, falkfyrebeard said:

    I know this seems to be marked as fixed in 6.12.3 but I am still running in to it on both of my servers on 6.12.3. Happened to both of them yesterday multiple times. The solution "umount /dev/loop2" fixes it every time.

     

    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
×
×
  • Create New...