TOS 7.0.1105 (x86) Official Release Update

Official news about TOS, mobile app, PC app updates or beta releases.
User avatar
TMroy
TM Support
Posts: 3106
Joined: 10 Mar 2020, 14:04
China

Re: TOS 7.0.1105 (x86) Official Release Update

Post by TMroy »

nitzer71 wrote: 05 Aug 2026, 10:11
Regarding the ntpd issue, we will vafiry it soon, thank you for your report.
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)
User avatar
sianderson
Silver Member
Posts: 444
Joined: 02 Aug 2020, 03:42
Great Britain

Re: TOS 7.0.1105 (x86) Official Release Update

Post by sianderson »

both updated, no issues observed so far
F2-424 TOS 7.0.1130
F2-423 TOS 7.0.1130
F2-210 TOS 4.2.44
D4-320

C/O
F4-424 TOS 6.0.794
User avatar
nitzer71
Posts: 29
Joined: 08 Jul 2026, 08:12
Switzerland

Re: TOS 7.0.1105 (x86) Official Release Update

Post by nitzer71 »

nitzer71 wrote: 05 Aug 2026, 12:55 After upgrading to TOS 7.0.1105, I noticed that the GlobalSearch process has been running continuously for several hours and using around 120–150% CPU.

Media Indexing is disabled on my TNAS.

I noticed the release notes mention a fix related to media indexing and system drive sleep mode. Could this update have triggered a GlobalSearch rebuild or some indexing process after the upgrade?

I did not notice this behaviour after the previous TOS 7 update, so I just wanted to check if this is expected.
Update: After restarting the GlobalSearch service, the high CPU usage stopped.

Before the restart,

Code: Select all

globalsearch
was running continuously for several hours after upgrading to TOS 7.0.1105 and was consuming around 120–150% CPU according to the process monitor, even though no manual indexing had been configured.

After restarting the GlobalSearch service, CPU usage returned to normal and the service is now idle.

I will continue monitoring.
User avatar
snapsh0t
Posts: 85
Joined: 19 Oct 2025, 03:23
Great Britain

Re: TOS 7.0.1105 (x86) Official Release Update

Post by snapsh0t »

So disk sleep activity has changed but not for the better. Now both HDDs sleep for 30 minutes, wake up together then go back to sleep after another 30 minutes, wake up after 30 minutes, etc....
This activity is preceded by SMART reports of temperature changes for the two drives but the temperatures reported are between 50C and 65C which are the temps of the M.2 drives; the HDDs are between 30C and 35C. These SMART reports are not present in the system log I recorded with TOS 7.0.0804.

Code: Select all

Aug  5 01:55:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 55 to 63
Aug  5 01:55:12 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 52 to 60
Aug  5 01:55:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=standby to=active detected_by=hdparm
Aug  5 01:55:21 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=standby to=active detected_by=hdparm
Aug  5 02:25:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 63 to 55
Aug  5 02:25:04 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 60 to 52
Aug  5 02:25:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=active to=standby
Aug  5 02:25:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=active to=standby
Aug  5 02:55:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 55 to 63
Aug  5 02:55:13 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 52 to 60
Aug  5 02:55:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=standby to=active detected_by=hdparm
Aug  5 02:55:21 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=standby to=active detected_by=hdparm
Aug  5 03:25:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 63 to 55
Aug  5 03:25:04 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 60 to 52
Aug  5 03:25:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=active to=standby
Aug  5 03:25:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=active to=standby
Aug  5 03:55:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 55 to 63
Aug  5 03:55:13 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 52 to 60
Aug  5 03:55:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=standby to=active detected_by=hdparm
Aug  5 03:55:22 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=standby to=active detected_by=hdparm
Aug  5 04:25:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 63 to 56
Aug  5 04:25:04 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 60 to 52
Aug  5 04:25:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=active to=standby
Aug  5 04:25:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=active to=standby
Aug  5 04:55:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 56 to 63
Aug  5 04:55:12 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 52 to 60
Aug  5 04:55:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=standby to=active detected_by=hdparm
Aug  5 04:55:21 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=standby to=active detected_by=hdparm
Aug  5 05:25:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 63 to 56
Aug  5 05:25:04 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 60 to 52
Aug  5 05:26:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=active to=standby
Aug  5 05:26:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=active to=standby
Aug  5 05:55:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 56 to 63
Aug  5 05:55:13 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 52 to 60
Aug  5 05:55:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=standby to=active detected_by=hdparm
Aug  5 05:55:21 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=standby to=active detected_by=hdparm
Aug  5 06:25:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 63 to 56
Aug  5 06:25:04 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 60 to 53
Aug  5 06:25:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=active to=standby
Aug  5 06:25:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=active to=standby
Aug  5 06:55:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 56 to 63
Aug  5 06:55:13 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 53 to 60
Aug  5 06:55:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=standby to=active detected_by=hdparm
Aug  5 06:55:22 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=standby to=active detected_by=hdparm
Aug  5 07:25:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 63 to 56
Aug  5 07:25:04 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 60 to 52
Aug  5 07:25:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=active to=standby
Aug  5 07:25:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=active to=standby
Aug  5 07:55:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 56 to 63
Aug  5 07:55:12 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 52 to 60
Aug  5 07:55:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=standby to=active detected_by=hdparm
Aug  5 07:55:21 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=standby to=active detected_by=hdparm
F2-425 Plus, 16GB RAM, 2 x 500GB WD SN700 EXT4 RAID1, 2 x 18TB WD Red Pro EXT4 RAID1, TOS 7.0.<latest>
User avatar
joka388
Posts: 37
Joined: 07 Mar 2022, 21:42
Austria

