Volumio 3 - Cannot complete music database

Volumio 3 on RPI3 (Fresh install on 16GB SD card)
Music Store on RPI4/Openmedia server running as NAS
Wired Gigabit ethernet

Volumio can now see my NAS music collection but falls over when compiling its database. As the album count reaches approximately 50 - 60 the total play time goes very odd (hundreds of hours?) then the count resets to zero after the album count goes over 100

Any ideas as to how to fix this?

I have a similar issue after upgrading from version 2.### to 3.173. However I don’t make it as far as you have.

This upgrade cleared all my setting and I needed to setup Volumio again using the wizard. Including the Network Path in the Sources section in Settings. When this was added, the network share mounts successfully (there is a ‘tick’ underneath Mounted), but NO music populates into the ‘My Music’ section. It only shows this error. I have searched this error online but cannot get any of the fixes working.Volumio 3 database error

Oh well,

maybe someone out there can help us both out. I first tried upgrading my 2.xxx copy but then tried a clean install on a larger SD card but the behaviour is the same.

I don’t get that error though - it just resets to zero.

Ok I have the same problem. The NAS is correctly mounted but I have zero music in the library. Not an error or else. Everything seems fine but the scansion starts and end a couple of seconds later without finding anything.

There is another similar thread someone raised on this forum here that sounds also like the same issue.

A reply on that thread suggests creating and sending a log after an attempt has been made to connect to the NAS, and update the database. Hopefully the Devs can sort this out soon!!

Here is mine, but i’m not sure that its something I can view. http://logs.volumio.org/volumio/S9jtwfz.html

I had that issue initially and was advised to replace the NAS name with its IP address so Volumio would mount the drive. This issue happens after the drive mounts.

Here is a log as requested, from a fresh boot and new attempt to build the database. The count gets to 117 albums but indicates 914 hours playing time which is obviously incorrect, then resets to zero

http://logs.volumio.org/volumio/zheYyE3.html

After a quick look at the log I uploaded I noticed that there was an issue when Volumio was scanning my .zip archive of music downloads. I’ve just moved the zip directory out of my music directory and started a rescan.

Database has compiled with no issues and the playtime appears to be ok too.

Not sure this will deal with HuntedDan’s issue though - a quick look through his log seems to show a different issue with wireless drivers?

My other Volumio setup - 2.xxx on an RPI 3 is perfecty ok with the zip archives though.

There is my log. It seems ok but I have over 60k tracks in NAS and it finds nothing.

Starting Live Log...
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CALLMETHOD: system_controller system enableLiveLog true
info: CoreCommandRouter::executeOnPlugin: system , enableLiveLog
info: Launching a new LiveLog session
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , rescanDb


info:
---------------------------- MPD announces state update: update
info: sendMpdCommand rescan took 4 milliseconds
info: ControllerMpd::getState


info:
---------------------------- MPD announces state update: update
info: sendMpdCommand status took 5 milliseconds
info: ControllerMpd::getState

info: sendMpdCommand status took 3 milliseconds

info: Command Router : Notfying DB Updatetrue
info: CoreCommandRouter::Close All Modals sent


info: sendMpdCommand status took 49 milliseconds
info: sendMpdCommand status took 47 milliseconds
info: sendMpdCommand playlistinfo took 4 milliseconds

info: Command Router : Notfying DB Updatefalse
info: CoreCommandRouter::Close All Modals sent



info: ControllerMpd::pushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CorePlayQueue::getTrack 0
info: CoreCommandRouter::volumioPushState
info: CorePlayQueue::getTrack 0
info: Received update from a service different from the one supposed to be playing music. Skipping notification.Current webradio Received mpd
info: ------------------------------ 89ms
info: sendMpdCommand playlistinfo took 12 milliseconds

info: ControllerMpd::pushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CorePlayQueue::getTrack 0
info: CoreCommandRouter::volumioPushState
info: CorePlayQueue::getTrack 0
info: Received update from a service different from the one supposed to be playing music. Skipping notification.Current webradio Received mpd
info: ------------------------------ 95ms
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , updateDb


