Sorry, we do not fully understand the issue you are reporting at the moment. Could you please provide a more detailed description of the problem, or attach relevant screenshots, so that we can further analyze and investigate it?
TOS 7.0.0706 Beta (X86) is Released for Update
Re: TOS 7.0.0706 Beta (X86) is Released for Update
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)
Technical team: support(at)terra-master.com(for technical support)
Service team: service(at)terra-master.com(for purchasing, return, replacement, RMA service)
Re: TOS 7.0.0706 Beta (X86) is Released for Update
Based on the blktrace output you provided, we observed periodic SMART status queries (smartctl) accessing the hard drives to read SMART information. In addition, we also found disk access activities originating from the PostgreSQL database service and certain system background services (such as RAID-related processes and kernel worker threads).
These read and write operations may prevent the drives from entering sleep mode properly. However, based on the logs currently available, we are unable to determine which specific service or process is responsible for keeping the drives awake, nor can we confirm whether these activities are occurring continuously.
To further investigate the issue, please export a Debug log package via TOS Desktop → Technical Support → Feedback & Support and send it to us for analysis. After reviewing the logs, we will further examine whether there are any services or processes continuously accessing the drives and help identify the root cause of the hard drives not entering sleep mode properly.
Thank you for your cooperation and support.
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)
Technical team: support(at)terra-master.com(for technical support)
Service team: service(at)terra-master.com(for purchasing, return, replacement, RMA service)
Re: TOS 7.0.0706 Beta (X86) is Released for Update
Does this help?
Code: Select all
Adm1n@Therver2:~# blktrace -d /dev/sdb -o - | blkparse -i -
8,16 2 11 20.180150055 38957 D R 512 [smartctl]
8,16 2 12 20.182117652 38957 D R 512 [smartctl]
8,16 0 17 22.080487222 0 C N [0]
8,16 0 18 22.080635256 0 C R [0]
8,16 0 19 22.089429008 0 C R [0]
8,16 0 20 22.090010318 0 C R [0]
8,16 3 1 22.080302894 38962 D R 36 [smartctl]
8,16 3 2 22.080312256 39 C R [0]
8,16 3 3 22.080341269 38962 D N 0 [smartctl]
8,16 3 4 22.080499193 38962 D R 512 [smartctl]
8,16 3 5 22.087552751 38962 D R 512 [smartctl]
8,16 3 6 22.089525998 38962 D R 512 [smartctl]
8,16 0 21 30.259708212 38997 D R 36 [smartctl]
8,16 0 22 30.259718482 17 C R [0]
8,16 0 23 30.259750581 38997 D N 0 [smartctl]
8,16 0 24 30.259897966 0 C N [0]
8,16 0 25 30.259915331 38997 D R 512 [smartctl]
8,16 0 26 30.260083146 0 C R [0]
8,16 0 27 30.267216081 38997 D R 512 [smartctl]
8,16 0 28 30.269186699 0 C R [0]
8,16 0 29 30.269264256 38997 D R 512 [smartctl]
8,16 0 30 30.269810943 0 C R [0]
8,16 0 31 40.346041072 39035 D R 36 [smartctl]
8,16 0 32 40.346050428 17 C R [0]
8,16 0 33 40.346079412 39035 D N 0 [smartctl]
8,16 0 34 40.346199043 0 C N [0]
8,16 0 35 40.346209740 39035 D R 512 [smartctl]
8,16 0 36 40.346340092 0 C R [0]
8,16 0 37 40.353403357 39035 D R 512 [smartctl]
8,16 0 38 40.355344952 0 C R [0]
8,16 0 39 40.355428622 39035 D R 512 [smartctl]
8,16 0 40 40.355869706 0 C R [0]
8,16 1 13 41.189286450 39040 D R 36 [smartctl]
8,16 1 14 41.189297603 27 C R [0]
8,16 1 15 41.189329881 39040 D N 0 [smartctl]
8,16 0 41 41.189476808 0 C N [0]
8,16 1 16 41.189490662 39040 D R 512 [smartctl]
8,16 0 42 41.189620385 0 C R [0]
8,16 1 17 41.196831694 39040 D R 512 [smartctl]
8,16 0 43 41.198661538 0 C R [0]
8,16 1 18 41.198760790 39040 D R 512 [smartctl]
8,16 0 44 41.199248043 0 C R [0]
8,16 0 45 50.430615756 0 C N [0]
8,16 0 46 50.430797079 0 C R [0]
8,16 0 47 50.439864044 0 C R [0]
8,16 0 48 50.440409827 0 C R [0]
8,16 3 7 50.430423274 39063 D R 36 [smartctl]
8,16 3 8 50.430433923 39 C R [0]
8,16 3 9 50.430465720 39063 D N 0 [smartctl]
8,16 3 10 50.430629392 39063 D R 512 [smartctl]
8,16 3 11 50.438023509 39063 D R 512 [smartctl]
8,16 3 12 50.439902386 39063 D R 512 [smartctl]
8,16 1 19 60.298115958 39098 D R 36 [smartctl]
8,16 1 20 60.298128771 27 C R [0]
8,16 1 21 60.298162978 39098 D N 0 [smartctl]
8,16 0 49 60.298311740 0 C N [0]
8,16 1 22 60.298324169 39098 D R 512 [smartctl]
8,16 0 50 60.298454723 0 C R [0]
8,16 1 23 60.305448312 39098 D R 512 [smartctl]
8,16 0 51 60.307332931 0 C R [0]
8,16 1 24 60.307433601 39098 D R 512 [smartctl]
8,16 0 52 60.307911666 0 C R [0]
8,16 0 53 60.517794907 0 C N [0]
8,16 0 54 60.518012235 0 C R [0]
8,16 0 55 60.526857745 0 C R [0]
8,16 0 56 60.527392787 0 C R [0]
8,16 1 25 60.517586925 39104 D R 36 [smartctl]
8,16 1 26 60.517598180 27 C R [0]
8,16 1 27 60.517628308 39104 D N 0 [smartctl]
8,16 1 28 60.517840985 39104 D R 512 [smartctl]
8,16 1 29 60.525035477 39104 D R 512 [smartctl]
8,16 1 30 60.526894105 39104 D R 512 [smartctl]
F2-425 Plus, 16GB RAM, 2 x 500GB WD SN700 EXT4 RAID1, 2 x 18TB WD Red Pro EXT4 RAID1, TOS 7.0.<latest>
Re: TOS 7.0.0706 Beta (X86) is Released for Update
snapsh0t wrote: ↑14 Jun 2026, 06:15Does this help?Code: Select all
Adm1n@Therver2:~# blktrace -d /dev/sdb -o - | blkparse -i - 8,16 2 11 20.180150055 38957 D R 512 [smartctl] 8,16 2 12 20.182117652 38957 D R 512 [smartctl] 8,16 0 17 22.080487222 0 C N [0] 8,16 0 18 22.080635256 0 C R [0] 8,16 0 19 22.089429008 0 C R [0] 8,16 0 20 22.090010318 0 C R [0] 8,16 3 1 22.080302894 38962 D R 36 [smartctl] 8,16 3 2 22.080312256 39 C R [0] 8,16 3 3 22.080341269 38962 D N 0 [smartctl] 8,16 3 4 22.080499193 38962 D R 512 [smartctl] 8,16 3 5 22.087552751 38962 D R 512 [smartctl] 8,16 3 6 22.089525998 38962 D R 512 [smartctl] 8,16 0 21 30.259708212 38997 D R 36 [smartctl] 8,16 0 22 30.259718482 17 C R [0] 8,16 0 23 30.259750581 38997 D N 0 [smartctl] 8,16 0 24 30.259897966 0 C N [0] 8,16 0 25 30.259915331 38997 D R 512 [smartctl] 8,16 0 26 30.260083146 0 C R [0] 8,16 0 27 30.267216081 38997 D R 512 [smartctl] 8,16 0 28 30.269186699 0 C R [0] 8,16 0 29 30.269264256 38997 D R 512 [smartctl] 8,16 0 30 30.269810943 0 C R [0] 8,16 0 31 40.346041072 39035 D R 36 [smartctl] 8,16 0 32 40.346050428 17 C R [0] 8,16 0 33 40.346079412 39035 D N 0 [smartctl] 8,16 0 34 40.346199043 0 C N [0] 8,16 0 35 40.346209740 39035 D R 512 [smartctl] 8,16 0 36 40.346340092 0 C R [0] 8,16 0 37 40.353403357 39035 D R 512 [smartctl] 8,16 0 38 40.355344952 0 C R [0] 8,16 0 39 40.355428622 39035 D R 512 [smartctl] 8,16 0 40 40.355869706 0 C R [0] 8,16 1 13 41.189286450 39040 D R 36 [smartctl] 8,16 1 14 41.189297603 27 C R [0] 8,16 1 15 41.189329881 39040 D N 0 [smartctl] 8,16 0 41 41.189476808 0 C N [0] 8,16 1 16 41.189490662 39040 D R 512 [smartctl] 8,16 0 42 41.189620385 0 C R [0] 8,16 1 17 41.196831694 39040 D R 512 [smartctl] 8,16 0 43 41.198661538 0 C R [0] 8,16 1 18 41.198760790 39040 D R 512 [smartctl] 8,16 0 44 41.199248043 0 C R [0] 8,16 0 45 50.430615756 0 C N [0] 8,16 0 46 50.430797079 0 C R [0] 8,16 0 47 50.439864044 0 C R [0] 8,16 0 48 50.440409827 0 C R [0] 8,16 3 7 50.430423274 39063 D R 36 [smartctl] 8,16 3 8 50.430433923 39 C R [0] 8,16 3 9 50.430465720 39063 D N 0 [smartctl] 8,16 3 10 50.430629392 39063 D R 512 [smartctl] 8,16 3 11 50.438023509 39063 D R 512 [smartctl] 8,16 3 12 50.439902386 39063 D R 512 [smartctl] 8,16 1 19 60.298115958 39098 D R 36 [smartctl] 8,16 1 20 60.298128771 27 C R [0] 8,16 1 21 60.298162978 39098 D N 0 [smartctl] 8,16 0 49 60.298311740 0 C N [0] 8,16 1 22 60.298324169 39098 D R 512 [smartctl] 8,16 0 50 60.298454723 0 C R [0] 8,16 1 23 60.305448312 39098 D R 512 [smartctl] 8,16 0 51 60.307332931 0 C R [0] 8,16 1 24 60.307433601 39098 D R 512 [smartctl] 8,16 0 52 60.307911666 0 C R [0] 8,16 0 53 60.517794907 0 C N [0] 8,16 0 54 60.518012235 0 C R [0] 8,16 0 55 60.526857745 0 C R [0] 8,16 0 56 60.527392787 0 C R [0] 8,16 1 25 60.517586925 39104 D R 36 [smartctl] 8,16 1 26 60.517598180 27 C R [0] 8,16 1 27 60.517628308 39104 D N 0 [smartctl] 8,16 1 28 60.517840985 39104 D R 512 [smartctl] 8,16 1 29 60.525035477 39104 D R 512 [smartctl] 8,16 1 30 60.526894105 39104 D R 512 [smartctl]
Code: Select all
smartctl -H /dev/sdb
smartctl -A /dev/sdb | grep -E "^(5|187|193|197|198) "
hdparm -B /dev/sdbRe: TOS 7.0.0706 Beta (X86) is Released for Update
My lack of Linux skills nearly caught me out but I realised I needed to repeat this for sda as well as sdb as they're the two HDDs in RAID1.Phil wrote: ↑14 Jun 2026, 09:31Please enter the above command in the terminal and then tell us the output.Code: Select all
smartctl -H /dev/sdb smartctl -A /dev/sdb | grep -E "^(5|187|193|197|198) " hdparm -B /dev/sdb
Code: Select all
Adm1n@Therver2:~# smartctl -H /dev/sdb
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 READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
Adm1n@Therver2:~# smartctl -A /dev/sdb | grep -E "^(5|187|193|197|198) "
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 396
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
Adm1n@Therver2:~# hdparm -B /dev/sdb
/dev/sdb:
APM_level = 254
Adm1n@Therver2:~# smartctl -H /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 READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
Adm1n@Therver2:~# smartctl -A /dev/sda | grep -E "^(5|187|193|197|198) "
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 394
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
Adm1n@Therver2:~# hdparm -B /dev/sda
/dev/sda:
APM_level = 254
Adm1n@Therver2:~#
F2-425 Plus, 16GB RAM, 2 x 500GB WD SN700 EXT4 RAID1, 2 x 18TB WD Red Pro EXT4 RAID1, TOS 7.0.<latest>
Re: TOS 7.0.0706 Beta (X86) is Released for Update
We don’t have enough information to understand the situation. Could you please describe the details?
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)
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
-
storageninja
- Posts: 64
- Joined: 06 Aug 2025, 14:32