Re: TOS 7.0.1105 (x86) Official Release Update

Post by joka388 »

snapsh0t wrote: 05 Aug 2026, 16:15 So disk sleep activity has changed but not for the better. Now both HDDs sleep for 30 minutes, wake up together then go back to sleep after another 30 minutes, wake up after 30 minutes, etc....
This activity is preceded by SMART reports of temperature changes for the two drives but the temperatures reported are between 50C and 65C which are the temps of the M.2 drives; the HDDs are between 30C and 35C. These SMART reports are not present in the system log I recorded with TOS 7.0.0804.

Code: Select all

Aug  5 01:55:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 55 to 63
Aug  5 01:55:12 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 52 to 60
Aug  5 01:55:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=standby to=active detected_by=hdparm
Aug  5 01:55:21 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=standby to=active detected_by=hdparm
Aug  5 02:25:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 63 to 55
Aug  5 02:25:04 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 60 to 52
Aug  5 02:25:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=active to=standby
Aug  5 02:25:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=active to=standby
Aug  5 02:55:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 55 to 63
Aug  5 02:55:13 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 52 to 60
Aug  5 02:55:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=standby to=active detected_by=hdparm
Aug  5 02:55:21 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=standby to=active detected_by=hdparm
Aug  5 03:25:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 63 to 55
Aug  5 03:25:04 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 60 to 52
Aug  5 03:25:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=active to=standby
Aug  5 03:25:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=active to=standby
Aug  5 03:55:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 55 to 63
Aug  5 03:55:13 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 52 to 60
Aug  5 03:55:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=standby to=active detected_by=hdparm
Aug  5 03:55:22 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=standby to=active detected_by=hdparm
Aug  5 04:25:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 63 to 56
Aug  5 04:25:04 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 60 to 52
Aug  5 04:25:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=active to=standby
Aug  5 04:25:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=active to=standby
Aug  5 04:55:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 56 to 63
Aug  5 04:55:12 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 52 to 60
Aug  5 04:55:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=standby to=active detected_by=hdparm
Aug  5 04:55:21 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=standby to=active detected_by=hdparm
Aug  5 05:25:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 63 to 56
Aug  5 05:25:04 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 60 to 52
Aug  5 05:26:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=active to=standby
Aug  5 05:26:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=active to=standby
Aug  5 05:55:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 56 to 63
Aug  5 05:55:13 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 52 to 60
Aug  5 05:55:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=standby to=active detected_by=hdparm
Aug  5 05:55:21 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=standby to=active detected_by=hdparm
Aug  5 06:25:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 63 to 56
Aug  5 06:25:04 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 60 to 53
Aug  5 06:25:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=active to=standby
Aug  5 06:25:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=active to=standby
Aug  5 06:55:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 56 to 63
Aug  5 06:55:13 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 53 to 60
Aug  5 06:55:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=standby to=active detected_by=hdparm
Aug  5 06:55:22 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=standby to=active detected_by=hdparm
Aug  5 07:25:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 63 to 56
Aug  5 07:25:04 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 60 to 52
Aug  5 07:25:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=active to=standby
Aug  5 07:25:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=active to=standby
Aug  5 07:55:04 Therver2 smartd[14563]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 56 to 63
Aug  5 07:55:12 Therver2 smartd[14563]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 52 to 60
Aug  5 07:55:17 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sda from=standby to=active detected_by=hdparm
Aug  5 07:55:21 Therver2 TOSDaemon[16071]: disk power state changed device=/dev/sdb from=standby to=active detected_by=hdparm
Thx snapsh0t, its exact the same on both of my NAS :evil:
F2-221 6 Gb RAM - 2x8TB
F4-425 16 Gb RAM - 4x4TB
User avatar
RyanYang
TM Support
Posts: 1166
Joined: 01 Dec 2020, 11:50
China

