indexing stops at 5000 songs
After moving homes I sat my powernode together with my Synology NAS drive.
It stops indexing process at 5000 songs. Have been busy for a whole week now with the helpdesk getting this to work. Lost sound also in trying but managed to get sound back.
Did a restart from the diagnostics page
Did a reindex from the diagnostics page. Led stays white forever even if I let it run overnight
Did a factory reset plugging in the power plug and holding the mute key.
I end up with continues red light.
Left it without power for 24 hours.
I am almost ready to throw it out of the window.
Any one a suggestion?
-
Official comment
Hi Rogier,
I notice that you currently have an open support request with us. Kindly continue collaborating with our support crew to have your issue is resolved. -
It might be due to a corrupted track. I have close to 40K tracks and this happened to me several years ago, indexing would fail when it hit that track. Resolving it required identifying the offending file and removing/replacing it.
I suggest initiating a support request from The BluOS Controller app as the log file that is sent to Bluesound can indicate which file is the culprit.
0 -
Thank you very much Brian.
When I run the log using http://192.168.2.1/diag?print=1 how can I recognize the culprit?
I have been sending many log files the last week. First they found an album that was not right.
Now they don't know the reason why the indexing process crashes.
Do you remember what type of damage the file had? Was it missing tag info or something else.
The strange thing is I did not change a single file since I moved.
0 -
if they were unable to identify the track I'm not sure what the next step is. I've long forgotten what tag preceded the bad track as it's been years since I examined the log file in a text editor looking for the issue. If you're able to open the log as text look for where it stops indexing and see whether the bad file is listed above or adjacent to the last known indexed track.
0 -
Maybe add tracks in batches of say 100 or more and reindex each batch to see if the culprit is present? Narrow down from there. Look out for "special" characters in metadata.
1 -
Not sure if this will work. Search the log for the word Indexing
This will bring you to a list like
Apr 6 16:24:56 (none) user.info ./ms.pl: main::__ANON__ ./ms.pl (1630) Indexing 0 files took 0.0 seconds Apr 6 16:24:56 (none) user.info ./ms.pl: main::__ANON__ ./ms.pl (1630) Indexing 50 files took 0.1 seconds Apr 6 16:24:57 (none) user.info ./ms.pl: main::__ANON__ ./ms.pl (1630) Indexing 100 files took 0.2 seconds
Maybe you can find some errors logged in between of after those indexing progress lines.
0 -
Thank you @Alain. Yes that is exactly what the helpdesk advised. So I did it in batches. But still going over the 5000 mark it stalled again.
0 -
Thank you Pinot Gris. This is what is says.
0 -
BTW, searching can be done directly in the output of the /diag?print=1 command in your web browser.
If your collection is (largely) FLACs, you can also use the official FLAC tools to test the integrity of all FLAC files. I wrote a simple batch file for Windows to recurse all subdirectories of my FLAC collection, let me know if you are interested in this.
0 -
Yes I have mostly flac files . Sounds wonderful Pinot. Totally appreciate all the kind and helpful responses here.
I searched on words like
error
failed
Another attempt
indexing
0 -
You can download the FLAC tools through the xiph website (xiph dot org slash flac), current version is 1.5.0. Syntax for the FLAC tool can be found on: xiph dot org slash flac slash documentation_tools_flac dot html
Extract the zip file to some location you prefer and add that location to the system path.
Copy following into a text file and name that test_flac.cmd
echo off
FOR /R ".\" %%G in (.) DO (
Pushd %%G
IF EXIST *.flac flac -t -s *.flac
Popd )
Echo "finished scanning, look at results before closing this window!"
pauseIf you run the cmd file from within a directory, it will scan all FLAC files in that directory and all it subdirectories. Do not run it on the full collection straight away, first try it on a subdirectory that only contains a few albums, to get a feel how it works.
One final note: flac.exe cannot handle files with a pathname longer than 244 characters (or 245, cannot recall exactly).
0 -
@Rogier,
How large was the last batch you added when the index stopped? The corrupted file must be in this batch.
I would start adding in ever smaller portions of this last batch until you can isolate the problematic file.
Is there an output from http://192.168.xxx.xxx:11000/Status during the process, and when stopped?
0 -
Hi Alain,
When I moved from around 4200 files upwards it stopped at 5000. Yes maybe I can isolate it. But why doesn't it show in the log when the error is caused by corrupt music file. In other words might the problem not lie somewhere else?
0 -
Hi Pinot
I downloaded the Linux version. I made the cmd file. It is in one of my flac music folders.
What do you mean by
"and add that location to the system path. "?
Can I run the cmd directly form within the folder or do I have to open terminal screen or on my windows laptop a command prompt to run it?
0 -
Hi Mark,
Thank you for your suggestion. Could you kindly explain the reason for that? My idea was to join forces cause I feel I am walking in circles now.
With kind regards
Rogier
0 -
Hi Rogier,
You confuse me, are you using Linux or Windows?
0 -
Hi Pinot, I am sorry. I can choose from 2 laptops either windows or Linux.
On windows laptop I am using app version 4.8. I just installed 4.8 on linux and will do the same on Windows.
0 -
The indexing happens on the BluOS device, the app is not really relevant for that.
The script is written for the Windows command processor, to use it on Linux you would have to rewrite it for bash.
If you wish to run flac (or flac.exe) in the terminal or batch file without specifying the full path to the flac.exe file, you have to add the path where flac.exe is located to the system path. If you run set path in the terminal, it will show you the system path as Path=....
You can add the path to flac.exe using Control panel - System - Advanced settings - Environment variables - System variables - Path. Do not use the Path under User variables!
I run the cmd directly for a limited number flac files, say a few dozen to approx a few hundred. For thousands flac files I run it from a terminal, as this can take an hour or more. If run directly, after finishing the window will close if you press a key. If run from terminal, the window will only close if you close the terminal window.
0 -
Yet another problem.
Looks like somebody broke into my NAS.
Did my IP address gave it away?
0 -
Why would you think you got hacked?
It's very unlikely that the firewall of your router should be breached.
Moreover, the ip address you mentioned is on your local lan and is normally not visible on the outside.
About the diagnostics: it's a pity that the BluOS does not provide any useful information in the log concerning corrupted file errors.
0 -
I got a mail from synology about a security breach. I did not log in this morning but got a mail somebody logged in. I have changed my password right away but don´t know if hacker got that too.
Is this normal when it says Niet beveiligd which means unsecured?
0 -
Rogier
Not Secured on port 5000 refers to the web interface of your Synology in your internal network is not using Secure Socket Layers when performing internal routines.
That being said - I see you are working directly with our Support Crew. You are in great hands with one of our subject matter experts on NAS connections, Charmain. Please continue to work with her.
0 -
Thank you very much Tony. Yes I have a meeting with her on Friday.
Meanwhile I am busy trying to get my NAS login sorted.
Never a dull moment
0
Please sign in to leave a comment.
Comments
23 comments