TOS 7.0.1105 (x86) Official Release Update

[TMzethar]

Thank you for your report, we will varify the GlobalSearch Issue soon.

[TMzethar]

Ok, so wasn't imagining that & can second this issue; have also noticed the NTP time sync not being accurate (drifting) across multiple TNAS models on TOS 7.

We've confirmed that there's an NTP bug — local time sync and NTP are supposed to work independently. A fix is currently in progress. Please wait for a future TOS 7 update.

[Gremlin]

OK, noted. I thought I saw some additional usb storage activity when the system booted (no usb storage device(s) attached).

[snapsh0t]

You can check the status of both services with the following commands:

Code: Select all

systemctl status smartd.service

Code: Select all

systemctl status smartmontools.service

Then try stopping and disabling the service to see if it resolves the issue:

Code: Select all

systemctl stop smartd.service

Code: Select all

systemctl disable smartd.service

We will investigate what might cause smartd.service to be unexpectedly started again.

Disabling smartd had the desired effect and the drives are sleeping after 30min and staying asleep until accessed then going back to sleep 30min later. Before that, the statuses were as follows

Code: Select all

Adm1n@Therver2:/# systemctl status smartd.service
● smartmontools.service - LSB: SMART monitoring daemon
     Loaded: loaded (/etc/init.d/smartmontools; generated)
     Active: active (running) since Wed 2026-08-05 15:01:04 BST; 2min 10s ago
       Docs: man:systemd-sysv-generator(8)
      Tasks: 1 (limit: 18631)
     Memory: 2.9M (available: 13.7G)
        CPU: 54ms
     CGroup: /system.slice/smartmontools.service
             └─1397 /usr/sbin/smartd --pidfile /var/run/smartd.pid

Aug 05 15:01:03 Therver2 smartd[1304]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 56 to 65
Aug 05 15:01:03 Therver2 smartd[1304]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 52 to 65
Aug 05 15:01:03 Therver2 smartd[1304]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD181KFGX_68AFPN0-4ZGZYW5V.ata.state
Aug 05 15:01:03 Therver2 smartd[1304]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD181KFGX_68AFPN0-4ZH08ZYV.ata.state
Aug 05 15:01:03 Therver2 smartd[1304]: Device: /dev/nvme0, state written to /var/lib/smartmontools/smartd.WD_Red_SN700_500GB-254726800656.nvme.state
Aug 05 15:01:03 Therver2 smartd[1304]: Device: /dev/nvme1, state written to /var/lib/smartmontools/smartd.WD_Red_SN700_500GB-254726800572.nvme.state
Aug 05 15:01:03 Therver2 smartd[1397]: smartd has fork()ed into background mode. New PID=1397.
Aug 05 15:01:03 Therver2 smartd[1397]: file /var/run/smartd.pid written containing PID 1397
Aug 05 15:01:04 Therver2 smartmontools[1245]:    ...done.
Aug 05 15:01:04 Therver2 systemd[1]: Started LSB: SMART monitoring daemon.

Adm1n@Therver2:/# systemctl status smartmontools.service
● smartmontools.service - LSB: SMART monitoring daemon
     Loaded: loaded (/etc/init.d/smartmontools; generated)
     Active: active (running) since Wed 2026-08-05 15:01:04 BST; 3min 1s ago
       Docs: man:systemd-sysv-generator(8)
      Tasks: 1 (limit: 18631)
     Memory: 2.9M (available: 13.4G)
        CPU: 54ms
     CGroup: /system.slice/smartmontools.service
             └─1397 /usr/sbin/smartd --pidfile /var/run/smartd.pid

