Volumio 2.014 - Scan mounted folder does not work

Help and Support Help
1

Volumio - version 2.041

Dear Volumio-community,

I hope someone can help me.
For serveral month I use volumio 1.55 on a Raspberry Pi 2 with access to the musicfolder on my NAS by smb and it works verry fine.
The Pi is connected by LAN.

This weekend I tested the new volumio 2.041 version on the same Pi2.
The skin looks verry good but i have a problem to integrate the music library.

The music is located on a NAS (Synology DS916) in a separate folder (music).
SMB-Mounting of the folder with userrights of a read only user works without problems.

After mounting the scanning of the content starts immediately and runs until 4700 +/- 50 titles.
Then it breaks up and the list of interpretes, albums and titles is empty again.
I can start this process by refresh or with a new try to read in, but the restult is every time the same.

Mounting by IP-address or DNS name for the NAS delivers the same result, abort after 4700 +/- 50 titles.

Is there perhaps a restriction on numbers or has someone an idea who the problem can be.

For a short hint many thanks in advance.

Best regards
hr16

2

Hi all

same problem here

3

We’re investigating on the issue, and hopefully in January we’ll have a version that fixes this problem

4

Hi,

I have the same problems with:
CuBox i4
Cubietruck 3
ODROID XU4

All 3 of them are stopping scanning after 2000 to 3000 titles and database is empty. I opened tickets on Github, but its still not working. Volumio 1.55 is working fine.
I hope, that this bug will soon be fixed…

Have a nice holiday

from9to5

5

Hi Michelangelo,

Is there somewhere I can download a previous version of Volumio 2.0? I stupidly deleted my share and tried re-adding it in case it was a network issue in my home.

6

Which version are you looking for?
-Gé-

7

Hi Gé,

I’m looking for a raspberry pi version pre 2.014, i’ve downloaded 2.041 from the site so will give that a go today just in case.

Gary

8

Without guarantee as these were possibly dev versions, so pls. don’t complain if you have ussues :wink:
2.013
2.011
2.009

9

Thank you!

10

HI all,

First of all, a big thanks to the developper for this software, it is the best one I found so far.
I am trying to use Volumio since Christmas and I have the same issue: after scanning 6 or 7000 musics (put on my NAS, a Synology 216J, I get the same error, it restart and the scan is cancelled. To help you, here is an extract of volumio’s journal:

[codepen]
Jan 14 20:34:32 volumio mpd[1788]: update: added NAS/PC_Saru/Musique a classer/Louise Attaque/Louise Attaque - Tes Yeux Se Moquent.wma
Jan 14 20:34:32 volumio mpd[1788]: update: added NAS/PC_Saru/Musique a classer/Louise Attaque/Louise Attaque - Ton Invitation.wma
Jan 14 20:34:32 volumio mpd[1788]: update: added NAS/PC_Saru/Musique a classer/Louise Attaque/Louise Attaque - Toute Cette Histoire.wma
Jan 14 20:34:32 volumio systemd[1]: mpd.service: main process exited, code=killed, status=11/SEGV
Jan 14 20:34:32 volumio systemd[1]: Unit mpd.service entered failed state.
Jan 14 20:34:33 volumio systemd[1]: mpd.service holdoff time over, scheduling restart.
Jan 14 20:34:33 volumio systemd[1]: Stopping Music Player Daemon…
Jan 14 20:34:33 volumio systemd[1]: Starting Music Player Daemon…
Jan 14 20:34:33 volumio systemd[1]: Started Music Player Daemon.
Jan 14 20:34:33 volumio volumio[806]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
Jan 14 20:34:33 volumio volumio[806]: MPD error: Error: This socket has been ended by the other party
Jan 14 20:34:33 volumio volumio[806]: MPD error: Error: This socket has been ended by the other party
Jan 14 20:34:33 volumio volumio[806]: MPD error: Error: This socket has been ended by the other party
Jan 14 20:34:33 volumio mpd[1910]: zeroconf: No global port, disabling zeroconf
Jan 14 20:34:35 volumio mpd[1910]: client: [0] opened from ::ffff:127.0.0.1:45930
Jan 14 20:34:37 volumio volumio[806]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
Jan 14 20:34:37 volumio volumio[806]: MPD error: Error: This socket has been ended by the other party
Jan 14 20:34:37 volumio volumio[806]: MPD error: Error: This socket has been ended by the other party
Jan 14 20:34:37 volumio volumio[806]: MPD error: Error: This socket has been ended by the other party
Jan 14 20:34:38 volumio mpd[1910]: client: [1] opened from ::ffff:127.0.0.1:45932
Jan 14 20:34:38 volumio mpd[1910]: client: [2] opened from ::ffff:127.0.0.1:45934
Jan 14 20:34:38 volumio mpd[1910]: client: [3] opened from ::ffff:127.0.0.1:45936
Jan 14 20:34:38 volumio volumio[806]: info:
Jan 14 20:34:41 volumio volumio[806]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
Jan 14 20:34:42 volumio mpd[1910]: client: [4] opened from ::ffff:127.0.0.1:45938
Jan 14 20:34:42 volumio mpd[1910]: client: [5] opened from ::ffff:127.0.0.1:45940
Jan 14 20:34:42 volumio mpd[1910]: client: [6] opened from ::ffff:127.0.0.1:45942
Jan 14 20:34:42 volumio volumio[806]: info:
Jan 14 20:34:45 volumio volumio[806]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats

[/codepen]

I did the scan several times and the error appeared at the same moment. I thought it was the last file so I erased it but like before, volumio restarted at the level of the file before the one I deleted (jus after “Louise Attaque - Toute Cette Histoire.wma”).
I also thought it was linked to my NAS (Synology DS216J) so I used my own computer as a storage: same result, after a while volumio restart.
I hope this will help you to find the bug in Volumio, I would very like to enjoy Volumio to its fullest!!
Have a good day

Saru