Roon Nucleus One fails to auto-update library when adding files (ref#CUSOOQ)

[Christophe_Remond (Christophe Rémond)]

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

I have a USB disk attached to my Nucleus One that I have been using without problems since its acquisition (about 8 months ago). But for some time I have noticed that when I add files to the library, I no longer have an automatic update... I have to "force" the update in the "storage" menu...

I created a new directory at the root of my USB disk and declared it in "Storage": automatic update is done without problem! Strange...

In addition, I noticed in the "Library" menu that the Roon server seems to be blocked on the audio analysis: the counter runs without ever reaching the number of files to be analyzed.

A clue to explain my problem?

NB : log file included below

[Christophe_Remond (Christophe Rémond)]

The audio analysis “blocked”…

[vadim]

Hello @Christophe_Remond,

Thank you for the detailed description — this helps narrow things down

A couple of clarifications and quick checks would help us understand what’s going on here:

1. Storage configuration

• In Settings → Storage, is the original folder on the USB drive (where auto-updates no longer work) explicitly listed as a Music Folder and showing a healthy status?

2. Audio analysis spinner

• The analysis counter continuously running usually means analysis jobs are queued or restarting.
• Please perform a full physical restart of the Nucleus One:
  • Power it off completely (rear button)
  • Wait ~30 seconds
  • Power it back on
• After reboot, check:
  • Does the audio analysis spinner still run indefinitely?
  • Does the track count change over time?

3. Auto-update behavior after reboot

• After the restart, try adding a small test file to:
  • the original folder (problematic one)
  • the newly created folder (which currently works)
• Let us know if the behavior differs after a clean reboot.

Once you confirm the points above (especially whether the spinner persists after a cold reboot), we can advise on the next steps.

[Christophe_Remond (Christophe Rémond)]

Hello

Thank you for the help

Yes, the disk that no longer works (auto-update) is well declared and healthy (see “Music” directory screen copy)

I did a total reboot as requested. I no longer have the audio analysis spinner running indefinitely… but the addition of new tracks is still not detected, while on the 2nd disc (“Test”) it works well

Have you examined the log file I provided?

[benjamin]

Hey @Christophe_Remond,

Thanks for the additional information! Could you please access the webUI of your Nucleus and share a screenshot? Here’s more info:

RoonOS webUI

With that, we were able to review a fresh diagnostic report from your Nucleus, and saw some issues with Roon attempting to scan a few files from the /Music share that could be causing you your issues. They were:

 Classical/Savall Le Royaume Oublié - La Tragédie Cathare - Savall (2009) [Apple Lossless]

and

Yuri Korzunov Through [DSDFLAC HD Format Test]/yuri-korzunov_through_chill_2022_1024fs.dsf

If you temporarily move these tracks to a different location, not watched by Roon, do you continue to run into issues?

Thank you!

[Christophe_Remond (Christophe Rémond)]

Bingo! You were right: it was indeed a directory that caused thus issue in Roon ( Classical/Savall The Forgotten Kingdom - The Cathar Tragedy - Savall (2009) [Apple Lossless]). Indeed, the file names were much too long (and some characters must have been a problem too!).

As soon as I set aside this directory and relaunched the Roon server, everything got back in order

Thank you very much @benjamin for your help!!

NB: it is still damaging that this kind of situation is not detected by the Roon server: these files were even not listed as “corrupted”… How can I protect myself from this kind of inconvenience in the future?

[benjamin]

Hey @Christophe_Remond,

That’s excellent news! I’m glad to hear that helped sort things out.

@Christophe_Remond

How can I protect myself from this kind of inconvenience in the future?

A good question! A few things you can do:

1. Enforce filename & path length limits - this is the single most important protection.

General rule of thumb:

• Folder names: ≤ 80 characters
• Filenames: ≤ 120 characters
• Avoid nesting deeper than:

  /Music/Classical/Composer/Work/Album/Tracks

2. Standardize characters. Stick to:

• A–Z, a–z
• 0–9
• space
• dash -
• underscore _

Avoid:

• Smart quotes “ ”
• Long dashes – —
• Slashes inside names
• Excessive brackets

Keeping consistent backups is also a good way to ensure long-term database safety. I hope this helps, and most importantly, happy listening!