Stuck file rescanning process on Roon Nucleus One (ref#5G73XG)

Support Nucleus Support
1

Select your Nucleus model from the list below

· Nucleus One

I'm having trouble with my Nucleus hardware

· Other

Select the option that fits best

· The Nucleus boots up and I can connect to it in the Roon app without issue, but I have a question about configuration/storage/attached devices

Describe the issue

Hello,

I installed the Roon Nucleus One following the instructions to migrate the database and installed an internal drive to store my music files.

Everything is working correctly, except that the file rescanning process remains stuck at 1/8468.

There are no other folders or sources being scanned for music files, other than a connection to Qobuz.

I have tried looking for a solution on forums and in various articles—specifically by restarting the Nucleus One multiple times.

I even disconnected the folder containing the music files so the system would ignore it and restarted the Nucleus; the rescanning process still starts up but makes no progress.

I didn't have this issue on the old Mac that was running Roon Server, and I can't figure out how to resolve it on the Nucleus One.

Thanks for your help.

2

Hello,

Just a quick update to let you know that the problem seems to have resolved itself overnight :wink:

Thanks for your attention, and sorry for starting this thread.

3

Hi @alvaro1,

Sorry that we missed the chance to assist before you found a resolution yourself.

When Roon arrests during file rescan, it’s usually one of two things:

  1. the server doesn’t have reliable access to the library storage location, so it gets caught in a loop trying to remount the drive via SMB

  2. a particular file isn’t consistently available to Roon due to permissions issues with the host folder.

  3. The URLs for Roon’s metadata services aren’t resolving properly through the router’s DNS service

  4. there’s a corrupt music file or piece of accompanying artwork breaking Roon’s file scanning

The first three are far more common than the last case.

Since the server appears to have chewed through the remaining files during a restart or scheduled Background Work, this will likely not occur (at least for a while) moving forward.

You can also try forcing a rescan of your networked storage while you’re actively using Roon.

Let us know if this happens again and we can provide next steps. Thank you!