Re: TOS 7.0.1105 (x86) Official Release Update

Post by RyanYang »

snapsh0t wrote: 05 Aug 2026, 16:15
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.
To contact our team, please send email to following addresses, remember to replace (at) with @
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement)
User avatar
Gremlin
Gold Member
Posts: 1719
Joined: 02 Dec 2022, 22:31
Great Britain

Re: TOS 7.0.1105 (x86) Official Release Update

Post by Gremlin »

Does update to .1105 rewrite the usb initboot to be compatible with TOS7 (ie default boot to TOS7) without following the older procedure.
F5-221 TOS7.0.1130 - 4x4TB (Ironwolf) Traid
F2-424 TOS7.0.1130 - 2x500GB nvme (P3) Traid, 2x6TB HDD (HGST) Traid
F2-221 TOS7.0.1130 - 1x3TB Ext4, 1x4TB Btrfs
F2-425+ TOS7.0.1130 - 2x500GB nvme (P3) Traid, 2x6TB HDD (EXOS) Traid
User avatar
TMzethar
TM Support
Posts: 3021
Joined: 27 Oct 2020, 16:43

Re: TOS 7.0.1105 (x86) Official Release Update

Post by TMzethar »

Gremlin wrote: 05 Aug 2026, 21:28 Does update to .1105 rewrite the usb initboot to be compatible with TOS7 (ie default boot to TOS7) without following the older procedure.
Please note that upgrading or updating TOS 7 will not overwrite the USB Initboot.
So if you need to reinstall the TOS 7, you'll have to manually flash the USB Initboot to the TOS 7‑specific version.
viewtopic.php?t=6433
To contact our team, please send email to following addresses, remember to replace (at) with @:
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
User avatar
nitzer71
Posts: 29
Joined: 08 Jul 2026, 08:12
Switzerland

Re: TOS 7.0.1105 (x86) Official Release Update

Post by nitzer71 »

After upgrading to TOS 7.0.1105, I noticed the globalsearch service eventually starts consuming around 120–150% CPU continuously. Restarting the GlobalSearch service temporarily resolves it, but the issue returns after several hours. The only indexed directory configured is the default user home folder, which contains only 17 files (~132 KB). Media Indexing is disabled.
User avatar
nitzer71
Posts: 29
Joined: 08 Jul 2026, 08:12
Switzerland

Re: TOS 7.0.1105 (x86) Official Release Update

Post by nitzer71 »

nitzer71 wrote: 06 Aug 2026, 09:49 After upgrading to TOS 7.0.1105, I noticed the globalsearch service eventually starts consuming around 120–150% CPU continuously. Restarting the GlobalSearch service temporarily resolves it, but the issue returns after several hours. The only indexed directory configured is the default user home folder, which contains only 17 files (~132 KB). Media Indexing is disabled.
Update: I restarted the GlobalSearch service and CPU usage dropped back to normal, but after several hours the issue returned.

The configured indexed directory is only the default user home folder and shows "Completed". The GlobalSearch database remains only 32 KB.

I checked the process and it appears to have a fanotify filesystem watcher open. During high CPU usage, strace shows repeated failed reads:

Code: Select all

read(8, ..., 256) = -1 EINVAL (Invalid argument)
repeated thousands of times.

This seems more like a GlobalSearch filesystem watcher loop than a normal indexing operation. Could this be related to the TOS 7.0.1105 update?
Post Reply

Return to “Update Notice”