· None of the above quite fits
· None of these quite match
· No music or audio devices showing after installing 2.71 (build 1683) on Mac Mini
· ISP router, Silent Angel Bonn N8 switch, no VPN
Sounds perhaps like this common issue and workaround:
Thank you for helping out. I saw that post as well but I’m not on Sequoia (I’m on Mac OS Monterey 12.7.6) and the privacy settings described are not available. Also, no music is showing even though I added my music folder and logged into Qobuz so I think it’s more than not being able to find devices over the network.
Any progress on this? Thx
Hi @Boude,
Your account has two Roon Server machines currently active. Which is hosting your main, active Roon Server? Only one server is hosted on the Monterey machine.
It’s the server called Mac Mini running on my Mac Mini on Monterey. I also created a server on my Macbook but that was when I was troubleshooting my Mac Mini. It can be removed.
Hi, were you able to find anything?
Checking in again.
Anyone still on this?
Starting to lose my patience here… can someone please reply? Anything?
Hey @Boude,
Thanks for your patience, and my apologies for the silence over the last couple of days, that’s longer than you should have had to wait. We’ve now been through the full set of logs from the Mac mini, and have a clear answer for you.
This isn’t the macOS Sequoia issue, you were right to rule that out. Your Roon Server database is failing to open at all, on every single start. That’s why you’re seeing no zones and no music: the server has nowhere to store or read any of it, so re-adding your music folder and signing back into Qobuz can’t stick.
Here’s the cause. On 6 August your Mac mini started Roon 1.8 (build 831), an old version, from a separate RoonServer.app in your Applications folder. Running 1.8 against a Roon 2.x database rolls the database’s internal version marker backwards. So when 2.71 starts, it thinks it’s looking at a Roon 1.8-era database and tries to upgrade it again, and that upgrade collides with your real, intact 2.x database that’s already sitting there:
[broker/database] ===[ Database Migration (v2 => v3 (roon 1.8) ] ===
[broker/database] ===[ Database Migration (v3 => v4 (roon 2.0) ] ===
Critical: Cannot create '.../broker_4.db' because a file or directory
with the same name already exists.The upgrade aborts, the database never loads, and everything downstream, zones, library, settings, even your scheduled backups , fails with it. The logs confirm this cleanly: your database was opening normally at ~608 MB right up to 1 August, and from 8 August onwards the server reports db_loaded=False continuously and never discovers a single audio device.
For contrast, on 6 August under 1.8 your Mac mini’s outputs were all detected perfectly, Built-in Output, HDMI and System Output. So there’s nothing wrong with the machine or the network. It’s purely the database.
Your 608 MB library database is still on the disk and intact, and you also have a clean automatic backup from 31 July in /Users/<username>/RoonBackups. (The backups from 9 and 10 August failed, so they didn’t overwrite the good ones, that turned out to be lucky.)
The best next steps here:
1. Make a safety copy. Quit Roon and Roon Server completely. Then copy these two folders somewhere safe, ideally an external drive:
~/Library/RoonServer/Database~/RoonBackups2. Remove the old Roon 1.8 installation. In Activity Monitor, quit anything still named Roon, RoonAppliance or RAATServer. Then:
/Applications/RoonServer.app please check its version first (right-click → Get Info); this is the 1.8 copy, and it’s the one that caused this. Don’t delete /Applications/Roon.app, which is your current 2.71 install.Roon or RoonServer installer disk images are still mounted in Finder, eject them.3. Send me a directory listing. Before you change anything inside the database folder, open Terminal, paste this and send me the output:
ls -la ~/Library/RoonServer/Database/Core/9e0664f4b60d4f9c919b41efbe2aa103/That tells me exactly which leftover folder from the 1.8 run is blocking the upgrade, so I can give you the precise item to move rather than have you guess.
Let’s then get you back up and running normally. There are two routes from here:
Restore from your 31 July backup (recommended). Move your current Database folder aside, start Roon Server 2.71 so it creates a fresh one, then restore the 31 July backup from ~/RoonBackups. This is the well-trodden path and it’ll bring back your library, zones, playlists and settings as they were before any of this started. Please don’t pick the 9 or 10 August entries, those runs errored out. You’d lose roughly a week of play history, during which Roon wasn’t working anyway.
Or, clear the blockage in place. Once I’ve seen the directory listing, I can tell you which single leftover folder to move out of the way so 2.71 opens your existing database directly. Slightly quicker, and it keeps every last play count, but it needs confirmation of the exact folder name first, which is why we’ve asked for the listing above.
Happy to walk you through either one, and I’ll stay with this until you’re playing music again.
Thanks again for sticking with it, and sorry for the wait. 
Ok thanks, I’ll give it a try over the weekend.
So I deleted the Roon server that was still on my Mac Mini. Part of the confusion is that if I understand correctly, Roon does not provide Roon Server as standalone anymore - it’s not available for download on the website - only as part of the Roon app. This is quite poorly explained, I had to search quite a bit and still not sure. I took the risk of just reverting to the July 31 backup and it worked so for now I should be ok. I dread the next Roon update as my Mac Mini is headless and I have to use a monitor that’s in the attic and see if one of my kids has a mouse to spare. I’ve set Roon to launch at startup if I have to restart my Mac Mini after an update (which is often the case) but not confident it will go smoothly. I absolutely love Roon, have a lifetime subscription but this is a headache. If you want every user to buy a Nucleus just say so, most people will get over it.
When I left it last night, a backup was scheduled from 1 am. Checked again today, Mac fan was blowing, CPU usage was around 70%. Restarted my Mac Mini, Roon + Roon Server automatically started up correctly. The red triangle notifying a backup issue is also gone and CPU usage around 10%; it looks like the problems were solved. So for me all good for now, can you please check on your end if you see anything out of the ordinary. Thx
· None of the above quite fits
· None of these quite match
· Hi, I've sent 2 request regarding my question in post (ref#KRI8IM): my full name is visible in a file path. Can you please urgently take it or delete the whole thread? Underlying issue is solved
· N/A
I have amended the post. In future, please flag the relevant post, select Something else, and the moderators will respond.