Roon Core Machine
Windows 10, Intel NUC NUC8i5BEH, external 4TB HDD with music FLAC files (and some mp3’s)
Hi, I installed ROON as adviced by my HiFi-specialist, because I’m considering some ROON-endpoints to replace my Plex/Sonos setup by something more High-End.
But I don’t get far as ROON seems to crash while indexing my library.
That library is also indexed bij Plex on the same NUC and that works perfectly.
I want to evaluate ROON, to decide if I’m going to use this NUC as Roon Rock.
But I can’t do a lot now.
It has indexed somewhere aroud 1600 albums of the 5500 available albums.
Thanks for the help!
Networking Gear & Setup Details
I’m a professional wifi-installer, and I’m full Ubiquiti Unifi at home.
Connected Audio Devices
Nothing connected to Roon. In the network, there are Sonos-speakers, and chromecast devices.
Number of Tracks in Library
Description of Issue
ROON just crashes after booting. Probably something with indexing my library as that isn’t finished yet.
For the small number of albums that are already read in, I would just uninstall everything, delete the hidden Roon folder, and start completely over.
I myself come to Roon via Foobar2000 and had to learn that I had corrupt (broken) files that Foobar2000 had simply read (indexed) without checking. A more detailed check showed with utilities then the problems with the files.
There are also certain conventions to follow, all of which are described in the FAQ. There may be invalid characters in the metadata, oversize file lengths in folders, etc.
If you can read the log data in the Roon folder, you may find the errors yourself.
Hi, It keeps happening, also after uninstalling. I think it has something to do with an album Roon can’t read. The software always crashes after 626 artists are scanned.
Can someone point me to where to look in the log files to find out which album is the problem?
(I searched for a way to attach or upload my log files, but that doesn’t seem to be possible on the forum here…)
I put my log files in Dropbox and provide a link. I assume you found the log files?
We’re sorry we didn’t get a chance to reply until today. Thank you for posting on community and engaging in conversation with our subscribers to find a solution.
It seems like the hypothesis you’re discussing might be what’s causing the crash. I’m not sure how far things have progressed with @Rugby (thanks for the help!), but if you’d like us to take a look, would you please:
- restart your Core
- start the import
- immediately after the crash, grab logs and upload them in our drive
Would you please let us know when the files are uploaded (please add the entire folder)? We are not automatically notified.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.