TOS 7.0.0465 Beta (X86) is Released for Update

[Phil]

Update from 7.0.0448 on my F2-423, The first update attempt reported a download error, even though the internet connection was fine.
The second attempt, after restarting the PC and NAS, initially proceeded normally, but after waiting about 30 minutes, the update failed. All the indicator lights on the NAS were lit normally, but the login page was not displayed.
Attempts to update via the TNAS PC ver. 5.2.520 and a browser (Chrome and Firefox latest version) were unsuccessful, even though the internet connection and firewall were unchanged.





Before anyone says anything weird, here are the results of the internet connection test.



What should I do?

Thank you for your detailed feedback. Your issue appears to be caused by the TOS system being installed on an M.2 NVMe SSD, resulting in an abnormal BIOS boot order. You can refer to this link for a solution: viewtopic.php?t=9417

[Nitrokalel]

Target Users:
Users currently running TOS 7.0.0299 beta or later versions.

Note:
If your TOS version is TOS 6, please refer to the TOS 7 beta update instructions first

Here, we sincerely thank user @snapsh0t, @Phil, @Gremlin, @samius, @rfbjr, @DanB, @Lex, @bartmans99, @Nitrokalel, @mmalchuk, @usersky, @EgorA, @BFG and others, for their sharing and feedback. It is your support that has enabled us to quickly identify and resolve some issues.

Update Notes
Bugs fixes:
1. Fixed the issue where file system snapshots could not be successfully taken under specific conditions.
2. Fixed the issue where the real-time display of application status might be abnormal when operating multiple applications simultaneously.
3. Fixed the issue where an extraction failure might be prompted when updating the system.
4. Fixed the issue where the USB Copy auto-mount function did not take effect.
5. Fixed the issue where the status display might be abnormal during VPN connection.
6. Fixed the issue where the text editor did not display the correct prompt when editing a read-only file.
7. Fixed the issue where some application shortcuts redirected to incorrect pages.
8. Optimized the page display of custom DDNS.
9. Fixed some other known issues.

Warning:
1. If the first update prompts a decompression failure, please click update again.
2. To reduce interruptions caused by system notifications, we have readjusted the triggering rules for notifications at various levels and simultaneously modified the default system notification settings. After the update, you will need to reconfigure your personal notification preferences.
3. Due to the kernel architecture upgrade in TOS 7, the VirtualBox application will no longer be compatible with subsequent versions and will be removed from the App Center.
We recommend that users who still rely on this feature migrate their existing virtual machines to the officially supported VMs (Virtual Machines) application to ensure continued functionality.
For migration instructions, please refer to the technical documentation: https://toshelp.terra-master.com/faq/category/vms


Important Information:
1.Updating the system theoretically will not affect the data on your hard drives, but for safety, please make sure to back up your data in advance.
2.Before updating, ensure that your primary volume (usually volume1) has at least 3GB of available space. Insufficient storage space may cause the update to fail.
3.After the update, the IP address of your TNAS may change. Please use the TNAS PC desktop client to search for and reconnect to the device.

Update Procedure:
1.Go to TOS > Control Panel > General Settings > System > Update, and click "Check for updates."
2.Follow the prompts to update the system.
3.After the system update is complete, you may need to refresh your browser.
4.The TNAS IP address may change after the update. If you cannot connect to your TNAS using the previous IP address, use the TNAS PC client to search for the new IP address.

Client Downloads:
1. Download TNAS PC 5.2.520 for Windows OS.
2. Download TNAS PC 5.2.520 for macOS (x86 and ARM architectures).
3. Download TNAS PC 5.2.520 for macOS (ARM architecture).
4. Download TNAS PC for Linux.
5. Download TNAS Mobile 3.X for Android.
6. For iOS, experience TNAS Mobile 3.X via: https://testflight.apple.com/join/wFWYABJS.

considero importante señalar que la actualización del kernel no es un argumento suficiente para eliminar VirtualBox. Esta herramienta ha demostrado ser compatible tanto con sistemas antiguos como con arquitecturas modernas, por lo que técnicamente es posible mantener su soporte.

Obligar a los usuarios a migrar a una única herramienta no es una buena práctica, y va en contra de la flexibilidad que ha caracterizado a TerraMaster. Los usuarios deben tener la posibilidad de elegir la solución que mejor funcione para sus necesidades.

Por lo tanto, solicito nuevamente que se habilite VirtualBox, o al menos se ofrezca como una opción alternativa.