Re: TOS 7.0.0706 Beta (X86) is Released for Update
Running TOS7 beta on two F4-SSD units, both same firmware, and found a few things that reproduce consistently on both. Posting here so TerraMaster support/devs can pick it up. Happy to provide more info if needed.
---
Bug 1 - iniparse crashes on every boot (both units)
Every boot, a bunch of iniparse processes segfault during early userspace init. Same crash on both units, different hardware, so it's not specific to one config. The kernel has CET/IBT enabled and this binary is jumping into non-executable memory.
Both units produce the same crash pattern with the same code bytes. The binary needs to be recompiled with proper IBT-compatible indirect calls, or CET compatibility needs to be checked before release.
---
Bug 2 - md9 (OS array) always starts degraded at boot
On both units, md9 boots with 1 out of 2 mirrors and immediately starts a recover. It completes in a few seconds so the array ends up fine, but it shouldn't be doing this on every clean boot.
Current array state after boot (both units clean):
Looks like the initramfs is assembling the array before the second NVMe is ready. The udev settle timeout might need adjusting for this platform?
---
Bug 3 - journald.conf has invalid size values, logging limits ignored
Both units log this on every boot:
The config is using percentage values for SystemMaxUse and RuntimeMaxUse but systemd 249 (which TOS7 ships) does not support percentage syntax for these settings. The values are silently ignored and journal sizing falls back to defaults. Should be fixed to use absolute values like 1G or 2G.
---
All three reproduce on every boot across both units. Let me know if you need full dmesg dumps or any other info.
---
Bug 1 - iniparse crashes on every boot (both units)
Every boot, a bunch of iniparse processes segfault during early userspace init. Same crash on both units, different hardware, so it's not specific to one config. The kernel has CET/IBT enabled and this binary is jumping into non-executable memory.
Code: Select all
[ 11.925605] iniparse[581]: segfault at 7f69c1d32413 ip 00007f69c1d32413 sp 00007fffdb5ae840 error 15 in iniparse[2bd413,7f69c1a75000+2be000] likely on CPU 2 (core 2, socket 0)
[ 11.925624] Code: ff d5 59 5e 5f 5d 6a 05 5a 6a 0a 58 0f 05 41 ff e5 5d e8 3c ff ff ff 2f 70 72 6f 63 2f 73 65 6c 66 2f 65 78 65 00 00 01 00 00 <e8> 4a 00 00 00 83 f9 49 75 44 53 57 48 8d 4c 37 fd 5e 56 5b eb 2f
[ 11.925912] iniparse[582]: segfault at 7f92cf7d9413 ip 00007f92cf7d9413 sp 00007ffedac41e20 error 15 in iniparse[2bd413,7f92cf51c000+2be000] likely on CPU 3 (core 3, socket 0)
[ 11.927788] iniparse[583]: segfault at 7fb2827ae413 ip 00007fb2827ae413 sp 00007fffe8cc3f10 error 15 in iniparse[2bd413,7fb2824f1000+2be000] likely on CPU 2 (core 2, socket 0)
[ 11.928518] iniparse[586]: segfault at 7fadc650f413 ip 00007fadc650f413 sp 00007ffea2b771d0 error 15 in iniparse[2bd413,7fadc6252000+2be000] likely on CPU 3 (core 3, socket 0)
[ 11.928847] iniparse[584]: segfault at 7f7952e37413 ip 00007f7952e37413 sp 00007ffd3d900b40 error 15 in iniparse[2bd413,7f7952b7a000+2be000] likely on CPU 0 (core 0, socket 0)
[ 11.930098] iniparse[588]: segfault at 7f2d13575413 ip 00007f2d13575413 sp 00007ffed9ee28c0 error 15 in iniparse[2bd413,7f2d132b8000+2be000] likely on CPU 0 (core 0, socket 0)
[ 11.930776] iniparse[589]: segfault at 7f2b09508413 ip 00007f2b09508413 sp 00007fffad4d29f0 error 15 in iniparse[2bd413,7f2b0924b000+2be000] likely on CPU 2 (core 2, socket 0)
[ 11.930996] iniparse[590]: segfault at 7fe97a3b7413 ip 00007fe97a3b7413 sp 00007ffc58c686c0 error 15 in iniparse[2bd413,7fe97a0fa000+2be000] likely on CPU 0 (core 0, socket 0)
[ 11.931652] iniparse[591]: segfault at 7f58aa714413 ip 00007f58aa714413 sp 00007fffb63cebd0 error 15 in iniparse[2bd413,7f58aa457000+2be000] likely on CPU 0 (core 0, socket 0)
[ 11.932167] iniparse[593]: segfault at 7f99d160a413 ip 00007f99d160a413 sp 00007ffec1763850 error 15 in iniparse[2bd413,7f99d134d000+2be000] likely on CPU 2 (core 2, socket 0)
---
Bug 2 - md9 (OS array) always starts degraded at boot
On both units, md9 boots with 1 out of 2 mirrors and immediately starts a recover. It completes in a few seconds so the array ends up fine, but it shouldn't be doing this on every clean boot.
Code: Select all
[ 3.404811] md: md9 stopped.
[ 3.451769] md/raid1:md9: active with 1 out of 2 mirrors
[ 3.452809] md9: detected capacity change from 0 to 15990784
[ 5.013596] md: recover of RAID array md9
[ 8.132323] md: md9: recover done.
Code: Select all
/dev/md9:
Version : 1.2
Raid Level : raid1
Array Size : 7995392 (7.63 GiB 8.19 GB)
Raid Devices : 2
Total Devices : 2
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
---
Bug 3 - journald.conf has invalid size values, logging limits ignored
Both units log this on every boot:
Code: Select all
[ 11.401837] systemd-journald[404]: /etc/systemd/journald.conf:26: Failed to parse size value, ignoring: 90%
[ 11.401837] systemd-journald[404]: /etc/systemd/journald.conf:30: Failed to parse size value, ignoring: 90%
---
All three reproduce on every boot across both units. Let me know if you need full dmesg dumps or any other info.
Re: TOS 7.0.0706 Beta (X86) is Released for Update
Re Bug 1: See my post of June 11 on this thread. So far no response.
Re Bug 2: I think it has been like this forever
F5-221 TOS7.0.0777 - 4x4TB (Ironwolf) Traid
F2-424 TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (HGST) Traid
F2-221 TOS7.0.0777 - 1x3TB Ext4, 1x4TB Btrfs
F2-425+ TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (EXOS) Traid
F2-424 TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (HGST) Traid
F2-221 TOS7.0.0777 - 1x3TB Ext4, 1x4TB Btrfs
F2-425+ TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (EXOS) Traid
-
storageninja
- Posts: 64
- Joined: 06 Aug 2025, 14:32

Re: TOS 7.0.0706 Beta (X86) is Released for Update
Re: TOS 7.0.0706 Beta (X86) is Released for Update
Based on the dmesg you provided, the main problem is that the `iniparse` process repeatedly experiences segmentation faults (SegFaults), while hardware (USB, network card) recognition is normal.
- Crashing process PIDs: 581, 583, 584, 593, 594
- Error code `error 15`: A user-space program attempted to execute an instruction from an illegal address
**Try to find out who is calling `iniparse`**
grep -r "iniparse" /etc/ /usr/lib/systemd/ /var/spool/cron/ 2>/dev/null
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)
Technical team: support(at)terra-master.com(for technical support)
Service team: service(at)terra-master.com(for purchasing, return, replacement, RMA service)

