Roon ARC Port: 43577
Internet/WAN: DSL 260 Mbit/s down; 50 MBit/s up
Router: fritz!box 7590
iPhone and RoPieee connected by WLAN
Music files are located on a Synology NAS (shared folder)
Connected Audio Devices
iPhone 12, iOS 16.4.1
ropieee player 1.8 (1125) and Topping D50s (DAC)
(and more endpoints)
Number of Tracks in Library
313,000 tracks
Description of Issue
When I start the rescan of music album files, after a short period the end points will stop playing, the core is not available anymore. After an additional Minute (or two) the core comes back and is available again. Recently added music is visible and detected. No issues during rescan Singles, EPs, Compilations (all on their own shared NAS folders)
My assumption is, that the core finds files that will trigger the reboot.
I took a look at the log files, but I can not interprete them.
I also checked the “Skipped Files” section with no hint for me.
My expectation is, that reading (corrupt) files should not irritate the core.
I am addressing you both because my reported problem from April 11 is still unanswered.
I do not know, if you will take care, but can you please point the responsible staff to my issue?
Thanks in advance.
For my own learning: How do I correctly request support from RoonLabs?
I will deliver timestamp and results of new database this evening (German timezone).
One question about the new database: I do not want to loose my database content (tags, playlists, grouping, etc.). Will there be a way back to my real music database?
here are some timestamps of unwanted Core reboots:
April 11 - 12:36 (UTC+2)
– during rescan of music files; I have saved the log files for your reference
April 13 - 16:26 (UTC+2)
– during rescan of music files
April 25 - 10:49 (UTC+2) today
– after showing up tags overview
How often are you rescanning files?
Typicallay once a week after adding new music files. Roon says “real time monitoring”, but this is not true (and was never true in my environment)
This is where backups come in! Per my last reply, by creating a fresh backup before moving through the steps of refreshing your database, you’ll be able to restore your settings after troubleshooting. If you don’t already have a recent backup, I would head to Roon Settings>Backups> Back up now
When you refresh your database, please test out scanning some of your library on the new database to test if the unwanted crashing still occurs.
With that, did this issue recently pop up ~ two weeks ago? There is a chance Roon is attempting to scan a corrupt file, potentially added around this timeframe, which is causing the crashing. Are you able to review what new tracks you added to your watched folder around that time?
I’m sorry to hear this. I just re-tested things on my end and was able to have Roon scan for new files in real-time properly.
How is your NAS connected to your core and router? Do you have your core and NAS hardwired directly to the same router?
No need to rescan your entire library - I would set aside a smaller subset specifically for testing purposes.
No need to do any of this. After you’ve finished testing, you can restore your database from the recent backup you’ve saved. Here is more info on this:
We aren’t seeing anything out of the ordinary in your core diagnostics at this time. Unfortunately, the first two timestamps pre-date how far back your diagnostics go. The newest timestamp shows generic networking errors that don’t point to the issue at hand.
Because you rescanned the file in question, are you still running into unwanted core reboots? I was hoping we could test out running your ROCK without the file imported, to see if reboots still occurred.
