[Help] TOS7 vSwitch disables Jumbo Frames during boot
[Help] TOS7 vSwitch disables Jumbo Frames during boot
Hello,
I use U4-500 and D4-320U.
If Open vSwitch is enabled, Jumbo Frames stop working on the network interfaces during the boot process. Even worse, standard MTU 1500 traffic also stops working. The MTU value has to be reduced in order to restore connectivity.
If Open vSwitch is disabled, the MTU works correctly after boot.
If Open vSwitch is enabled after the system has already booted, the MTU also works correctly.
However, if Open vSwitch was enabled during boot and the MTU becomes broken, then disabling Open vSwitch and rebooting the TNAS fixes the issue. After that, if Open vSwitch is enabled again, the MTU continues to work correctly until the next reboot.
When the MTU does not work correctly, the RAID can also become unstable. Usually, one of the drives in the RAID1 array is affected.
I suspect this issue is related to SMB behavior, as SMB is sensitive to MTU problems.
I encountered this problem on my system. The RAID1 array would not assemble properly under any circumstances. I disabled Open vSwitch and rebooted the TNAS, and the RAID array assembled successfully without any issues.
Please fix the proper MTU handling when using Open vSwitch.
P.S.
It would also be very useful to have the ability to assign multiple network interfaces directly to the TNAS itself, including interfaces from different VLANs.
Additionally, it would be highly desirable for TNAS to have a standard option to use a local NTP server. If the time between hosts and storage systems becomes inconsistent, it can cause serious infrastructure problems. For enterprise environments, it is preferable to use a single internal NTP server, but currently TNAS does not provide this capability.
Привет,
Если включён Open vSwitch то во время загрузки Jumbo Frames перестают проходить на интерфейс. Хуже того, обычные MTU 1500 также престают ходить. Нужно уменьшать MTU.
Если Open vSwitch выключен, то при загрузке MTU работает правильно.
Если Open vSwitch включить после загрузки, то также MTU работает правильно.
Если Open vSwitch был включён во время загрузки (MTU сломалось), то если Open vSwitch выключить, а потом выключить то MTU нормально заработает. Если потом включить Open vSwitch то MTU продолжит работать правильно до первой перезагрузки.
Когда MTU нормально не проходит, то может ломаться RAID. Обычно один из дисков RAID1.
Я думаю, что это связано с работой SMB, чувствительной к MTU.
Я столкнулся с такой проблемой. RAID1 никак не хотел собираться.
Выключил Open vSwitch. Перезагрузил TNAS. RAID собрался без проблем.
Пожалуйста почините нормальную работу MTU в связке с Open vSwitch.
P.S.
Также очень хочется назначать несколько интерфейсов на сам TNAS из разных VLAN.
И очень бы хотелось для TNAS иметь стандартную возможность использовать свой локальный NTP сервер. Если между хотами и хранилищем время расходится, это может вызвать серьёзные проблемы, поэтому для инфраструктуры лучше использовать один свой NTP сервер, а у TNAS нет такой возможности.
I use U4-500 and D4-320U.
If Open vSwitch is enabled, Jumbo Frames stop working on the network interfaces during the boot process. Even worse, standard MTU 1500 traffic also stops working. The MTU value has to be reduced in order to restore connectivity.
If Open vSwitch is disabled, the MTU works correctly after boot.
If Open vSwitch is enabled after the system has already booted, the MTU also works correctly.
However, if Open vSwitch was enabled during boot and the MTU becomes broken, then disabling Open vSwitch and rebooting the TNAS fixes the issue. After that, if Open vSwitch is enabled again, the MTU continues to work correctly until the next reboot.
When the MTU does not work correctly, the RAID can also become unstable. Usually, one of the drives in the RAID1 array is affected.
I suspect this issue is related to SMB behavior, as SMB is sensitive to MTU problems.
I encountered this problem on my system. The RAID1 array would not assemble properly under any circumstances. I disabled Open vSwitch and rebooted the TNAS, and the RAID array assembled successfully without any issues.
Please fix the proper MTU handling when using Open vSwitch.
P.S.
It would also be very useful to have the ability to assign multiple network interfaces directly to the TNAS itself, including interfaces from different VLANs.
Additionally, it would be highly desirable for TNAS to have a standard option to use a local NTP server. If the time between hosts and storage systems becomes inconsistent, it can cause serious infrastructure problems. For enterprise environments, it is preferable to use a single internal NTP server, but currently TNAS does not provide this capability.
Привет,
Если включён Open vSwitch то во время загрузки Jumbo Frames перестают проходить на интерфейс. Хуже того, обычные MTU 1500 также престают ходить. Нужно уменьшать MTU.
Если Open vSwitch выключен, то при загрузке MTU работает правильно.
Если Open vSwitch включить после загрузки, то также MTU работает правильно.
Если Open vSwitch был включён во время загрузки (MTU сломалось), то если Open vSwitch выключить, а потом выключить то MTU нормально заработает. Если потом включить Open vSwitch то MTU продолжит работать правильно до первой перезагрузки.
Когда MTU нормально не проходит, то может ломаться RAID. Обычно один из дисков RAID1.
Я думаю, что это связано с работой SMB, чувствительной к MTU.
Я столкнулся с такой проблемой. RAID1 никак не хотел собираться.
Выключил Open vSwitch. Перезагрузил TNAS. RAID собрался без проблем.
Пожалуйста почините нормальную работу MTU в связке с Open vSwitch.
P.S.
Также очень хочется назначать несколько интерфейсов на сам TNAS из разных VLAN.
И очень бы хотелось для TNAS иметь стандартную возможность использовать свой локальный NTP сервер. Если между хотами и хранилищем время расходится, это может вызвать серьёзные проблемы, поэтому для инфраструктуры лучше использовать один свой NTP сервер, а у TNAS нет такой возможности.
Re: [Help] TOS7 vSwitch disables Jumbo Frames during boot
{I don't use Jumbo frames, so cannot comment}Tolian wrote: ↑27 Jun 2026, 17:34
Additionally, it would be highly desirable for TNAS to have a standard option to use a local NTP server. If the time between hosts and storage systems becomes inconsistent, it can cause serious infrastructure problems. For enterprise environments, it is preferable to use a single internal NTP server, but currently TNAS does not provide this capability.
However, I have set up one of my nas to be NTP server (via Control panel) and the others use that server via the "customise" option under "Sync with server" (Tos6 and Tos7)
Seems to work OK.
F5-221 TOS7.0.0777 - 4x4TB (Ironwolf) Traid
F2-424 TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (HGST) Traid
F2-221 TOS7.0.0777 - 1x3TB Ext4, 1x4TB Btrfs
F2-425+ TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (EXOS) Traid
F2-424 TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (HGST) Traid
F2-221 TOS7.0.0777 - 1x3TB Ext4, 1x4TB Btrfs
F2-425+ TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (EXOS) Traid
Re: [Help] TOS7 vSwitch disables Jumbo Frames during boot
Thank you very much for your reply. In TOS 6, there was no option to set up a custom NTP server, only to select one. I've only been using TOS 7 for two days. Before, I couldn't find the option to set the NTP server IP address. Thanks to your post, I went back into the settings and searched more carefully than the first time. And I found it! Thank you.However, I have set up one of my nas to be NTP server (via Control panel) and the others use that server via the "customise" option under "Sync with server" (Tos6 and Tos7)
Seems to work OK.
Re: [Help] TOS7 vSwitch disables Jumbo Frames during boot
To better assist you in confirming whether there are any abnormalities in the TOS system, please send the complete log to our technical support email at [email protected] via email, and attach the forum link and your forum ID as well.
Re: [Help] TOS7 vSwitch disables Jumbo Frames during boot
Hello,To better assist you in confirming whether there are any abnormalities in the TOS system, please send the complete log to our technical support email at [email protected] via email, and attach the forum link and your forum ID as well.
Thank you very much. I already contacted support yesterday, attached the log, and provided a link to the forum.
Maybe someone else is experiencing similar issues, or problems with RAIDs falling apart. I think the discussion in general might also be helpful.
Best wishes.
Re: [Help] TOS7 vSwitch disables Jumbo Frames during boot
To establish a connection with your local NTP server, navigate to Control Panel > General Settings > Region and Language > Time, enable the Sync with Server option, choose Custom from the dropdown list, and then input your NTP server address.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Re: [Help] TOS7 vSwitch disables Jumbo Frames during boot
I was already told in this thread above that this feature has appeared in TOS7. Thank you.
Re: [Help] TOS7 vSwitch disables Jumbo Frames during boot
It also exists in TOS6 for certain and quite possible in Tos5 although I cannot remember that far back. You're welcome/
F5-221 TOS7.0.0777 - 4x4TB (Ironwolf) Traid
F2-424 TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (HGST) Traid
F2-221 TOS7.0.0777 - 1x3TB Ext4, 1x4TB Btrfs
F2-425+ TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (EXOS) Traid
F2-424 TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (HGST) Traid
F2-221 TOS7.0.0777 - 1x3TB Ext4, 1x4TB Btrfs
F2-425+ TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (EXOS) Traid
Re: [Help] TOS7 vSwitch disables Jumbo Frames during boot
TOS 7.0.0777
The problem remains relevant.
Open vSwitch is off
Open vSwitch is on
Rebooting TNAS
Open vSwitch is on
Open vSwitch is off
The problem remains relevant.
Open vSwitch is off
Code: Select all
TNAS:~# ping 192.168.192.81 -s 9000
PING 192.168.192.81 (192.168.192.81) 9000(9028) bytes of data.
9008 bytes from 192.168.192.81: icmp_seq=1 ttl=128 time=0.469 msCode: Select all
TNAS:~# ping 192.168.192.81 -s 9000
PING 192.168.192.81 (192.168.192.81) 9000(9028) bytes of data.
9008 bytes from 192.168.192.81: icmp_seq=1 ttl=128 time=0.469 msOpen vSwitch is on
Code: Select all
TNAS:~# ping 192.168.192.81 -s 9000
PING 192.168.192.81 (192.168.192.81) 9000(9028) bytes of data.
^C
--- 192.168.192.81 ping statistics ---
9 packets transmitted, 0 received, 100% packet loss, time 8198msCode: Select all
TNAS:~# ping 192.168.192.81 -s 9000
PING 192.168.192.81 (192.168.192.81) 9000(9028) bytes of data.
9008 bytes from 192.168.192.81: icmp_seq=1 ttl=128 time=0.493 ms


