Participating in the QuTS hero h6.0 Beta has been an eye-opening look into the future of ZFS storage. Testing this firmware feels like a shift from “solid storage” to “intelligent infrastructure.”
The first thing I noticed was the improved UI responsiveness. Operating the Web UI feels snappier, even when background ZFS tasks like snapshot replication are running. The system feels more composed under load, likely thanks to the kernel-mode SMB daemon, which has noticeably smoothed out high-throughput file transfers.
Security is where this build truly shines. I experimented with the Immutable Snapshots, and the peace of mind knowing that data is physically locked against modification or accidental deletion—even from a compromised admin account—is a game-changer for ransomware protection. Pairing this with FIDO2 Passkeys has made my login workflow both faster and significantly more secure, removing the friction of traditional 2FA while hardening the front door.
A standout “quality of life” addition is finally seeing Qtier on QuTS hero. Historically, we had to choose between ZFS’s data integrity and QTS’s automated tiering; now, having the ability to hot-swap data between NVMe and high-capacity HDDs automatically within a ZFS pool is the hybrid performance dream.
I also spent time with the High Availability (HA) Manager. While it requires two units, the active-passive failover felt much more refined than previous iterations. The new ACL 2.0 engine also deserves a mention—managing complex permissions on large directories used to be a chore, but it now feels instantaneous.
For a beta, it is remarkably stable, though I did encounter minor UI refreshes and vague log entries. However, the roadmap—especially the upcoming Ransomware Guard and on-prem AI integration—makes h6.0 feel like the most comprehensive update QNAP has released in years. It’s a bold step forward for anyone prioritizing data sovereignty and enterprise-grade resilience.
Switched 1 week ago….I cannot express my regret enough. QNAP has offered to look at it, but its so messed up, their remote support fails. I can only send them logs. Re-initialized twice, losing all my AI data, so not super thrilled with losing facial recognition data on 54,000+ photos.
Switched to ACL 2.0. Worst mistake of my life regarding IT. Nothing but headaches and instability. For the love of GOD DO NOT UPGRADE ACL…if you head my advice, you may have no issues at all. Or at least you will be able to revert your way out of this mess. From research I have done, numerous people are having this issue. I can confidently say its either their own apps or own OS. How do I know these things?
I removed all non approved hardware. (even though it worked for over a year flawlessly on 5.2.x). I am now removing approved hardware (such as the video card). I have removed all non qnap Software, and now, we start removing all qnap software we can. Qsync and Qftp are next on the chopping block.
What is the issue? After about 1 hour, file manager stops accessing files, shares go non responsive, and it is so bad the OS can’t even perform a shut down or restart if its been on for more than 40 minutes to 1 hour. and as mentioned, tried to get an SSH key so their techs can look around…their own remote support app is so broken it can’t execute that task correctly.
So in conclusion, I know have an 84 Terabyte paper weight because of this half baked beta. Its bad enough I am opting out of beta as soon as 6.0 stable comes out.
QNAP, your ACL 2.0 is pure IT nightmare fuel, and was rolled out long before it was ready.
For Reference I have a TS-1655 with 128GB of RAM, 2 Corel Edge TPU co-processors, and an NVIDIA card installed. Previously had a QNAP card with cache drives installed (pulled those already).
I am aware of the risks, but this was particularly terrible oversight. On the up side, for anyone having the same issue, I have found what seems to be the source of the problem. It is…drum roll….The Clamwin AV interaction with ACL 2.0. Been stable for a longer run than I have had all week. I re-introduced the AV to confirm, locked immediately.
I have been part of betas before, but very rarely have I seen one that breaks the entire system. Maybe I just wasn’t in the right betas.