TOS 7.0.1188 (x86) Official Release Update

[angelor]

You can refer to this post to reinstall the TOS system:
viewtopic.php?t=423
When initialization begins, you can press ESC to enter custom installation mode and manually upload the bootloader and the TOS installation package to install the TOS version you want.

ok, just a thing:
several weeks ago the Support told me to follow this post to install a specific (v1140) TOS7 version:
How to Flash a New USB Initboot for TOS on Windows PC？ viewtopic.php?t=6433
and they gave me the TOS7 v1140 installation package (.ins file)

Now you suggest me to follow another post for reinstalling the TOS system (viewtopic.php?t=423).

What is the difference?
For me, i would like to install (or downgrade) TOS7 to a specific version that I used and it was working (i.e. v1140) when i update to a new version (i.e. v1169) but there is a malfuncion/problem with this new version.
Thanks in advance

[snapsh0t]

There was never any chance that those temps were real. The NAS is only a few cm from my knee and I'd have heard the fan going flat out and probably have felt the case glowing......
The initial smartctl commands seem to show both the false and the real temps so I hope they make sense to you.

Code: Select all

Adm1n@NAS4:/# smartctl -a /dev/sda | grep -i temperature
194 Temperature_Celsius     0x0022   125   109   000    Old_age   Always       -       25
Adm1n@NAS4:/# smartctl -a /dev/sdb | grep -i temperature
194 Temperature_Celsius     0x0022   122   108   000    Old_age   Always       -       28
Adm1n@NAS4:/# smartctl -d sat -a /dev/sda
smartctl 7.5 2025-04-30 r5714 [x86_64-linux-6.12.63+] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red (CMR)
Device Model:     WDC WD30EFRX-68EUZN0
Serial Number:    WD-WCC4N3ZAKX0N
LU WWN Device Id: 5 0014ee 266af3104
Firmware Version: 82.00A82
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database 7.5/5706
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Sep 10 10:37:17 2026 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever 
                                        been run.
Total time to complete Offline 
data collection:                (39240) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine 
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 394) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x703d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   181   178   021    Pre-fail  Always       -       5925
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       679
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   096   096   000    Old_age   Always       -       3391
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       150
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       17
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       660
194 Temperature_Celsius     0x0022   125   109   000    Old_age   Always       -       25
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

The above only provides legacy SMART information - try 'smartctl -x' for more

Adm1n@NAS4:/# hdparm -H /dev/sda

/dev/sda:
SG_IO: bad/missing sense data, sb[]:  f0 00 0b 04 51 40 00 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 drive temperature (celsius) is:  under -20
 drive temperature in range:  yes
Adm1n@NAS4:/# 

[CursaYang]

Based on the current SMART data, both hard drives appear to be operating normally. The values 118, 122, and 125 shown in the logs are normalized SMART Attribute 194 values, rather than actual drive temperatures. The current temperatures of `/dev/sda` and `/dev/sdb` are 25°C and 28°C respectively, both within the normal range. We also found no reallocated sectors, pending sectors, offline uncorrectable sectors, or SATA CRC errors, and the SMART health status is reported as PASSED. Therefore, there is currently no evidence of overheating or a hardware health issue with the drives.

[CursaYang]

The post from technical support is for recreating the boot system — if your current boot system is not the TOS 7 one, you cannot install TOS 7 directly. The post I shared covers the steps for reinstalling the system. These two posts do not conflict, and you can combine them: first create the TOS 7 boot system, then follow the reinstallation procedure. When the initialization process begins, select custom installation mode and upload the 7.0.1140 installation package.

[OttO1916]

The system configuration does not include Rsync task configurations. Regarding the issue you mentioned, please check whether the current storage pool and volumes are in a normal state. You can also enter dmesg in the terminal to check whether there are any file system errors.
viewtopic.php?t=2575

Dmesg doesn't show any file system errors.
When rsync "crashes" i see the jobs disappearing, the data is being sent to the other side so the jobs keeps on running.
Also i see active rsync process(es). All data is copied and the job ends with error message in notifications stating to view the log.
That log cannot be opened because the job doesnt exist.

