Can the support team please acknowledge my ticket? Node N100 not indexing after upgrade to 3.10.3

Answered
Nicolas

I've opened up a ticket 5 days ago as my Node N100 is now refusing to index my music library, it stops after some 1500 tracks being indexed and wouldn't go any further.

As I had upgraded to 3.10.0 and got the solid red issue after a power down scenario, I had to reset to factory defaults so it could upgrade to 3.10.3, which it did. But reconfiguring the Node to index my music library now results in this failed indexing. No changes done to my music library which had been indexing fine before, and has for the past 5 years I've owned my Node.

Would appreciate some help on this as it renders my Node unusable now. All of my music is streaming from my music library on my NAS...

 

Anyone else with this issue?

0

Comments

3 comments

Date Votes
  • Official comment
    Tony W.
    Product Support Manager

    Hi Nicholas

    Thanks for your patience and glad to see you resolved the issue as we continue to work through an unexpected increase in Support during the Pandemic.

  • Bjørn Ulvik
    Hi-Res
    • Edited

    Hi Nicolas, I had the same issue. Files that have been indexed without proplems for years.

    Reason: 2 files (out of 177000) made the indexing fail. Both were AAC-files (m4a), encoded with FFmpeg (firefox addon).
    Solution: Find and remove the file(s) that makes the indexing fail.

    Depending on how your library is organized on your NAS it can take "a lot" of time.

    In my case my library is organized in folders like this:
    A-C/ArtistName/Subfolders
    D-F/ArtistName/Subfolders
    *
    *
    Y-Z/ArtistName/Subfolders

    I created a new folder on my NAS and moved all files/folders there:
    On my "music share" I added A-C/Subfolders first, indexed and if the index failed I had to look in that folder to find the file(s) that made the index fail.
    If the index didn't fail, I moved it back to the new folder, and added D-F/Subfolders to the "music share", indexed.....and so on.

    0
  • Nicolas

    Ok I identified the file at fault, but went through a much easier method of looking at the log file sent by the Node to the support team when the ticket was created (through the Help section of the controller app), and sure enough the last properly indexed files pointed to a directory where I could easily identify the file at fault.

    So issue fixed, though I would have appreciated an answer from the support team anyway on my support ticket, which has not yet been acknowledged. So much for official support efficiency...thanks to the community ;-)

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post