QuTS 6 Beta - Disk suspend now broken/programmatically impossible

Weedy · February 16, 2026, 8:16pm

I have taken steps to ensure nothing touches the spinning rust except access to the shared folders on the spinning rust.

# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath]
md321 : active raid1 nvme0n1p5[2] nvme1n1p5[0]
      31868416 blocks super 1.0 [2/2] [UU]
      bitmap: 0/1 pages [0KB], 65536KB chunk

md13 : active raid1 sdb4[129](F) sda4[128](F) nvme1n1p4[0] nvme0n1p4[1]
      458880 blocks super 1.0 [4/2] [UU__]
      bitmap: 1/1 pages [4KB], 65536KB chunk

md9 : active raid1 sdb1[129](F) sda1[128](F) nvme1n1p1[0] nvme0n1p1[1]
      530048 blocks super 1.0 [4/2] [UU__]
      bitmap: 1/1 pages [4KB], 65536KB chunk

unused devices: <none>

[admin@TheVault weedy]# zpool status
  pool: zpool1
 state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
        still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(7) for details.
  scan: scrub repaired 0 in 0 days 00:01:49 with 0 errors on Tue Feb  3 04:34:51 2026
 prune: last pruned 0 entries, 0 entries are pruned ever
        total pruning count #43, avg. pruning rate = 0 (entry/sec)
expand: none requested
 ztier: [reloc] none requested
        [smart] none requested
config:

        NAME                                      STATE     READ WRITE CKSUM
        zpool1                                    ONLINE       0     0     0
          mirror-0                                ONLINE       0     0     0
            qzfs/enc_0/disk_0x1_S63XNX0T125223_3  ONLINE       0     0     0
            qzfs/enc_0/disk_0x2_S63XNX0T131734_3  ONLINE       0     0     0

errors: No known data errors

  pool: zpool2
 state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
        still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(7) for details.
  scan: scrub repaired 0 in 0 days 02:15:48 with 0 errors on Tue Feb  3 06:48:51 2026
 prune: last pruned 0 entries, 0 entries are pruned ever
        total pruning count #43, avg. pruning rate = 0 (entry/sec)
expand: none requested
 ztier: [reloc] none requested
        [smart] none requested
config:

        NAME                                        STATE     READ WRITE CKSUM
        zpool2                                      ONLINE       0     0     0
          mirror-0                                  ONLINE       0     0     0
            qzfs/enc_0/disk_0x3_5000C500E64A8A3A_3  ONLINE       0     0     0
            qzfs/enc_0/disk_0x4_5000C500E64A2AB0_3  ONLINE       0     0     0

errors: No known data errors

  pool: zpoolExt2
 state: ONLINE
  scan: none requested
 prune: never
expand: none requested
 ztier: [reloc] none requested
        [smart] none requested
config:

        NAME                                        STATE     READ WRITE CKSUM
        zpoolExt2                                   ONLINE       0     0     0
          mirror-0                                  ONLINE       0     0     0
            qzfs/enc_0/disk_0x1_S63XNX0T125223_2    ONLINE       0     0     0
            qzfs/enc_0/disk_0x2_S63XNX0T131734_2    ONLINE       0     0     0
            qzfs/enc_0/disk_0x3_5000C500E64A8A3A_2  ONLINE       0     0     0
            qzfs/enc_0/disk_0x4_5000C500E64A2AB0_2  ONLINE       0     0     0

errors: No known data errors

I don’t remember having 3 pools in QuTS 5.

