"auxfile not found" error messages

I recently went through a process or reorganizing my library on disk using Roon’s export function. Roon had no issue matching albums in their new storage locations and directory structures on my NAS. After the files were organized on disk the way I wanted I migrated them from the NAS to a USB-attached array connected directly to the core (Nucleus+).

All of this worked perfectly and my library is exactly how it looked before I started.

Ever since the reorganization I’ve been getting errors similar to these in the core logs on Roon startup (during the initial library scan):

09/04 17:30:13 Warn: auxfile not found 589336 (24:1:b296af78-6796-40c6-be47-06bcb308c1b8)                                                     
09/04 17:30:13 Warn: auxfile not found 589080 (24:1:526af872-fcb6-4a1d-91e2-78080a3b0256)                                                     
09/04 17:30:13 Warn: auxfile not found 691480 (24:1:853b18cd-2e83-4cfa-8725-507e5bd84456)                                                     
09/04 17:30:13 Warn: auxfile not found 690456 (24:1:85b43dbf-3995-4793-9c8d-ba27e8c34f02)                                                     
09/04 17:30:13 Warn: auxfile not found 690712 (24:1:a7901404-1a58-4b6d-8b95-023d4bf10556)                                                     
09/04 17:30:13 Warn: auxfile not found 690456 (24:1:85b43dbf-3995-4793-9c8d-ba27e8c34f02)                                                     
09/04 17:30:13 Warn: auxfile not found 690712 (24:1:a7901404-1a58-4b6d-8b95-023d4bf10556)                                                     

There are hundreds of these messages at this stage in startup, but that’s the only time I see them pop up.

So, what do these errors mean. Roon is obviously looking for a file and not finding it, but what are auxfiles? If it’s extra artwork or PDF booklets then I don’t really care, but if it’s something more critical I’d like to get to the bottom of it.

If it’s nothing to worry about then is there a way to clean up the database so that it no longer looks for these files? I’ve gone through the library cleanup and that hasn’t done anything to help.

Again, there’s no outward indication of a problem and I wouldn’t be asking this had I not noticed these errors when looking for something different in the core logs.

Yup, this is what we’re looking for. Nothing to really worry about.

1 Like

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.