Roon Version 1.7 Build 528 on MacOS 10.15.3
Core on Ubuntu in FreeNAS VM
Controllers on Mac and iPad both affected
Network is COX
Router Ubiquity UniFi USG
Switches are Ubiquity Switch-8
Problem began after update to build 528 controllers.
Album metadata load (selection in controller) always spins.
Artist search succeeds but album selection spins if not in local library
Search for track finds the track but selection spins
Share of album spins. Share of track succeeds.
Shares are to MissyGreyhound@twitter
Is there anything I need to verify? We’ve had a number of flash over clearings. Core and Mac are UPS protected. Endpoints are on Furman Elite power conditioning.
Endpoints have auto restarted multiple times April Fools Day.
Core switch (video switch) has restarted multiple times since core rebooted.
Issue first noted after 528 build upgrade.
Last core host reboot on 3/18/2020
Unifi Advanced features are off at the moment but changing had no effect.
Network latency is 32 ms avg
Network download speed is > 100 mbps
Network upload speed is > 11 mbps
About 200 dropped packets
No transfer errors
If you try temporarily hosting your Roon Core on the Mac, do you see similar behavior there? Or does this issue just impact when the Core is on the VM?
Open Roon on the other PC you wish to try as the Core
Roon Settings → General
Disconnect
On the “Choose your Core” screen, press “Use this PC”
If asked to Unauthorize, you can go ahead and do so. You are limited to one active Roon Core at a time but you are free to switch between them as often as you’d like.
Verify if the same behavior occurs on the different Core
Lets try an orderly restart of FreeNAS and the VM. After all the wind the other day, it decided it could find local albums like Thile-Mehldau but not their tracks. I checked the server logs and FreeNAS itself was happy. The VM could be indisposed.
Reboot of FreeNAS sorted it. Can now play Lukas Nelson’s new album (first time played).
I had assumed a server restart had occurred after all the strum und drang. The FreeNAS hardware is pretty robust (Xeon, ECC memory, ZFS file system) but not bullet proof.
Glad to hear the reboot sorted the issue out. VMs are a bit tricky to troubleshoot so if you experience this issue again I would also check to see if it occurs on another Core running a native operating system.
