Local Share and Network Share not working - Reindex music collection stuck on 1 song
AnsweredHey guys, i am using a synology DS920+ NAS with a Network Share connected to my NODE 2021.
Everything worked fine using the Network share, i was able to reindex the music collection after adding new music etc. until today... :(
I added some music to the NAS Music Folder (share), opened the BluOS app on my phone, pressed Reindex music collection, and it's been stuck at Indexing - 1 song processed forever.
I did a factory reset, deleted the share / added the share again, still stuck on Indexing - 1 song processing.
Sometimes it will actually try to index it and the button 'Reindex music collection' will be greyed out, sometimes i am able to press the 'Reindex music collection' again, but no matter what i do, it is simply stuck at:
'Indexing 1 songs processed'.
Adding any of my music shares locally does not work either, it will say 'Configuring - Please wait while BluOS prepares your Folder.' and then shortly after i get the message:
'Not Complete - There is a problem adding this local share'
I've restarted the NAS, I have tried using the app on the phone and also on my desktop PC.
I've also looked at the permissions on my NAS, everything is fine there.
Latest updates etc. are installed. Really not sure what to do anymore. I have also tried to rebuild the index, that doesn't work either, still simply stuck at the '1 songs processing'.
So yeah, it is essentially looping constantly as well i think, the lights on the NODE are white, indicating that its reindexing, and unless i reboot the NODE, it will just stay in this mode forever.
I really hope you guys can help me with this, it is driving me absolutely crazy. I must have been at it for 4-5 hours trying to fix this issue :(
HELP!
-
Official comment
Hey Alain, thanks for the reply. I solved the issue, turns out that the RJ-45 port on my network switch that the NODE is connected to doesn't work anymore, so it was trying to reindex via Wi-Fi, and the Wi-Fi is absolutely terrible in this room.
Definitely something i should have checked a lot earlier, but i am very happy that the issue is resolved now and that there is nothing wrong with my precious NODE!
Post is closed for comments.
Comments
1 comment