BUT: when i create new jobs without RunNow checked they don't disappear and start/end successfully on the planned time.
Also after a reboot the jobs are still there.
-> So creating AND running it seems to be the prob?

[dnetkach]

Hello TerraMaster Team,
Note: This report is compiled with the help of an AI Assistant to properly translate system diagnostic logs from Russian into English.
I have manually updated my TerraMaster F6-424 Max to the latest release TOS 7.0.1188. During my testing of the virtualization features, I encountered a critical issue: virtual machines completely freeze and lock up under disk I/O load.
System Specs:
• NAS Model: F6-424 Max
• OS Version: TOS 7.0.1188 [1]
• CPU: Intel Core i5-1235U
• RAM: 64 GB DDR5 (Micron)
• BIOS Version:** TM-v1.0.18_T726 (2024/09/20)
• Storage Configuration: Single SATA HDD running TOS, Docker, and VMs combined.

Investigation & The Bug:
To completely isolate any hardware or power management issues, I have manually configured the BIOS: Intel C-States limits are locked to C0/C1, Aggressive LPM Support for SATA is Disabled, and RAM Power Down Mode is Disabled. CPU temperatures stay perfectly fine at +46°C. The hardware itself is 100% stable.
The dmesg kernel trace reveals that the problem is a core architectural software bug in the TOS 7 storage subsystem. Regardless of the disk controller layout selected via the web interface (SATA or VirtIO), the hypervisor back-end wraps virtual disks into the SCST / LIO-ORG / TCM_Loopback iSCSI loop system. Under disk I/O pressure, this emulation stack fails to synchronize its cache, drops the mapping, and triggers a guest Kernel Panic.
Captured dmesg Logs (TOS 7.0.1188):
Here is the log snapshot taken right after the Windows VM froze on the 7.0.1188 build:
[13458.138341] dev[0000000071431d88]: Backstore name 'naa.5157e6a306e662cc' is too long for INQUIRY_MODEL...
[13458.330217] scsi host34: TCM_Loopback
[13458.330686]: scst: Attached to scsi34, channel 0, id 1, lun 0, type 0
[13458.330748] sd 34:0:1:0: [sdc] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB)
...
[13678.579251]: scst: Detached from scsi33, channel 0, id 1, lun 0, type 0
[13678.617313] sd 33:0:1:0: [sdb] Synchronizing SCSI cache
[13678.865301]: scst: Detached from scsi34, channel 0, id 1, lun 0, type 0
[13678.910343] sd 34:0:1:0: [sdc] Synchronizing SCSI cache
[13699.327676] x86/split lock detection: #AC: CPU 3/KVM/213612 took a split_lock trap at address: 0xfffff80034c48
Request for the Developers:
The TCM_Loopback driver module drops the device mapping throwing a Detached event while executing Synchronizing SCSI cache.
Please request the virtualization/storage engineering team to look into this thread. The backend of the VMs app should stop wrapping standard local virtual storage drives (.qcow2 / .raw images) into a problematic iSCSI target/loopback architecture when a single drive setup is detected, or fix the cache synchronization pipeline within the modified scst kernel module.
Thank you!

[snapsh0t]

Based on the current SMART data, both hard drives appear to be operating normally. The values 118, 122, and 125 shown in the logs are normalized SMART Attribute 194 values, rather than actual drive temperatures. The current temperatures of `/dev/sda` and `/dev/sdb` are 25°C and 28°C respectively, both within the normal range. We also found no reallocated sectors, pending sectors, offline uncorrectable sectors, or SATA CRC errors, and the SMART health status is reported as PASSED. Therefore, there is currently no evidence of overheating or a hardware health issue with the drives.

Yes, I could see that for myself but does it get us any closer to finding why the normalised temperatures are reported as if they were the real one in the debug syslog?

[Gremlin]

@snapsh0t:
The fact that someone has chosen to log a "Normalised Value" and then call it Celcius is suspicious of itself
Or maybe it's just a bad attempt at calculating Fahrenheit.