Adicionalmente, es fundamental que la aplicación VMs funcione de manera estable antes de sustituir completamente a VirtualBox. Actualmente, presenta fallas críticas, especialmente en la importación y exportación de máquinas virtuales en formato OVF.

Es indispensable que:

La importación y exportación en OVF funcione correctamente

No existan bloqueos o congelamientos durante los procesos

Se garantice la estabilidad general de la aplicación

Quiero dejar claro que no me opongo a la migración hacia una nueva plataforma. Sin embargo, esta transición debe ser progresiva, controlada y basada en una herramienta completamente funcional, no en una aplicación en estado beta con fallas críticas como la actual.

Quedo atento a sus comentarios y a una pronta solución.

However, I would like to point out that the kernel upgrade is not a sufficient justification for removing VirtualBox. This software has proven to be compatible with both legacy and modern systems, so maintaining its availability should be technically feasible.

Forcing users to adopt a single tool is not a good practice and goes against the flexibility that has characterized TerraMaster. Users should be allowed to choose the solution that best fits their needs.

Therefore, I respectfully request that VirtualBox be reinstated, or at least offered as an alternative option.

Additionally, it is critical that the VMs application reaches a stable and reliable state before replacing VirtualBox entirely. At present, it has serious issues, particularly with importing and exporting virtual machines in OVF format.

It is essential that:

OVF import and export work reliably

The application does not freeze or become unresponsive

Overall system stability is ensured

I want to be clear that I am not opposed to migration toward a new platform. However, this transition must be gradual, controlled, and based on a fully functional solution—not on a beta application with critical flaws as it currently stands.

I look forward to your response and a prompt resolution.

然而，我认为仅以内核架构升级作为移除 VirtualBox 的理由是不充分的。VirtualBox 已被证明能够在新旧系统环境中稳定运行，从技术角度来看，继续支持该应用是可行的。

强制用户使用单一工具并不是良好的做法，这也违背了 TerraMaster 一直以来所强调的灵活性。用户应当有权选择最适合自身需求的解决方案。

因此，我再次请求恢复 VirtualBox，或至少将其作为可选方案提供给用户。

此外，在完全替代 VirtualBox 之前，必须确保 VMs 应用具备足够的稳定性。目前该应用存在严重问题，尤其是在 OVF 格式虚拟机的导入与导出方面。

必须确保以下几点：

OVF 的导入与导出功能稳定可靠

操作过程中不会出现卡顿或无响应

应用整体运行稳定

我想明确说明，我并不反对向新平台迁移。但这一过程必须是渐进的、可控的，并基于一个完全成熟、稳定的解决方案，而不是当前这样一个存在严重缺陷的测试版应用。

期待您的回复以及问题的尽快解决。

[Nitrokalel]

No piensan arreglarlo? siguen empeñados y necios a seguir con VMs y no integrar un interruptor con virtual Box?
porque no entienden que lo que hacen esta mal? vengo desde TOS5 y confio en la marca y le tengo cariño ala marca, y gracias a ese tiempo y a TOS he aprendido mucho, he aprendido tanto que me resulta facil simplemente cambiar de Sistema Operativo el nas completo y nadar al carajo TOS7, pero no entioenden, requieren una demanda? o que necesitan entender para que regresen esa funcionalidad? nosotros los que sabemos, sabemos que es facil cambiar de SO pero estamos aqui probando este sistema y alzando la voz para que no salga con este tipo de errores que solo lastimaran a la marca, NO van por buen camino, NO SAQUEN TOS 7 A PRODUCCION, retirenlo de los productos finales, por eso estamos aqui todos nosotros.

Разве они не планируют это исправить? Они по-прежнему упрямо настаивают на использовании виртуальных машин вместо интеграции переключателя с VirtualVox?
Почему они не понимают, что делают что-то не так? Я использую TOS5, доверяю этому бренду и испытываю к нему привязанность. Благодаря этому времени и TOS я многому научился. Я узнал так много, что мне легко просто сменить операционную систему всего NAS и отказаться от TOS7. Но они не понимают. Им нужен судебный иск? Или что им нужно понять, чтобы вернуть эту функциональность? Мы, те, кто знает, понимаем, что легко сменить ОС, но мы здесь, тестируем эту систему и поднимаем свой голос, чтобы она не выходила с такими ошибками, которые только навредят бренду. Они на неверном пути. НЕ ВЫПУСКАЙТЕ TOS7 В ПРОИЗВОДСТВО. Удалите её из финальных продуктов. Вот для чего мы все здесь.

