Roon 1.8 does not see local folders on Linux ZFS drive [Resolved]

Dean_Bailey · February 25, 2021, 2:32am

Roon 1.8 build 764, no change. Still unable to access local data.

Bernard_Languillier · February 25, 2021, 9:19pm

There are good UI improvements in the recent dot releases so it’s nice to see the team working hard on addressing frequent criticisms. 1.8 is shaping out to be great.

But I still think that they are getting their priorities a bit mixed up. Discontinuity of service, be it for a minority or users, must always come first.

Dean_Bailey · February 25, 2021, 9:34pm

Absolutely. The UI performance has gotten rather nice with the 1.8 releases. Some questionable style changes, but I can totally live with that I’m seeing.

This right here. I’ve been getting more and more unhappy with the situation with every point fix release that doesn’t rectify this bug. I mean, sure, it is great they fixed all the ui borks that should have been caught by QA before release… but I’d very much rather them dedicate more manpower to fixing the showstopper bugs (that should have been caught by QA before release).

Bernardo_Meurer_Cost · February 25, 2021, 9:46pm

I honestly cannot understand why it’s taking them this long to solve this, it’s really frustrating.

We’re nearing on three weeks since my system worked and I’m really regretting having built it around Roon. Feeling like a chump honestly.

dylan · February 26, 2021, 7:07pm

Hi everyone,

I just wanted to provide an update that our team has been working on a solution to this and, while I can’t provide any specific timelines just yet, we’ll be sure to keep everyone here updated on the status when we have more to share. Thanks for your continued patience as we work to get this resolved.

Bernard_Languillier · February 28, 2021, 6:54am

Great to hear the team is working on this.

Let’s hope a fix can be delivered in the coming hours.

Bernardo_Meurer_Cost · March 2, 2021, 7:24am

We’re fast approaching a month since Roon has worked at all for us.

Dean_Bailey · March 2, 2021, 11:24pm

21 days in and no resolution. Any chance that I’ll be able to access my local content soon?

Bernard_Languillier · March 3, 2021, 9:36pm

This is getting extremely worrisome.

We now have a clear demonstration that Roon is fine with a significant number of paying customers being stranded for more than 3 weeks without being able to listen to music…

Bernardo_Meurer_Cost · March 4, 2021, 7:53am

This entire experience is unacceptable. That they’d release software that is so obviously broken to paying customers, and then leave us in the dark regarding the timeline for a fix is wrong and disrespectful.

I’m incredibly disappointed in Roon’s team, hard to grasp how they can care so little for such a large group of users with completely bricked systems.

Bernardo_Meurer_Cost · March 6, 2021, 3:48am

Another week without this problem being solved, is there any chance this can be prioritized?

Bernard_Languillier · March 6, 2021, 9:13pm

Yep, nearly one month…

At this point I will start to actively recommend my high end network to avoid spending money on Roon.

Who would want to fine tune a system based on Roon with the risk of not being able to play music for a month with zero useful feedback from their team for an issue that shouldn’t take more than a few hours to fix?

Ralf_Borchert · March 7, 2021, 5:20pm

I was running Roon on Ubuntu 18 with (music) file storage on ZFS without problems for years. Recently I moved my Roon Core to a Mac Pro with all storage on a ZFS Pool. The only way to attach the music storage is via /Volumes/Pool/Music. Roon throws up a warning about using Volumes … Please get this fixed as (for me anyway) ZFS is the only way to store a carefully ripped music library. Thanks, R.

Bernardo_Meurer_Cost · March 8, 2021, 7:31am

@enno @brian @allan @mike Could we please get some real information on the timeline for a fix here? This is incredibly disheartening.

brian · March 8, 2021, 3:21pm

We have a fix in QA now, along with a lot of other post-1.8 changes/improvements. Once they have all been stabilized, we will ship it.

Steef_de_Bruijn · March 8, 2021, 3:46pm

Hi @brian,

Thank you very much for this update.

Steef

Robert_Dura · March 8, 2021, 6:16pm

Thank you! Looking forward to the update.

Bernardo_Meurer_Cost · March 8, 2021, 7:50pm

I appreciate you getting back to us, looking forward to the fixed release!

Jonathon_Wiebe · March 8, 2021, 10:35pm

Can you let me know when this has landed in production? My subscription off and will remain lapsed until this is confirmed resolved. Thanks.

Dean_Bailey · March 12, 2021, 6:34pm

So, we’re at 31 days of this particular bug.

31 days of not being able to access our local content on systems that had worked (mostly) without error for multiple years before the 1.8 release.

31 days of not being able to properly use our $499-$699 lifetime licenses (or a full month of monthly billed service for those who aren’t lifetimers).

31 days of not getting any indication of when we’ll be able to use the software that we paid for, in the way it was sold to be used.

31 days days since the initial bug report was filed.

21 days since being told QA was able to reproduce this bug.

14 days since we were first told that the bug was being worked on.

What gives? How is this even close to being acceptable?