Aug 05 15:01:03 Therver2 smartd[1304]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 56 to 65
Aug 05 15:01:03 Therver2 smartd[1304]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 52 to 65
Aug 05 15:01:03 Therver2 smartd[1304]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD181KFGX_68AFPN0-4ZGZYW5V.ata.state
Aug 05 15:01:03 Therver2 smartd[1304]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD181KFGX_68AFPN0-4ZH08ZYV.ata.state
Aug 05 15:01:03 Therver2 smartd[1304]: Device: /dev/nvme0, state written to /var/lib/smartmontools/smartd.WD_Red_SN700_500GB-254726800656.nvme.state
Aug 05 15:01:03 Therver2 smartd[1304]: Device: /dev/nvme1, state written to /var/lib/smartmontools/smartd.WD_Red_SN700_500GB-254726800572.nvme.state
Aug 05 15:01:03 Therver2 smartd[1397]: smartd has fork()ed into background mode. New PID=1397.
Aug 05 15:01:03 Therver2 smartd[1397]: file /var/run/smartd.pid written containing PID 1397
Aug 05 15:01:04 Therver2 smartmontools[1245]:    ...done.
Aug 05 15:01:04 Therver2 systemd[1]: Started LSB: SMART monitoring daemon.
Adm1n@Therver2:/# 

[nitzer71]

Thank you for your report, we will varify the GlobalSearch Issue soon.

Additional observation:

after a clean NAS reboot, globalsearch starts normally with very low CPU usage. Approximately 2 hours later it begins consuming CPU again and continues increasing over time. Restarting only the globalsearch service immediately returns CPU usage to normal, but the behaviour repeats after a few hours.

[TMzethar]

Additional observation:

after a clean NAS reboot, globalsearch starts normally with very low CPU usage. Approximately 2 hours later it begins consuming CPU again and continues increasing over time. Restarting only the globalsearch service immediately returns CPU usage to normal, but the behaviour repeats after a few hours.

We haven't been able to replicate the issue on our side yet. If you have a moment, you can contact us online and book a time for one of our engineers to take a remote look.
https://salesiq.zohopublic.com/signatur ... 97d0be8892

Update: It has been confirmed that GlobalSearch has an issue causing an infinite loop that consumes excessive resources. Please wait for a future update to resolve this issue.

[snapsh0t]

So I stopped and disabled the smartd service as suggested by RyanYang but now I can't get it back. A reboot didn't help. How do I get it back, please?

Code: Select all

Adm1n@Therver2:/# systemctl status smartd.service
Unit smartd.service could not be found.
Adm1n@Therver2:/# systemctl enable smartd.service
Failed to enable unit: Unit file smartd.service does not exist.
Adm1n@Therver2:/# systemctl start smartd.service
Failed to start smartd.service: Unit smartd.service not found.
Adm1n@Therver2:/# 

[thomass112]

Thanks for posting this, glad to see the x86 branch keeps getting steady point releases. Given the pattern from 7.0.0777 and earlier builds, it'd be great if this one specifically addresses the App Center going empty/missing installed apps after upgrade and the Docker container autorun-too-early issue at boot, since both kept popping up across the last few releases and seem to be the most disruptive for people running production setups. Has anyone upgraded from 6.x directly to 1105 yet, or is it safer to go through 6 → 7 beta → stable like the official guidance suggested? Also curious if HDD sleep/hibernation for non-system drives is stable now, that was still flaky as of 0777.

[TMzethar]

Thanks for posting this, glad to see the x86 branch keeps getting steady point releases. Given the pattern from 7.0.0777 and earlier builds, it'd be great if this one specifically addresses the App Center going empty/missing installed apps after upgrade and the Docker container autorun-too-early issue at boot, since both kept popping up across the last few releases and seem to be the most disruptive for people running production setups. Has anyone upgraded from 6.x directly to 1105 yet, or is it safer to go through 6 → 7 beta → stable like the official guidance suggested? Also curious if HDD sleep/hibernation for non-system drives is stable now, that was still flaky as of 0777.

Most of the issues you mentioned have been addressed in recent releases. For details, please refer to the update notes for each TOS 7 version:
viewforum.php?f=28

Please do not upgrade directly from 6.x to TOS 7.0.1105 using the .bz2 update package, as this may cause issues.

For the proper upgrade procedure to TOS 7, please refer to:
viewtopic.php?t=10183

Alternatively, you can first flash the internal USB Initboot to the TOS 7‑specific version, then perform a clean installation of a newer TOS 7 release:
viewtopic.php?t=6433

[Claus]

Hi, I manually updated from version V804. Now I have the GlobalSearch problem too. After a restart, things look very good for a short while. However, after about 10 minutes, the process's resource usage keeps climbing higher and higher.
Hardware: F4-424 Max.