[admin@TheVault weedy]# fatrace |grep '/mnt/sync'
qboost.cgi(4931): RCO /mnt/sync/.config/passwd
qboost.cgi(4931): RCO /mnt/sync/.config/group
qboost.cgi(4931): RCO /mnt/sync/.config/uLinux.conf
qboost.cgi(4931): O   /mnt/sync/.config/qboost/qboost_schedule.conf
qboost.cgi(4931): CO  /mnt/sync/.config/qboost/qboost_schedule.conf
qboost.cgi(4931): RCO /mnt/sync/.config/uLinux.conf
qboost.cgi(4931): RCO /mnt/sync/.config/uLinux.conf
qboost.cgi(4931): CO  /mnt/sync/.config/qboost/qboost_schedule.conf
qboost.cgi(4932): RCO /mnt/sync/.config/passwd
qboost.cgi(4931): RO  /mnt/sync/.config/uLinux.conf
qboost.cgi(4931): C   /mnt/sync/.config/uLinux.conf
qboost.cgi(4931): CO  /mnt/sync/.config/qboost/qboost_schedule.conf
qboost.cgi(4932): RCO /mnt/sync/.config/passwd
qboost.cgi(4931): RCO /mnt/sync/.config/syslog_server.conf
qboost.cgi(4931): CO  /mnt/sync/.config/qboost/qboost_schedule.conf
qboost.cgi(4932): RCO /mnt/sync/.config/group
qboost.cgi(4931): CO  /mnt/sync/.config/radius_global.conf
qboost.cgi(4931): CO  /mnt/sync/.config/qboost/qboost_schedule.conf
qboost.cgi(4931): O   /mnt/sync/.config/uLinux.conf
qboost.cgi(4931): R   /mnt/sync/.config/uLinux.conf
qboost.cgi(4931): C   /mnt/sync/.config/uLinux.conf
qboost.cgi(4931): O   /mnt/sync/.config/qboost/qboost_schedule.conf
qboost.cgi(4931): C   /mnt/sync/.config/qboost/qboost_schedule.conf
qboost.cgi(4931): CO  /mnt/sync/.config/qboost/qboost_schedule.conf
qboost.cgi(4931): RCO /mnt/sync/.config/uLinux.conf
qboost.cgi(4931): CO  /mnt/sync/.config/qboost/qboost_schedule.conf
manaRequest.cgi(4933): RCO /mnt/sync/.config/passwd
manaRequest.cgi(4933): RCO /mnt/sync/.config/group
manaRequest.cgi(4933): RCO /mnt/sync/.config/BOOT.conf
manaRequest.cgi(4933): RCO /mnt/sync/.config/uLinux.conf
appRequest.cgi(4934): RCO /mnt/sync/.config/passwd
appRequest.cgi(4934): RCO /mnt/sync/.config/group
appRequest.cgi(4934): RCO /mnt/sync/.config/BOOT.conf
appRequest.cgi(4934): RCO /mnt/sync/.config/uLinux.conf
sh(4979): RCO /mnt/sync/.config/passwd
gpuhal_app(4981): RCO /mnt/sync/.config/.gpuconf/assign_list
gpuhal_app(4981): RCO /mnt/sync/.config/.gpuconf/qts_blacklist
gpuhal_app(4981): RCO /mnt/sync/.config/.gpuconf/assign_list
unknown(4981): RCO /mnt/sync/.config/.gpuconf/assign_list
unknown(4981): RCO /mnt/sync/.config/.gpuconf/assign_list
appRequest.cgi(4934): RCO /mnt/sync/.config/uLinux.conf
unknown(4996): RCO /mnt/sync/.config/passwd
unknown(4997): RCO /mnt/sync/.config/.gpuconf/assign_list
unknown(4997): RCO /mnt/sync/.config/.gpuconf/qts_blacklist
unknown(5005): RCO /mnt/sync/.config/passwd
unknown(5006): RCO /mnt/sync/.config/.gpuconf/assign_list
unknown(5006): RCO /mnt/sync/.config/.gpuconf/qts_blacklist
unknown(4997): RCO /mnt/sync/.config/uLinux.conf
appRequest.cgi(4934): RCO /mnt/sync/.config/uLinux.conf
unknown(5006): RCO /mnt/sync/.config/uLinux.conf
qpkg_cli(5013): RCO /mnt/sync/.config/uLinux.conf
qpkg_cli(5013): RCO /mnt/sync/.config/.qos_config/users/admin/config
qpkg_cli(5013): O   /mnt/sync/.config/BOOT.conf
qpkg_cli(5013): R   /mnt/sync/.config/BOOT.conf
qpkg_cli(5013): C   /mnt/sync/.config/BOOT.conf
qpkg_cli(5013): O   /mnt/sync/.config/3rd_pkg_v2.conf
qpkg_cli(5013): R   /mnt/sync/.config/3rd_pkg_v2.conf
qpkg_cli(5013): C   /mnt/sync/.config/3rd_pkg_v2.conf
qpkg_cli(5013): O   /mnt/sync/.config/3rd_pkg_v2.conf
qpkg_cli(5013): R   /mnt/sync/.config/3rd_pkg_v2.conf
qpkg_cli(5013): C   /mnt/sync/.config/3rd_pkg_v2.conf
qpkg_cli(5013): O   /mnt/sync/.config/3rd_pkg_v2.conf
qpkg_cli(5013): RC  /mnt/sync/.config/3rd_pkg_v2.conf
qpkg_cli(5013): RCO /mnt/sync/.config/3rd_pkg_v2.conf
sh(5016): O   /mnt/sync/.config/passwd
sh(5016): R   /mnt/sync/.config/passwd
sh(5016): C   /mnt/sync/.config/passwd

< Continue to imagine log lines here. It's EVERY single QNAP system process. fatrace output is 2k lines even after grep filtering >

@SteveKo Can we do something about this?
I understand I’m not fully supported in my quest to sleep my HDDs when not in use. But I did try hard to keep EVERYTHING on the M.2s and only have my spinning rust for cold bulk storage.
I idled at like 6.5watts when the drives were sleeping.

Why have this setting? You have changed the way the OS works so it is literally impossible for the drives to sleep. EVER.

SteveKo · February 17, 2026, 10:28am

Thank you very much for your report!

I will submit this situation to our internal team for analysis. However, please be advised that our Taiwan headquarters is currently on the Lunar New Year holiday, so response and support times may be slightly longer than usual.

Once the holiday ends next week, I will follow up with the development team to confirm the details. Thank you for your patience and understanding.

Happy Lunar New Year!

SteveKo · February 18, 2026, 1:29am

Or, regarding your situation, we suggest that you open a support ticket so we can assist you with a more in-depth review of your advanced settings.

Thank you for your cooperation!

Support Portal: https://service.qnap.com/