[PROBLEM] Library update in progress message

[Nutul]

Does MPD access SACD ISO files...? Never tried, just asking...

[TheOldPresbyope]

Does MPD access SACD ISO files...? Never tried, just asking...

https://moodeaudio.org/forum/showthread....3#pid63153

[the_bertrum]

Tried different options. It seems that all albums from the disk are added to the library.
The mpc update [<path>] command runs without errors, albums from the folder are added, and everything is written to the log.

Moreover, after Update library, it is possible to perform Update this folder once, and then the disk is accessed, the kswapd0 and mediainfo processes are running, and after their completion it is no longer possible to update either a separate folder or the entire library. Only regeneration works

I can't attach the log file because it exceeds the allowed size. But there are no errors, only warnings like -

++ WARN: unexpected PVD type 0
2025-06-18T08:43:33 exception: Failed to open ISO9660 file "/var/lib/mpd/music/USB/2Tb_Music/CLASSIC/Hesperion XXI & Jordi Savall - Orient - Occident SACD (2006) ISO/Alia Vox - Orient-Occident.iso"

Have I got this order of operations right:

1. Starting from an empty library, update library completes, all tracks found and added.
   
2. Next run update on a single folder, this appears to complete (question: have things changed in that folder, and do those changes reflect in the UI?).
   
3. Next try update either whole library or single folder which results in "Update in progress"
   

Assuming that's correct, I'm afraid I can't reproduce.  However, I have an mpdignore file in the root of my library that excludes a folder (@eaDir - an annoying Synology thing) that get created by my NAS.  It seems that if i update directly in a folder that contains this hidden folder then the mpdignore doesn't work, but it does at levels lower than that. For example:

Tracks are stored at this level:
/music/artist/album
mpdignore is in music and has "@eaDir" in its exclude mask.  The @eaDir folder is always in the folder containing files:
/music/@eaDir 
and 
/music/artist/album/@eaDir

A full update never scans the problem directory, nor does a folder scan in an intermediate folder like "artist" in the example, a folder scan on album though throws errors that show the hidden folder was scanned.  I'd guess that this behaviour coupled with the presence of problematic files that throw errors in your library might be the cause.

[Nutul]

Does MPD access SACD ISO files...? Never tried, just asking...

https://moodeaudio.org/forum/showthread....3#pid63153

Thanks, dude, for helping me refresh my lazy brains. Although I was pretty sure it didn't.

[alexarz]

Have I got this order of operations right:

1. Starting from an empty library, update library completes, all tracks found and added.
   
2. Next run update on a single folder, this appears to complete (question: have things changed in that folder, and do those changes reflect in the UI?).
   
3. Next try update either whole library or single folder which results in "Update in progress"
   

Yes, you got it right. And step 2 does update the data in the folder.

I don't understand how the mpdignore file can help me if I don't know which albums or tracks are problematic in my library.
I deleted the ISO files from the library, but it didn't help. 
There are no errors in the log.

Is there any way to enable extended log?

Another question - in version 8 there was such an option "USB auto DV update".
In version 9 it is not there, but how does it work, is the database updated automatically when a new device is connected or not?
My disks with the library are connected via USB, and sometimes when the system is turned on, the disks take a very long time to access (the LEDs on them blink).

[the_bertrum]

My tale about mpdignore was just to illustrate that clearly the update routine behaves slightly differently when executed on the folder that contains the files rather than on a folder "above" that in the structure. So:
folder1/folder2/folder3/file1
Update at folder1 or folder2 does not throw warnings in my log, update at folder3 does.
I don't know why it is different, but it is.

Have a good look at what the folders look like from moOde by browsing to the library folders in the terminal. Run ls -la to see if there are unexpected things.

[alexarz]

I looked, deleted some questionable folders from the disk.
Regenerated the library - did not help

[the_bertrum]

I don't have experience of USB mounting in moOde, so I can't comment on the nuances of that.

I'm now very suspicious of the hygiene of your library. You've already shown a spurious iso file that was lurking about, and you mention deleting "questionable folders". I suggest you format a fresh USB disk, manually create a folder structure and then copy just a few music files into it. Update that and see if the problem re-occurs. Assuming that is fine I'd spend a few hours going through your library manually and copying only the audio tracks that you actually want into a fresh library. I strongly suspect your issue will go away at that point.

[alexarz]

There are over 1300 folders on the disk, it's impossible to view them manually.
The folders I deleted were created by Volumio when I loaded it. There were no problems with it, by the way. As well as with Moode 8.3.3

[the_bertrum]

OK, so 1300 folders that you're not sure of the contents of, but you do know that other software has been creating stuff in there. Like I said, I'm suspicious of the hygiene of your library.
It may be time consuming, but it isn't impossible to tidy it up, and given we have many other users who don't have this issue, your library is the prime suspect. Take the time, research some tools that could help, but definitely tidy it up or we can't possibly help. Something in your library breaks moOde, but we can't reproduce it because we don't have that something and until you find it we will never know what it is.