TOS 7.0.1130 (x86) Official Release Update

[nitzer71]

That could be quite catastrophic over time. I use the NAS as local time source I need to remove that because its indeed not syncing externally.

Code: Select all

ntp       102815  0.0  0.0  76172  6488 ?        Ssl  21:41   0:00 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u ntp:ntp

There seems no configuratie path given via -c ...

I had the same issue on my TNAS. I found that /etc/ntp.conf contained:

Code: Select all

server 127.127.1.0 minpoll 6 maxpoll 10 iburst prefer

I removed only the "prefer" option so it now reads:

Code: Select all

server 127.127.1.0 minpoll 6 maxpoll 10 iburst

After restarting the ntp service, and also after rebooting the NAS, an external NTP server is now selected instead of LOCAL(0).

For example:

Code: Select all

*193.177.220.128  129.134.29.123   2 u

LOCAL(0) remains available as a fallback but is no longer selected.

So it appears that the "prefer" setting on LOCAL(0) is what causes the problem.

[TMroy]

We'll be optimizing how NTP is configured. Please stay tuned for the upcoming update.

[crisisacting]

We'll be optimizing how NTP is configured. Please stay tuned for the upcoming update.

That's great; the more that's exposed in TOS (the web interface), the better.

[Gremlin]

Curiouser and curiouser, he said going down the rabbit hole ....
one nas with ntp server running and pointing to 'time.windows.com' (for a relatively common source vs my desktops)

Code: Select all

ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 LOCAL(0)        .LOCL.           5 l  28h   64    0    0.000   +0.000   0.000
*ns-cov.radel.co 139.143.5.30     2 u  547 1024  377   14.831   +1.503   0.724
+194.213.3.203   85.199.214.98    2 u  754 1024  377   15.060   +0.062   0.618
+83.151.207.133  94.198.159.14    2 u  315 1024  377   11.586   +3.098   0.602
-time.cloudflare 10.29.8.4        3 u  126 1024  377   10.651   -0.951   0.391

which tells me it is working because of the '*' and m/s expanded service clusters. 194.xxx (line 3) was line 2 previously and active.


1 nas with ntp server running and pointing to #1 above

Code: Select all

ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*LOCAL(0)        .LOCL.           5 l  199 1024  177    0.000   +0.000   0.000
-178-79-184-152. 82.35.162.146    2 u  961 1024  177    9.937  -232.71 165.554
-139.59.177.246  85.199.214.98    2 u  828 1024  177   10.914  -236.78 168.234
+139-162-242-115 80.192.165.246   2 u 1043 1024  177   12.336  -187.57 126.917
+185.137.221.158 145.238.80.80    2 u 1034 1024  177   19.090  -186.56 127.042

Which equates to the 'bug' reported.

2 nas without ntp server running ostensibly pointing to #1 above:

Code: Select all

ntpq -p
ntpq: read: Connection refused

which (sort of) makes sense but does not tell me what is happening.
If I enable ntp service, it shows the bug.