他們不打算修復這個問題嗎？他們仍然固執地堅持使用虛擬機，而不是將交換器與 VirtualVox 整合嗎？

他們為什麼不明白自己這樣做是錯的？我一直在使用 TOS5，我信任這個品牌，也對它有感覺。感謝這段時間以及 TOS，我學到了很多。我學到的東西如此之多，以至於我可以輕易地更換整個 NAS 的作業系統，放棄 TOS7。但他們不明白。難道他們需要打官司嗎？或者他們需要明白什麼才能恢復這項功能？我們這些懂行的人都知道更換作業系統很容易，但我們在這裡測試這個系統，發出我們的聲音，就是為了避免它出現這種只會損害品牌的錯誤。他們走錯方向了。不要將 TOS7 發佈到生產環境。從最終產品中移除它。這就是我們聚集在這裡的原因。哎呀


Don't they plan to fix it? Are they still stubbornly insisting on using VMs instead of integrating a switch with VirtualVox?
Why don't they understand that what they're doing is wrong? I've been using TOS5 and I trust the brand and have affection for it. Thanks to that time and to TOS, I've learned a lot. I've learned so much that it's easy for me to simply change the operating system of the entire NAS and ditch TOS7. But they don't understand. Do they need a lawsuit? Or what do they need to understand to bring back that functionality? We, the ones who know, know that it's easy to change the OS, but we're here testing this system and raising our voices so that it doesn't come out with these kinds of errors that will only hurt the brand. They're not on the right track. Don't release TOS7 to production. Remove it from the final products. That's why we're all here. ing

[Gremlin]

Fortunately @TM don't force you to use their operating system. Plus it is possible for users to add their own choice of applications if they are prepared to put in the effort. There are, admittedly, issues with the TOS system of itself that can impose themselves between the o/s and "freewill". However, to say that they are not on the right track is to probably be ignoring the bigger picture.
As far as I know, there is only one person who has, publicly, devoted their time to producing alternative apps for the various TOS systems (and we should all be grateful to them) so perhaps those who want something that is currently not available should maybe follow that lead.

[Joesh]

Thank you for your detailed feedback. Your issue appears to be caused by the TOS system being installed on an M.2 NVMe SSD, resulting in an abnormal BIOS boot order. You can refer to this link for a solution: viewtopic.php?t=9417

I'm not installed TOS on an M.2 NVMe SSD, I'm using HDD.
Is it possible the boot priority change it self?

[TMnight]

Thank you for your continued trust in TOS. We also understand your expectations and concerns regarding the VirtualBox functionality. We recognize that many users, like you, are accustomed to the experience of previous versions, and such changes may cause inconvenience and frustration.

TOS 7 has undergone a major kernel architecture upgrade, which brings improvements in system performance and security. However, this also means that the original VirtualBox application is not fully compatible with the new system at a low level and cannot be guaranteed to run stably or safely. Therefore, we had to remove it from the App Center. This decision was not made lightly, but to ensure the overall reliability of the system and the security of user data.

We will continue to monitor issues, feature requests, and optimization needs related to VMS, and will iterate improvements promptly. We recommend prioritizing the use of VMS to achieve better compatibility and user experience. We also appreciate the valuable feedback you provide during testing, as it plays an important role in helping us improve the system and avoid potential pitfalls.

[TMnight]

The EFI warning in the system log has been reproduced and fixed. The UI error "Failed to retrieve data" has also been reproduced, and a fix is ​​currently under discussion; it is expected to be fixed in a future version.And we appreciate your patience.

[TMnight]

The boot priority will not change on its own. After following the steps in the link, is the NAS currently functioning normally?

[TMjack]

Regarding the error "Failed to retrieve data", we have successfully reproduced it in our laboratory environment.
After investigation, the issue is caused by a timing problem during the system startup phase: the corresponding .sock file for the interface service has not yet been created, or the nginx-related configuration has not finished loading, which results in the failure to obtain data.
In addition, we have reproduced and fixed the EFI warning in the system log.
We will fix this issue and release an update in a subsequent version.

[Joesh]

The boot priority will not change on its own. After following the steps in the link, is the NAS currently functioning normally?

Can you read carefully??.... I'm not installed TOS on NVME, and I'm not changed my F2-423 boot order... I'm using HDD
I hope after this post, no one said about change boor priority again....

Clearly I wrote on the las post:

I'm not installed TOS on an M.2 NVMe SSD, I'm using HDD.
Is it possible the boot priority change it self?