Mac Mini M1 16GB RAM
I setup Roon core on the machine. I use Openzfs on OSX 2.0.1 for my Media Library storage on an OWC Thunderbay 8.
When I try to add a folder to Roon, it does not recognize the Volumes. Even not when I set:
sudo zfs set com.apple.mimic=apfs which tells zfs to mimic a apfs volume.
Have you got “Ignore Ownership on This Volume” (The switch is in the Get Info window) set for those volume? Or open permissions for the folders inside? Has ROON got Full Disk access? (In System Preferences>Security).
The Roon Server has full disk access. It should see the volumes. Also it should see the Media Volume which is APFS but doesnt…
Here is how the Volumes look like:
Here the view of the storage setup page:
And here the Privacy page:
Looks right.
Try changing the Music Storage Folder to the Music folder, or whatever is one level up from the actual album folders.
So my music is on the “Media” volume. The screenshot is only an example that the Volumes are not shown in the Roon app. So on my desktop screenshot you see two additional volumes, “data” and “Media”, completely ignored by roon… Thats the problem!
Can you see anything in roon if you go up a couple of directories?
sunshine>Macintosh HD>
OR
sunshine>Macintosh HD>Volumes
No change. Can not go up Higher then Macintosh HD
Do you have Roon and Roon Server installed on the Mac? Which is your core?
The list only shows access granted to Roon Server.
Only Roon Server installed. This is the Roon Core (Which is called Roon Server). Its a mac mini M1. The Screenshot you see is from the Roon Application on my Macbook Pro M1. But its the same when I go to the Roon App Settings/Storage Page on my Ipad/Iphone…
I found this though: https://help.roonlabs.com/portal/en/kb/articles/roon-storage-location-drive-disappears-after-installing-macos-ventura#Steps_to_resolve
Does Roon have issues with Disk detection and macos? Is this a Bug? I mean obviously this Bug was not fixed since a long time…
Did you do this per data set, e.g., sudo zfs set com.apple.mimic=apfs <data set>?
See, this does not have to do with zfs. Its a bug in Roons Disk arbitration handling. The “Media” Volume IS an APFS Volume if you look at the screenshot i provided. The data Volume is a zfs volume. All of the devices are visible in Disk Utility as well as in diskutil list. Can you forward this to the developers and label it as a bug? Or is there a way I can file a bug on github or somewhere?
@anon47984560, I am a volunteer moderator and do not work for Roon Labs.
I took an interest in this thread because I use Open ZSF with Linux: root and data partitions.
There are quite a few gotchas using ZFS with macOS because of restrictions by Apple, e.g., storage may only be HFS. Moreover, your setup is peculiar, and not a supported Roon installation.
Nonetheless, community members will offer assistance when they are able. Did you specify the data set as mentioned above? Additionally, caching directories also need to use HFS, so this may be relevant to your situation.
Unfortunately, my Mac has finally died, and won’t be replaced, so I can’t have a tinker.
I just wanna demonstrate you quickly with the following code snippet which works (quick hack):
//
// main.swift
// test
//
// Created by Michael Ruepp on 12.01.23.
//
import Foundation
print("Hello, World!")
let filemanager = FileManager()
let keys = [URLResourceKey.volumeNameKey, URLResourceKey.volumeIsRemovableKey, URLResourceKey.volumeIsEjectableKey]
let paths = filemanager.mountedVolumeURLs(includingResourceValuesForKeys: keys, options: [])
if let urls = paths {
for url in urls {
if (url.pathComponents.count == 1 || url.pathComponents.count == 3) && (url.pathComponents[0] == "/" || url.pathComponents[1] == "Volumes") {
print(url)
print(url.pathComponents)
do {
let values = try url.resourceValues(forKeys: [.volumeIsInternalKey,.isVolumeKey,.volumeLocalizedNameKey])
if let volname = values.volumeLocalizedName {
print("Name: \(volname)")
} else {
print("NO NAME")
}
if let volint = values.volumeIsInternal {
print("Volume is internal: \(volint)")
} else {
print("Volume is not internal")
}
if let isvol = values.isVolume {
print("It is a volume: \(isvol)\n")
} else {
print("It is not a volume")
}
} catch {
print("Error retrieving: \(error.localizedDescription)")
}
}
}
}
I get this output:
Hello, World!
file:///
["/"]
Name: Macintosh HD
Volume is internal: true
It is a volume: true
file:///Volumes/data/
["/", "Volumes", "data"]
Name: data
Volume is internal: true
It is a volume: true
file:///Volumes/Media/
["/", "Volumes", "Media"]
Name: Media
Volume is not internal
It is a volume: true
file:///Volumes/Backups%20of%20sunshine/
["/", "Volumes", "Backups of sunshine"]
Name: Backups of sunshine
Volume is not internal
It is a volume: true
Program ended with exit code: 0
Oh, I was under the impression to talk to a Roon Support Specialist. Sorry. Where can I direct my support questions, do you know by the way?
Running Roon in on macOS with Open ZFS is not an officially supported environment. It is considered Tinkering. Roon does not stop users from using their software in unsupported environments which is great for the tinkerers among us; however, when you do so, you are also taking on the ongoing support for that environment.
This is why your post was moved, back in 2021 by Roon staff, to the Tinkering section so other users who may also be using your environment can help you with diagnosing and resolving your issue.
If this does not work for you, then I would recommend running Roon in an officially supported environment for the stability and support you are looking for.
Martin
Mac Mini M1 Ventura 13.1
Since a year now I write forth and back with someone I was under the impression it is a Roon Support contact. It gives me really a bad impression of the quality of roon support. But today I learned this guy is a community member. So I do not want to reiterate the BUG I discovered in Roon Disk enumeration. Read it here please or move the topic to the support topic. I do not know why it even endet up there. It does NOT affect only ZFS volumes but also APFS Volumes. I am a paying member and I hope you finally address this issue!!!
Not applicable
Not applicable
WHAT DID YOU DO? I really dont appreciate your actions and i question your knowledge! YOU COULD NOT HELP AND NOW MOVE MY POSTS AWAY FROM THE SUPPORT SECTION!
I ESPECIALLY STATET THAT THIS AFFECTS APFS VOLUMES!!! CONSIDERING THIS BUG GOES ON FOR A LONG TIME AND IS EVEN RECOGNIZED IN THE SOFTWARE SECTION, YOUR LACK OF UNDERSTANDING AND MOVING MY SUPPORT/BUG REPORT IS ABSOLUTELY NOT TOLERABLE. I am a paying customer and even provided code samples for solving the problem. I CAN NOT BELIEVE!!! I QUIT MY ROON SUBSCRIPTION!
Does your face wrinkle up and get all red when you make an angry shouting post?
What did who do? The thread was moved by Roon staff (not a moderator/volunteer) because you’re running an unsupported set up. By definition you can’t receive support on something that is unsupported. It doesn’t matter what the problem is. However you might be able to receive help via the Tinkering category - hence the move.
Having said all of this - why the aggression? Life’s too short to shout about unrecognised volumes!!!
Please stick to the facts, @anon47984560. They are here for everyone to see. Your first post, which received one reply, was written August 2021. You didn’t respond until January 2023.
Moreover, although my forum badge clearly shows that I am a community moderator, I provided clarification as soon as I could see a misunderstanding.
This is evidently incorrect. Your own words:
Your Media volume is evidently Open ZFS (the Open ZFS logo is clearly displayed here.) Therefore, you are using either a Zvol (block storage) formatted with the Apple file system or a data set mimicking this. Either way, this is not a supported platform.
Finally, I’d like to point you to the community guidelines, in case you missed them.
Likewise, if you do need assistance, Tinkering is the correct place for your setup as I have previously explained.