ntp.conf is unmodified and does not reflect my configuration choices wrt to chosen time server. (so there are other configuration files somewhere?)
BUT (that's a big but) all my nas appear to be in sync with my desktops and show the correct time.
Just thought I would mention it

[EriChan]

Thanks for the detailed feedback and cross-device testing!

It will be optimized in a future TOS update, please stay tuned.

[Nitrokalel]

尊敬的 TerraMaster 团队：

您好！

首先，我想对贵团队在 TOS 7 上所做的出色工作表示祝贺。我对 TOS 7 系统的发展非常满意，尤其是 VMs 虚拟机应用。我目前使用该功能在 TerraMaster 设备上运行和管理虚拟机。

随着时间的推移，我注意到 VMs 应用不断得到改进和完善，我认为它正在逐渐成为一个更加稳定、成熟的虚拟化平台。正因为如此，我希望提出一项我认为对于在专业和企业环境中使用 TerraMaster 的用户来说非常重要的改进建议。

目前，VMs 应用已经支持 虚拟机克隆、关机状态下导出虚拟机以及创建快照（Snapshot） 等功能。

这些功能非常实用，在某些故障或意外情况下也确实能够提供帮助。但是，我认为有必要明确指出：

克隆、导出以及快照并不能真正替代完整的备份系统。

目前，VMs 应用似乎还缺少一种原生机制，可以在 虚拟机保持开机并正常运行的情况下，对其进行完整备份。

这里所说的“备份”，是指能够以一致且可靠的方式复制虚拟机恢复所需的全部内容，包括：

虚拟磁盘
虚拟机配置
相关文件
以及恢复该虚拟机所需的其他组件

并且能够将这些备份保存到 其他存储位置、其他存储卷、另一台 NAS，甚至另一台 TerraMaster 设备上，而无需关闭正在运行的虚拟机。

类似的功能已经广泛应用于企业级虚拟化平台，例如 Microsoft Hyper-V 和 VMware。这些平台允许管理员在虚拟机持续运行的情况下执行备份。

此外，TerraMaster 目前已经拥有一款非常有价值的工具：

Centralized Backup

因此，我认为如果能够将 Centralized Backup 与 VMs 进行深度整合，让 Centralized Backup 可以直接备份由 VMs 管理的虚拟机，将会是一项非常有意义的功能。

例如：

可以让用户在虚拟机持续运行的情况下，将其完整备份到其他存储卷，或者直接备份到另一台 TerraMaster 设备。

我认为 VMs + Centralized Backup 的集成，可能会成为 TOS 7 中一项非常重要的企业级功能。

对于像我们这样在企业环境中使用 TerraMaster，或者为客户提供 IT 服务的用户来说，拥有真正的虚拟机备份功能，可以帮助我们更好地满足企业内部关于以下方面的要求：

数据保护
业务连续性
灾难恢复
IT 安全策略
客户的备份和合规要求

从技术角度来看，如果能够让虚拟机持续运行在一台 TerraMaster 设备上，同时自动将其备份保存到 另一台 TerraMaster 主机，将能够显著提高整个基础设施的可靠性、安全性以及灾难恢复能力。

我认为，这项功能不仅能够为现有用户带来很大的价值，也能够进一步提升 TerraMaster 在专业和企业市场中的竞争力。

对于我们用户而言，我们将获得一个更加完整、安全和可靠的虚拟化解决方案。

对于 TerraMaster 而言，这也能够进一步增强 TOS 在 中小型企业、系统管理员、IT 专业人员以及虚拟化应用场景 中的吸引力，并有可能带来更多用户、更好的评价以及更多的产品销售。

非常感谢贵团队抽出时间阅读我的建议。

我真诚希望这封邮件能够转交给负责 TOS 7、VMs 和 Centralized Backup 开发的相关团队进行评估。

如果这类功能已经在 TerraMaster 未来的开发计划或产品路线图中，我也非常希望能够了解相关信息。

期待您的回复。

此致
敬礼！

[CursaYang]

Thank you for your feedback. I will forward this request to the product team for evaluation.

[OttO1916]

Updated to TOS7.0.1130 without ay issues

[elfreakoxs]

TOS 7 USB disk hibernation regression - ICY BOX IB-RD3640SU3

NAS: TerraMaster F4-424 Pro
TOS: 7.0.1105 / testing around 7.0.1130
USB enclosure: ICY BOX IB-RD3640SU3, configured as hardware RAID5
USB volume: 12 TB logical disk, shown by TOS as H/W RAID5 and /dev/sdf

Problem:
This enclosure and its disks entered standby/hibernation correctly under TOS 6. Since upgrading to TOS 7, the enclosure has never spun down, even after more than 24 hours of no activity.

The internal HDD RAID5 does enter hibernation when the TOS web interface is closed. Therefore, general disk hibernation is working and the issue appears isolated to the USB hardware RAID enclosure.

Checks completed:
Media Index is disabled for the USB volume.
No scheduled S.M.A.R.T. test is configured for the USB disk.
No Docker container or bind mount accesses the ICYraid5 shared folder.
No backup, sync, download, or media-server task uses the USB volume.
My desktop PC/SMB client was off or disconnected during testing.
TOS, Storage Manager, and File Manager were closed during the idle test.
The USB volume was left untouched for a full day.
The USB volume's md wrapper is healthy and idle.
No process is holding /dev/sdf or /dev/md1 open.

Relevant results:
md1 is healthy and idle.
sync_action is idle.
mismatch count is 0.
fuser and lsof show no process accessing /dev/sdf or /dev/md1.

Device detection:
USB ID: 152d:0567
Driver: usb-storage
Speed: 5000M
SCSI address: 5:0:0:0
Logical device: /dev/sdf

TOS identifies the enclosure as a virtual SCSI hardware RAID disk:
Vendor: H/W RAID
Product: 5
Capacity: 12 TB

Important TOS 7 finding:
The TOS 7 script /etc/tos/scripts/spindown explicitly skips USB disks. It only configures standby timers for non-USB disks. Therefore, TOS's normal internal-disk hibernation script is not applying a standby timer to this USB enclosure.

Manual ATA/SAT standby attempts also fail because the hardware RAID USB bridge blocks ATA pass-through:
smartctl -s standby,180 /dev/sdf returns Operation not permitted.
hdparm -y /dev/sdf returns Operation not permitted.

Suspected cause:
Because TOS 7 skips USB devices in its spindown script, this enclosure appears to rely on its own internal idle timer to enter standby. I suspect that TOS 7 is periodically sending low-level USB/SCSI status, health, capacity, mount-state, or monitoring requests to the device. Even very small recurring requests may keep resetting the enclosure's inactivity timer.

This would explain why the same enclosure slept correctly in TOS 6 but never sleeps in TOS 7.

Request:
Could TerraMaster please investigate USB hibernation for JMicron 152d:0567 hardware RAID devices, specifically the ICY BOX IB-RD3640SU3?

1. Does TOS 7 intentionally skip USB disks in /etc/tos/scripts/spindown?
2. Is TOS 7 periodically polling USB SCSI logical units even when no user or application activity exists?
3. Has USB enclosure standby behaviour changed between TOS 6 and TOS 7?
4. Is there a supported way to allow this enclosure to reach its autonomous idle standby state?

I can provide a TOS diagnostic report and the full command output if required.

[EriChan]

To help us accurately diagnose this issue and confirm whether there is an anomaly within the TOS system, we recommend scheduling a remote technical support session with our engineering team.

Please contact our online technical support via the link below. When reaching out, be sure to include this forum post link and your forum ID so our engineers can quickly reference your context and assist you directly:
https://salesiq.zohopublic.com/signatur ... 97d0be8892