Index problem

[mdp]

Dear,

This week I added 4tb of new and changed (higher quality) music to my collection.

Synology DS1819+ 2x 500gb ssd i/o cache. running Dsm 7.1.1-42962 update 3

Did rescan, restarted my Nas. Stil part of the old data remained in the index, not able to play. Message: file moved of deleted.

In folder view the updated foldername of the changed albums (Album name in id-tag wasn't changed) isn't either updated to the new name.

Is it possible to complete whipe out the existing index db and make a virgin fresh one?
I am no specialist but my guts said it has something to do with the i/o cache of the Nas.
Cache is recently formatted in the newest format used in DSM 7.1 (Storage chapter volume you can see wether format can be updated to best match the running DSM)

Yours Mdp

[tarnkappe]

which control point (app) are you using to browse the minimserver music files? Maybe this app is caching old music info and you have to make it to reread everything or clear its cache?

[simoncn]

It can take quite a long time to scan 4 TB of new music. It sounds like you restarted the NAS before the rescan had completed. This would cause the error messages you are seeing.

If you did the rescan from MinimWatch, you need to wait until the minim icon changes colour from yellow to green (transparent on macOS). If you did the rescan from the MinimServer configuration page, you need to click the 'Refresh status' button periodically until the status changes from Restarting or Started to Running. At this point, the rescan is complete and you can reload the rescanned library into your control point if the control point requires this.

[mdp]

Rescan was ready in a blink. Minim was running as I rebooted Nas and Laptop.
I used several different players. I also checked with finder and Foobar if the new files where really there. Foobar played them well.
For Linn I use Kazoo Ios and Android version and the new Linn App

Minim is misled and sees no reason to change. Tagging was not changed, just the files where replaced by better ones.
At this moment the Recently Added search only shows new albums I added this holiday but last day, last week etc chapters are gone. (I made changes in ListVieuwAlbums this week)
How can I get rid of whole history?
Total size database is 23 tb.
I already did everything you mentioned before I did my post.

[simoncn]

If the rescan was ready in a blink, this means it has not worked for some reason. Scanning 23 TB should take quite a long time.

After you have done a rescan, please look at the MinimServer log. At the end of the log, you should see lines like this:

restarting MinimServer[name]
ohnet.debug setting is ''
Current time is Sun Jan 08 07:43:06 GMT 2023 in time zone GMT
starting MinimServer[name]
*** possibly some other error or warning messages here ***
Library contains nnnnnnn audio files in nnnnn folders
MinimServer[name] is running

Do you see this, or some other output indicating that the rescan has not worked? If so, please post the messages you are seeing. Warnings about problems found when scanning a few of the files in your library are not an issue and can be ignored.

If you are getting a large amount of log output (more than 200 lines), don't copy it inline to a post here but instead save it to a file, zip the file and post the zipped file as a file attachment. Many thanks.

[mdp]

I did restart or rescan, I am not shure which, from the Java Icone and "Vieuw log" during the process. Viewed the debug log during the process. Startup lasted much longer.
Some of the folders with problems flew by, during watching.

Checked the music in folder mode: Name of the folders were updated to the new name and the new files were there and could be selected and played.
Problem solved?
How? Was the restart of the Synology not a restart of Minim?

Anyway all of the better files I search for are there now.
Many thanks for the support.
But I understand that recently added is not definitive, what I added last year, last month, last week, is gone now.
Or will these chapters appear again wen I modify the ListVieuwAlbum?

Thanks mdp

[simoncn]

I'm pleased to hear the problem is fixed now. After adding or changing any files, it is important to do a Rescan from the Java icon, not a Restart. It is also important to let the Rescan complete before you restart the NAS.

When you restart the NAS. MinimServer will do either a restart or a rescan despending on how you have set the MinimServer startupScan property. If you have set startupScan to false, restarting the NAS will do a MinimServer restart (without rescan). If you have set startupScan to true, restarting the NAS will do a MinimServer rescan.

The Recently Added information is handled differently. It is stored in a file named added-dates.txt in the MinimServer/recent shared folder. It is important not to delete this file because deleting it will cause you to lose your Recently Added information.

[mdp]

Normally the rescan initiated by chrome 192.168.1.119:9790 adress line on tab Satus button rescan. Does the job for small changes adding new albums.
One of the greatests features of minimserver is that music in the current que of the endpoint (musicstreamer), isn't influenced by a rescan (if the involved selected music wasn't changed).

Maybe you can add one line in the status field, refuring to the text above. (for major changes to prefer the java portal)
My startup property was set "false" I changed it in "true"

I only have seen different behavior in Recently Added; missing info and next day albums were found again.

[simoncn]

I mentioned the Java icon because you mentioned it and I thought you were doing all rescans that way.

Doing a rescan from the Status page button is the same as doing a rescan from the Java icon. The difference is that the status page doesn't give you feedback to tell you when the rescan has finished because the status page does not update automatically. To make the page update, you need to click 'Refresh status'.

I am working on changes that will make the status page update automatically when the rescan is complete. The future goal is to provide first-class support for all user actions from the status page so that people don't need to use the Java icon. The Java icon will remain available as an option.