My first impression is very positive.
The UI feels much faster, smoother and more modern compared to previous QuTS hero versions. Pages load instantly, and there is no need to reload pages repeatedly to get them to render correctly. Overall usability and visual consistency are clearly improved.
Idle system resources
After boot and ~5 minutes idle:
CPU average usage: ~4.1%
Memory usage: ~6.37 GB / 15.41 GB
The system feels light and responsive, with no noticeable background spikes.
SMB performance testing
Single large file (~16 GB), Windows PC ↔ NAS via SMB:
PC → NAS: ~280 MB/s
NAS → PC: ~280 MB/s
Transfers were stable, with no disconnects, freezes, or retries. QuLog and notifications remained completely clean during and after transfers.
Snapshot sanity check
Created snapshot on shared folder Public
Snapshot status: Ready
Snapshot size: ~208 KB
Snapshot type: Crash consistent
Snapshot deletion: Successful
No warnings or errors recorded in QuLog
Snapshot operations were fast and behaved exactly as expected.
Logs & notifications
QuLog Center: clean (Warnings/Errors filter)
Notification Center: no unexpected alerts
Logout behavior: instant logout, no hanging (significant improvement)
One non-blocking, one-time log entry observed after boot:
“QuTS hero does not support this version of CacheMount. Go to App Center or the QNAP website to check for app updates…”
Notes:
Appeared only once
CacheMount is not available in App Center or on the QNAP website for this beta
No functional impact observed
Overall assessment
So far, QuTS hero 6.0 public beta feels mature, fast, and stable:
Noticeably improved UI responsiveness
Excellent SMB performance
Clean snapshot behavior
Clean logs
No regressions observed in basic daily operations
This is a very promising beta release.
Thank you for the opportunity to test QuTS hero 6.0. I will continue testing and provide additional feedback if anything new appears.
This is based on hands-on testing on my TS-264.
SMB transfers (~16 GB) were tested via \\IP\Public\TEST_COPY at ~280 MB/s both directions.
Snapshot create/delete was verified in Snapshot Manager (status Ready, ~208 KB).
One-time CacheMount compatibility message was observed in QuLog after boot.
If you need any specific detail, let me know.
Additional observations (QuTS hero 6.0 Public Beta)
During further testing I noticed two UI issues that may be worth investigating:
Logout freeze / hang
On at least one occasion, clicking Logout caused the web UI to hang/freeze instead of logging out normally. The session did not complete the logout flow and required manually closing the tab / reloading to recover.
Blank “Properties” window on folders
When I right-click a folder in File Station and choose Properties, the Properties dialog sometimes opens as a blank/empty window (no details shown). Closing and reopening may be needed, but the behavior is inconsistent.
Everything else in my test run remained stable; these two items look like UI/UX regressions rather than functional storage/network issues.
Additional observation in QuTS hero 6.0 beta:
The logout process works correctly when initiated manually by the user.
However, if the web interface is left open for a long period of time, the session timeout triggers an automatic logout attempt.
In this case, the UI hangs on the loading screen and does not redirect to the login page.
A manual browser refresh is required to complete the logout process.
Additionally, after a subsequent successful login, the web UI may load in a broken/unusable state, requiring another manual page refresh to render correctly.
The preload of “/usr/local/lib/libtrash.so” in generally is very bad practice!
I use Entware OPKG to customize and automate some processes. In my special case I modified HBS3 scriptes to turn on and turn off my external HDDs automatically. That are shell scripts, which use modified busybox 1.37 from Entware.
Before this beta my scripts worked without issues, but this beta uses a very dirty trick with preload of this “libtrash.so” in generally, before a shell script will be executed. That leads to errors by executing of nc (netcat from busybox):
/opt/bin/nc: /opt/lib/libc.so.6: version `GLIBC_2.33’ not found (required by /usr/local/lib/libtrash.so)
/opt/bin/nc: /opt/lib/libc.so.6: version `GLIBC_2.34’ not found (required by /usr/local/lib/libtrash.so)
I found a workaround for my special case and cleared LD_PRELOAD in my shell script. However, the use of such unclean techniques is really bad and doesn’t exactly reflect well on QNAP’s programming quality.
Hi, based on our internal analysis, this issue appears to be related to the toolchain update in version 6.0. Since your BusyBox wasn’t built using this specific toolchain, it is incompatible with the system’s libraries.
We believe this isn’t directly caused by PRELOAD itself; rather, PRELOAD forces the program to use our system libraries, which then exposes the mismatch.
We plan to release the necessary open-source components for this version after the official 6.0 release. At that time, you can try to rebuild your tools, which should theoretically resolve this issue. Thanks!
First impressions
Idle system resources
SMB performance testing
Snapshot sanity check
Logs & notifications
Overall assessment