NAS library scanned but not saved

Help and Support Help
1

Hi,

I’m using Volumio 2.041, on RP Raspbian GNU/Linux 8 (jessie), Linux 4.4.9-v7+ armv7l, headphone jack (no DAC), 8GB SD. Music files are on WD MyCloud NAS, firmware v04.04.05-101. Both are connected to the same router via Ethernet. NAS has static IP address.

Volumio finds the NAS and mounts it (using cifs). It scans files when I go to My Music and hit Rescan. It finds files OK, but then when it’s done, it does not save the result. If I navigate away and then come back later Volumio reports 0 artists, 0 albums, 0 tracks. I can see these numbers go up when scanning, but the result is never saved.

I have tried rebooting all devices. I even reflashed a new image of Volumio and started from scratch. There is nothing marked as an error in /var/log/volumio.log. Tail of log is

2017-01-27T21:08:02.646Z - info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats 2017-01-27T21:08:06.633Z - info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats 2017-01-27T21:08:10.641Z - info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats 2017-01-27T21:08:14.653Z - info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats 2017-01-27T21:08:19.640Z - info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats 2017-01-27T21:08:22.662Z - info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats 2017-01-27T21:08:26.573Z - info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats 2017-01-27T21:08:30.639Z - info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats 2017-01-27T21:08:34.650Z - info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats 2017-01-27T21:08:38.642Z - info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats

I have no idea how to troubleshoot this. I would like to use Volumio, but this is a showstopper. Does anyone have any advice or suggestions? Thanks

2

Can you run:

sudo journalctl -f

just before you start a scan, and leave it running while the scan takes place. Does it’s output show any errors?

3

THANK YOU! Yes! There is an error reported:

Jan 28 15:19:10 volumio mpd[3703]: update: added NAS/path/to/offending/file/name.m4a Jan 28 15:19:10 volumio mpd[3703]: ffmpeg/mov,mp4,m4a,3gp,3g2,mj2: moov atom not found Jan 28 15:19:10 volumio systemd[1]: mpd.service: main process exited, code=killed, status=11/SEGV Jan 28 15:19:10 volumio systemd[1]: Unit mpd.service entered failed state. Jan 28 15:19:10 volumio systemd[1]: mpd.service holdoff time over, scheduling restart. Jan 28 15:19:10 volumio systemd[1]: Stopping Music Player Daemon... Jan 28 15:19:10 volumio systemd[1]: Starting Music Player Daemon... Jan 28 15:19:10 volumio systemd[1]: Started Music Player Daemon. Jan 28 15:19:11 volumio mpd[5295]: zeroconf: No global port, disabling zeroconf Jan 28 15:19:12 volumio volumio[3716]: info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats Jan 28 15:19:12 volumio volumio[3716]: MPD error: Error: This socket has been ended by the other party Jan 28 15:19:12 volumio volumio[3716]: MPD error: Error: This socket has been ended by the other party Jan 28 15:19:12 volumio volumio[3716]: MPD error: Error: This socket has been ended by the other party

I will try again after removing the file that resulted in this error. Does that seem like a rational approach to you? It may be that I may find others this way.

4

Yes, remove this file and redo the scan.
Another approach would be adding this to /etc/mpd.conf

decoder {
plugin "ffmpeg"
enabled "no"
}
5

Thank you chsims1 and michaelangelo. One corrupted file in the library was all it took. Removed, re-ripped, and everything seems OK now. Issue resolved.