info:
---------------------------- MPD announces state update: update
info: sendMpdCommand update took 3 milliseconds
info: ControllerMpd::getState


info:
---------------------------- MPD announces state update: update
info: sendMpdCommand status took 4 milliseconds
info: ControllerMpd::getState


info: Command Router : Notfying DB Updatetrue
info: CoreCommandRouter::Close All Modals sent
info: sendMpdCommand status took 47 milliseconds
info: sendMpdCommand status took 46 milliseconds
info: sendMpdCommand status took 45 milliseconds



info: Command Router : Notfying DB Updatefalse
info: CoreCommandRouter::Close All Modals sent


info: sendMpdCommand playlistinfo took 31 milliseconds
info: sendMpdCommand playlistinfo took 5 milliseconds


info: ControllerMpd::pushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CorePlayQueue::getTrack 0
info: CoreCommandRouter::volumioPushState
info: CorePlayQueue::getTrack 0
info: Received update from a service different from the one supposed to be playing music. Skipping notification.Current webradio Received mpd
info: ControllerMpd::pushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CorePlayQueue::getTrack 0
info: CoreCommandRouter::volumioPushState
info: CorePlayQueue::getTrack 0
info: Received update from a service different from the one supposed to be playing music. Skipping notification.Current webradio Received mpd
info: ------------------------------ 94ms
info: ------------------------------ 91ms
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
1 Like

The same error occurred.
This problem could not be solved by GUI operations.
I logged in via SSH, deleted the mpd database file /var/lib/mpd/tag_cache, and recreated the same file with “touch /var/lib/mpd/tag_cache”. I also set the permissions. Then I rebooted mpd or rebooted the Volumio system.
My Volumio 3 is now functioning properly.

1 Like

Please, can you repeat that from a fresh reboot, after an hour or two the log is soooooo awfully long, making it impossible to analyse.

Sorry for the delay. I used another RPi and loaded it with Volumio V3. Did the same process as I did before using the same network path, but this time my NAS music loaded ok. It was a different RPi that I used for this test though (a slightly older V1 B+, as opposed to RPi Zero that could not scan the NAS music). I have run the log on this successful test and the link is below, in case it I useful. I’m going to attempt upgrading the RPi zero again and see what happens there. Hopefully it works this time. http://logs.volumio.org/volumio/CbQAFcm.html

I upgraded my RPi Zero and found the original issue. The Network path mounted but received the same scanning database error: No database. The below log is from a clean boot of V3 on the RPi Zero. http://logs.volumio.org/volumio/PTRNEgO.html
Volumio 3 database error

As an update, I added the test setup back onto the network and when it’d loaded it had forgotten the music that it scanned before, and the same situation as seen on the RPi zero was present, databaseError: No Database. Thought I’d let you know. Cheers.

Same here, I can reproduce it on a Pi Zero and a Pi 2. Nothing useful in the log.
Downgrading fixes it, another upgrade kills it.
The suggestion to clean the mpd cache, and recreate the file with the correct permissions helped a little bit, afterwards I do not get the error message. However: still no music and no errors
I even ran mpd in verbose mode and did not see suspicious log entries. Does anyone has an idea what I can try to help you debug this?

My Setup works,

i use a RPI 3B+, and a RPI 3B

i have an USB Stick, it is on an Fritz.Box.

My Setup runs with cifs,
and in options i must type „vers=1.0“
Maybe that helps somebody.

I had the same issue yet none of the solutions worked for me.

My work-around is to not add the entire library at once. Make mounts by sub directory. Break up your music library if necessary. I have mine sorted by family member plus a few others like xmas. It seems to work for me.
I suspect the older version of mpd in Volumio 3 has a bug, but there were no bugs around that version that struck me as being the issue.
Good luck!

Still an issue for me :pensive:

Same here.
Problem was solved though, by updating to V3.233

Thank you Volumio!

Hello guys,

I just installed a fresh 3.233 version on a Pi4 B+ and after some issues mounting the nas drive it worked ok.

BUT i found an issue with my library also.

It scans ok, but after that if I make ANY adjustments on the remote interface, Windows or Android, like DSD playback direct or over PCM it erases completely the library and has to rescan everything.

Would it be related ?