Roon crashing when scanning NAS

Roon Core Machine

Windows 10, Ryzen 5950x, 32GB ram

Networking Gear & Setup Details

Ethernet, two switches, Asus router

Connected Audio Devices

Sonore microRendu (as remote)
Main PC (as Core)
NAS storage with lossless files

Library Size

around 50,000 tracks

Description of Issue

Came home to Roon not running on my main Core. Tried to start it up, got stuck on loading screen. Uninstalled and cleared database. Reinstalled and it would open now.
Tried to point it to my NAS where all the music is stored and it began loading. Now it opens, scans for like 2 seconds and immediately crashes.

Quick update: I have a large backup drive that has all my music on it. This is connected via USB. I pointed roon to that (had to uninstall again, as it was crashing before I could do anything) and it is loading fine.

So what is going on with Roon scanning the NAS folders. Seems weird as nothing has changed. I am able to access the music stored on my NAS via other programs (VLC, foobar2000 and J. river).

Thanks for the info, @Runnin17. Can you please use the directions found here and send us over a set of logs using a shared Dropbox link (or any other file sharing service)? We’ll take a look at what’s happening. Thanks!

Not trying to bypass Roon’s response to you, and I don’t know the details of how Roon works or what most of the log entries mean, but a quick glance through one of your log files (Roon_log.01.txt) shows lots of pathnames to FLAC files followed by ‘CorruptFile’ or ‘UnsupportedFormat’, which doesn’t sound good.
If these files are ‘bad’ enough to crash Roon Server, pointing Roon to a backup of the same ‘bad’ files will possibly cause similar symptoms.

So a quick update. Pointed my Roon core to a different location with newly downloaded FLAC files to test this whole corruption thing. So far everything is running well for the past 24 hours. Added around 300 albums (total of 2149 tracks). No crashes and this was accessed via the NAS. So for some reason the corrupted files made Roon mad or it was something wrong with the database when it had to scan the bad files.

Now to find out if there is a way to scan the files to figure out which ones are the bad ones.

As I stated above, they are listed in your log files. That may not be all of them, but it is certainly the ones identified by Roon as ‘bad’.

Hi @Runnin17

Can you reproduce the crashing and then use the directions found here and send us over a set of logs using a shared Dropbox link (or any other file sharing service)? We can take a look at what is causing the crash to occur. Thanks!

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.