Yes. Thanks for suggesting that.
Hope that link provides some additional help. See also @DDPS link above as well.
1 Like
@Arindal In my engagement with QNAP over the past week concerning the new Roon system requirements, they have not indicated or suggested that switching to QuTS would be the answer to the issue of glibc. In fact, QNAP indicated to me that they cannot even guarantee that a future update will address the issue. This is what QNAP stated to me:
So, it sucks all round. A big thumbs down 
What model is your NAS.
Indeed. These are the only non-Enterprise/Business models that support it:
Doesn’t look like a solution for most people
1 Like
I’m using the HS-264 model.
1 Like
Then you could switch to QuTS Hero, but it would require to completely rebuild your NAS. This sounds much worse than sticking to the Docker solution.
There are good things happening:
1 Like
QNAP´s own definition of a home NAS is a bit weird. There are a lot of hero-capable models filed under business NAS, which you would typically expect to be used for private purpose, examples:
Same is true to the fanless and all-flash devices not listed here, which make a lot of sense for roon in my opinion. Does not change the fact that there are probably a lot of legacy units being used as roon core out there, which are not QuTS-compatible.
2 Likes
I’m not an IT person, so rebuilding a NAS is problematic; I will not be doing that. I will wait for an official communication from Roon on the way forward.
OK, strange, but that’s still just 7 models. And the switch to QuTS still requires backup up, tearing down the whole NAS, and rebuilding from scratch. Since those who are most scared of the Docker switch are the “not so technical” users, this does not sound like a great solution for them even if they technically could. Any NAS that supports QuTS also supports Docker…
Plus the designated home units, plus some fanless/all-flash models, so like 10 of the current line-up. As their entry-level products are all out of the picture due to incompatible CPU, it basically leaves maybe 2 or 3 units which are declared non-QuTS, but Roon-capable. And lots of legacy products, of course.
Agreed, that probably will be the easiest solution. Not sure, though, if Docker will support USB-Audio and HDMI-Out, though, which were features heavily promoted by QNAP for their ´Multimedia-NAS´.
I almost wish that nobody had discovered or mentioned that moving to QuTS is possibly an option. I believe it’s just clouding the discussion.
This is a personal opinion but I believe that asking people to move to Docker is acceptable as long as:
- Roon provides outstanding documentation including step-by-step instructions with pictures
- All functionality is carried forwards inclusive of USB and HDMI output
- Performance does not drop and memory consumption does not increase
In 2026, I don’t think we can or should have a discussion about how Docker performs worse than native. Docker shares the kernel with the underlying OS and, with bind mounts, has essentially direct access to the file system. Docker is adopted massively across the industry. People are even using it, many without knowing, in Roon Extension Manager scenarios.
We should think about moving to Docker as something more akin to “I have to uninstall and reinstall Roon” than an earth-shattering situation.
Telling any Roon user they have to move to QuTS should not be an option. It’s a completely different OS with a different underlying file system. It requires finding a place to put all of your data, doing the transition, and re-installing all of your data. If a bunch of people try this, some of them will lose data. Period. On top of that, it is known to be more resource intensive including requiring more RAM. You can’t predict how your system will work after you “upgrade” to it so you’d be taking big risk and hoping that the end result is OK.
And, by the way @Arindal, I’ve seen indications that QuTS has the latest gclib but I have not seen anything to indicate that it has the right drivers or anything else to support your HDMI use case. Maybe it does and you know that already but before you go “upgrade” or even truly consider that as option, you’ll want to know.
So what’s my point? I don’t want to get in the way of anyone moving to QuTS. If that’s something you want to do then, by all means, have at it. But let’s please not position it as a viable option for Roon to ask of users. It’s not.
11 Likes
Enabling HDMI is handled the same way as under QTS, and it worked the same way for Hybrid Disc Station (admittingly, I never tried roon or Plex).
I absolutely agree to all of your concerns. I would not take the decision to move to another OS lightly (in my case, moving 12+TB of data is anyways pain in…, so I am sitting here waiting). And I am also skeptical when it comes to QuTS hero on overly lean QNAP machines, which do not allow upgrading (additional RAM or SSD for caching).
Can people please stop proposing migrating to ZFS as a realistic solution to keep a piece of music management software working 
2 Likes
Nobody in this thread has said anything about ZFS. However, QuTS Hero does include it, and I think that most everybody agrees that the idea of switching to that is not practical for most people. Frankly, that is why I didn’t bring it up originally when I started this thread. Most everybody here in this thread is on the same page with you.
1 Like
QuTS is indivisible from ZFS. It doesn’t ship with any other file system.
1 Like
True. And while QuTS Hero’s implementation of OpenZFS can be a little weird, by and large it works well and for some of us who work with ZFS in the enterprise word, it is welcome territory to manage on your home NAS. (I have a TVS-h1688x).
Yes QuTS Hero 5.2.9 doesn’t work with the new Roon server. Hero 6.0 is still in public beta and while it’s probably pretty close to release, I haven’t upgraded to it yet. So i don’t know if glib is updated.
I believe I indicated my understanding of that in the post you responded to.
OK. I don’t understand why you said this though:
Anyway, nbd.
I wrote this, but then I looked at your name and, well, if you’re a fan, then what I said stands. But if you’re the man, himself, then you can do and say whatever you want, sir.
Look at that NAS! What an absolute beast! Do you actually run the RoonOnNAS QNAP package on that? Or do you do what any self-respecting enterprise-admin-class user would do and run it in Docker already? 
I love ZFS. I use it on a self-built TrueNAS box with a beefy processor and 128GB of RAM. I can teach the class on storage pools, datasets, snapshots, POSIX vs. ACL (including mixed mode, de-duplication, ARC, etc. ZFS is great for me and you, @Sevenfeet, but it’s not for the average consumer that buys a consumer-targeted NAS and is at the limits of their comfort zone getting a Roon package installed from a catalog.
At the risk of repeating myself …I believe that Roon (the company and its employees) and this community can support Synology and QNAP users in getting a Docker container stood up and working with the right documentation and container design. @Stephen_Shaw1 has been very gracious about exchanging a couple of private messages with me about the container design and I believe he’s making all the right choices.
With his container, and the right docs, I think it’s about 15 minutes of work to get the container stood up. The user forces Roon to do a backup, stops the current package, creates a folder/share on the NAS for the container to store stuff in, copies old backups to it and then uses the documentation to guide the install.
What you have, at the end of this, is your NAS still running the same operating system, everything working like it did. You don’t have to copy your data off and back. You don’t have to learn anything about ZFS or try to re-create your SMB shares or install your other software or anything. Moving to Hero is the move to ZFS and, for anyone that doesn’t already know and love it, or have a specific interest in it (and hardware that’s up to the task), it’s a bad choice.
But like I said, I love ZFS and am always up for chatting about it
2 Likes