[Unraid OS version 6.10.0-rc3 available]

On 3/17/2022 at 11:46 AM, bonienl said:

Remove the IP and gateway assignment of vlan 10 under network settings, put "none" as network protocol.

 

Under Docker settings define the network and gateway as desired for interface br0.10.

 

 

Hi @bonienl,

 

Thanks for your suggestion.

If you check the second part of my post I tried that as well, although I can only ping the gateway of the new VLAN.

I assume that from the Unraid console I should be resolve that, but I might wrong.

 

On my network side I have Mikrotik devices where I added the VLAN address and mapped to the local bridge. From that device I can also ping the VLAN's gateway 192.168.10.1 but not the one that assigned to the Docker Container.

 

Regards,

Tamas

 

[Unraid OS version 6.10.0-rc3 available]

Hi,

 

I upgraded to 6.10.0-rc3 to resolve an intermittent Unraid OS crash issue that most probably caused the mcvlan in my Docker setting.

I have a quad nic and currently only the eth0 used which bonded to eth1 in a active-backup mode.

 

My problem that I can't create a VLAN on eth0 which would be both shows as an option on my docker container and route traffic as well.

 

After the Upgrade the following steps were done to create a new VLAN: 

1. changed mcvlan to ipvlan in Docker settings
2. Enabled VLANs under network settings and created one like below
3. This time the routing table shows the new VLAN and it's routes
4. Back in Docker settings I selected the new VLAN
5. Tried to select the new network for some of my docker containers, but It's not listed there

 

I also treid to not set IPv4 assignemnt

This time there is no routes, which kinda make sense

Although this time the Custom br0.10 is listed for my container

 

 

Sadly Ping from the console only returns for the Gateway of the new VLAN,

but not from the container (it do work if I use the br0 with my main subnet)

 

Any help would be really appreciated.

 

Regards,

monghuz

 

pandora-nas-diagnostics-20220317-1139.zip

[[6.9.0 RC2] Mover file does not exist]

Hi @mgutt,

 

Thanks for sharing the result of your investigation.

I'm new on this forum so I'm not sure how to engange engange the owners of unraid to get their feedback. 

 

Regarding your below note is this command that we can use it as a workaround to fix the issue? e.g. to recreate the symlinks?

On 12/27/2021 at 1:49 PM, mgutt said:

Internal note:

rsync --archive --itemize-changes --ignore-existing --remove-source-files /mnt/cache/Backups/Shares/appdata/ /mnt/disk7/Backups/Shares/appdata && rsync --archive --itemize-changes --delete "$(mktemp -d)/" /mnt/cache/Backups/Shares/appdata/

 

Thanks,

monghuz

 

[[6.9.0 RC2] Mover file does not exist]

attached

pandora-nas-diagnostics-20211122-0959.zip

[[6.9.0 RC2] Mover file does not exist]

I have the same issue. There are thousands of these files and all of the are exists on the location which saying "No such file..." on unraid 6.9.2

 

Nov 21 04:01:13 Pandora-NAS root: Specified filename /mnt/disk1/appdata/Plex-Media-Server/Library/Application Support/Plex Media Server/Metadata/TV Shows/e/31721686c60b228ff0a6a436b5f10e3a0244fdc.bundle/Contents/_combined/themes/com.plexapp.agents.plexthememusic_3ef0ef6f1f2088d165b2a9c69a7ec06eb19cfc08 does not exist.
Nov 21 04:01:13 Pandora-NAS move: move: file /mnt/disk1/appdata/Plex-Media-Server/Library/Application Support/Plex Media Server/Metadata/TV Shows/e/31721686c60b228ff0a6a436b5f10e3a0244fdc.bundle/Contents/_combined/themes/com.plexapp.agents.plexthememusic_3ef0ef6f1f2088d165b2a9c69a7ec06eb19cfc08
Nov 21 04:01:13 Pandora-NAS move: move_object: /mnt/disk1/appdata/Plex-Media-Server/Library/Application Support/Plex Media Server/Metadata/TV Shows/e/31721686c60b228ff0a6a436b5f10e3a0244fdc.bundle/Contents/_combined/themes/com.plexapp.agents.plexthememusic_3ef0ef6f1f2088d165b2a9c69a7ec06eb19cfc08 No such file or directory

For me it's a mover related issue and would be great if the support team could have a look