· 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
Roon Nucleus has been getting stuck adding music to library and the wheel just goes on continuously. I have rebooted the Nucleus numerous times, disabled and enabled the storage device (external hard drive) and also done a diagnostic check on the hard drive for errors and everything is functioning on that end. This happened randomly just 2 days ago and I have no idea what may be causing it. Everything in the set up is hard wired. Please help. Thank you.
Thanks for writing in and for sharing your report!
From a fresh Roon Server diagnostic report, we can see a handful of corrupt files failing to analyze. For example:
Warn: [storage] [directory] Failed to extract audio format from '/roon/sys/storage/mounts/Elements_WD_Elements_2667_575843324442314A55484C56_14649CF3649CD8B6-p1/Music/Justin Townes Earle/Justin Townes Earle - Midnight at the Movies/02 Justin Townes Earle - What I Mean to You.flac': CorruptFile
and
Warn: [storage] [directory] Failed to extract audio format from '/roon/sys/storage/mounts/Elements_WD_Elements_2667_575843324442314A55484C56_14649CF3649CD8B6-p1/Music/Led Zeppelin - Houses of the Holy 2CD [Deluxe Edition]/CD1/06 D’yer Mak’er.flac': CorruptFile
As a next step, I would test out temporarily removing these albums from your local library folder, and see if Roon is able to finish re-scanning.
The ' is being seen as ’, I would bet that other track titles with apostrophe’s might have the same issue. If you go to the actual file location using your computer’s file manager, what does “D’yer Mak’er” look like at the file level?
From the web
The appearance of ’ instead of an apostrophe (') is a common character encoding error known as mojibake. It occurs when text is encoded in UTF-8 but then misinterpreted by a viewer or system using Windows-1252 (or ISO-8859-1).
“Smart Quotes” Origin: Modern word processors like Microsoft Word often replace standard straight apostrophes with “smart” curly quotes (specifically the right single quotation mark, Unicode U+2019).
The Encoding Mismatch: In UTF-8, this curly quote is stored as three bytes: 0xE2 0x80 0x99. If a system reads those three bytes as Windows-1252 text, they map to the characters â, €, and ™ (often rendered together as ’).
Yesterday I did the rename of the RoonServer file to RoonServer_old and all files went through with no issues once finished and library was completed. However, when I updated to my most recent backup which was from April 6th the issue returned. Any insight into what is causing this to continue?
Thanks for the update @brian_pedersen, and it’s certainly interesting a fresh database allowed for full analysis.
Was the backup you restored from, created before the issue began?
A few next steps for you to try:
Go to Roon Settings → Library → Background Audio Analysis and temporarily change the schedule to “Throttled” or turn it to “Fast.” This overrides the 1–5 AM window and forces Roon to process the backlog now. Give it several hours.
Settings → Library → Clean Up Library, please share a screenshot of this window.
Another test - rather than pointing Roon at your entire WD Elements drive, temporarily remove the storage location in Roon (Settings → Storage → disable the WD Elements). Let the library settle with no local files. If the spinning stops, that may likely confirm a file on the drive is the trigger.
With that, it may help to review your WD Elements drive, sort files by date modified and look for anything added or changed around April 7–9. That’s the window when things first broke, and a new file added around that time is the most likely smoking gun.
Do you recall adding any new music to the drive right around that time?
hi benjamin! i am also experiencing this issue. is there any way you can look into what’s causing the trouble? happy to include any logs necessary, but i can’t find the place to attach files. this is what i’m getting:
the rest of my library plays fine. i’ve also done the steps of using the “clean up library” feature, turning off the scheduling window for analyzing tracks, and force restarting both the server and my Nucleus to no avail.
Hi Benjamin - Disabling the storage location and removing all files dated later than April 6th did the trick! I completed a new back up and everything is A-OK. Thank you for your help with this!
