· I can't get Roon to start up; the startup icon runs continuously. I bought a new iMac, restored my data and apps from Time Machine backup. I have checked privacy/firewall/network settings and all is as it should be. Should I reinstall, and if so, how do I do that?
Tell us about your home network
· Linksys Velop
AceRimmer
("I’m not just a hero; I’m a legend!")
2
If I recall correctly you cannot restore Roon from a Time Machine restore process.
This is because it creates an identical ID for Roon for one and database issues can also arise.
Not in the Appleverse myself so I will let someone who is, explain better but I am pretty sure that is your problem.
mjw
(Father! Father! Resist not! Let us destroy the core! Set us free!)
3
The way to fix this is as follows.
Make (or have ready) a Roon backup from the original Mac
Uninstall and completely remove Roon from the new Mac
Reinstall Roon on the new Mac using the official installer
Restore the Roon backup when first running at the login screen (there is a link at the bottom of the display)
If you are uncertain about any steps or don’t have a Roon backup, wait for Roon Support to assist.
@AceRimmer is correct that a previous database can’t be restored indirectly from a third-party or OS backup service. You’ll need to restore a dedicated Roon Backup you created within Roon or reinstall the app fresh.
Let’s try a fresh database and see if your issues persist:
We did as you suggested, but received a message saying “Fatal Error. Could not create lock file.” We reset permissions on the home directory from Terminal, which had no effect. Any suggestions would be most appreciated. Thanks!
Please fully quit Roon, RoonServer, and RAATServer, then remove or rename the following folders from your user Library:
~/Library/Roon
~/Library/RoonServer
~/Library/RAATServer
After that, reinstall Roon and launch it again so the application can generate a completely fresh set of database folders.
The “Could not create lock file” error usually indicates that Roon still cannot write to its local data folder, most often due to migrated permissions/ownership from the Time Machine restore. If the error persists even with fresh folders, we’ll need to inspect the ownership and write permissions of your home Library folders more closely.