Hi all,
I have two shares on my NAS a smaller and a bigger one, only I can add the small one without error, when I say error I mean it just keeps spinning and never finish my scan.
I use NFS and mount point shows up, it starts scanning but keeps doing it the share size is about 2TB.
Kodi able to read this share without any error.
How should I proceed to be able to start use my volumio?
Thank you and best regards,
R Jr.
MP3, FLAC, M3U, JPG, NFO , SFV, WV in nutshell
No, but other apps able to read and index without any error.
Data scrubbing was done about 2 weeks ago
Thank you
Thanks for the feedback. I asked the 2nd question as I have had similar behavior with a corrupted track. After replacing it, the scanning ran without issues.
Please follow these instruction and attach a log, so maybe we can see something in it.
Could you tell me some hint what should I run to make sure I do not have any corrupted files?
Please find the logs here:
http://logs.volumio.org/volumio/rekctHG.html
Sorry for me not being clear. need the log when you scan the library and it get stuck 
Your NAS should have a built in function to scan the volumes.
Just make two logs for you
This is when I start the scan:
http://logs.volumio.org/volumio/grchASN.html
and this is when “its finished”
http://logs.volumio.org/volumio/RpSQxyG.html
Do you see any interesting?
Now 4 hours later it show 0, however when it starts it starts counting till about 10000 files
Thank you and best,
R Jr.
for starters I see a lot of errors with mp3 files:
[src/libmpg123/parse.c:1185] error: Giving up searching valid MPEG header after 65536 bytes of junk.
Jul 28 17:55 : mpg123: mpg123_getformat() failed: Message: I am done with this track.
Jul 28 17:55 : ffmpeg/mp3: Format mp3 detected only with low score of 1, misdetection possible!
Jul 28 17:55 : ffmpeg/mp3: decoding for stream 0 failed
Jul 28 17:55 : ffmpeg/mp3: Could not find codec parameters for stream 0 (Audio: mp3 (mp3float), 0 channels, fltp): unspecified frame size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
Kernel errors:
Jul 28 18:04:22 volumio kernel: [<809f4a58>] (dump_backtrace) from [<809f4de8>] (show_stack+0x20/0x24)
Jul 28 18:04:22 volumio kernel: r7:ffffffff r6:00000000 r5:60000113 r4:80fe5ef0
Jul 28 18:04:22 volumio kernel: [<809f4dc8>] (show_stack) from [<809f8ffc>] (dump_stack+0xcc/0xf8)
Jul 28 18:04:22 volumio kernel: [<809f8f30>] (dump_stack) from [<809f72e8>] (dump_header+0x64/0x208)
Jul 28 18:04:22 volumio kernel: r10:80f05180 r9:00100cca r8:00000000 r7:80d1520c r6:96db3900 r5:825dec80
Jul 28 18:04:22 volumio kernel: r4:86895d50 r3:9f188448
Jul 28 18:04:22 volumio kernel: [<809f7284>] (dump_header) from [<802b4868>] (oom_kill_process+0x1b4/0x1c0)
Jul 28 18:04:22 volumio kernel: r7:80d1520c r6:86895d50 r5:825df200 r4:825dec80
Jul 28 18:04:22 volumio kernel: [<802b46b4>] (oom_kill_process) from [<802b53e0>] (out_of_memory+0x2b8/0x390)
Jul 28 18:04:22 volumio kernel: r7:80f08440 r6:80f05008 r5:825dec80 r4:86895d50
Jul 28 18:04:22 volumio kernel: [<802b5128>] (out_of_memory) from [<80304f9c>] (__alloc_pages_nodemask+0x7ec/0x1184)
Jul 28 18:04:22 volumio kernel: r7:80f057bc r6:00000000 r5:ffffe000 r4:00400100
Jul 28 18:04:22 volumio kernel: [<803047b0>] (__alloc_pages_nodemask) from [<802aed98>] (pagecache_get_page+0x10c/0x34c)
Jul 28 18:04:22 volumio kernel: r10:81031b1e r9:00000030 r8:80f05a1c r7:ad9f77a0 r6:00100cca r5:00000044
Jul 28 18:04:22 volumio kernel: r4:88cc0003
Jul 28 18:04:22 volumio kernel: [<802aec8c>] (pagecache_get_page) from [<802b0cf8>] (filemap_fault+0x638/0xb20)
Jul 28 18:04:22 volumio kernel: r10:80f05008 r9:86895ec8 r8:00000040 r7:8561fcc0 r6:86895ec8 r5:8561fcc0
Jul 28 18:04:22 volumio kernel: r4:ad9f7690
Jul 28 18:04:22 volumio kernel: [<802b06c0>] (filemap_fault) from [<8042c590>] (ext4_filemap_fault+0x38/0x4c)
Jul 28 18:04:22 volumio kernel: r10:86895fb0 r9:86895ec8 r8:00000040 r7:0000002f r6:76a11000 r5:86895ec8
Jul 28 18:04:22 volumio kernel: r4:ad9f7678
Jul 28 18:04:22 volumio kernel: [<8042c558>] (ext4_filemap_fault) from [<802e7fd0>] (__do_fault+0x48/0x150)
Jul 28 18:04:22 volumio kernel: r5:aef360c0 r4:86895ec8
Jul 28 18:04:22 volumio kernel: [<802e7f88>] (__do_fault) from [<802ed1f4>] (handle_mm_fault+0xaf4/0xe44)
Jul 28 18:04:22 volumio kernel: r7:0000002f r6:76a11000 r5:80f05008 r4:00000254
Jul 28 18:04:22 volumio kernel: [<802ec700>] (handle_mm_fault) from [<80a04420>] (do_page_fault+0x144/0x314)
Jul 28 18:04:22 volumio kernel: r10:00000254 r9:00000000 r8:aec98e44 r7:aec98e00 r6:80000007 r5:76a11ac4
Jul 28 18:04:22 volumio kernel: r4:86895fb0
Jul 28 18:04:22 volumio kernel: [<80a042dc>] (do_page_fault) from [<80114298>] (do_PrefetchAbort+0x48/0x9c)
Jul 28 18:04:22 volumio kernel: r10:00000020 r9:00000029 r8:86895fb0 r7:76a11ac4 r6:80a042dc r5:00000007
Jul 28 18:04:22 volumio kernel: r4:80f0ae84
Jul 28 18:04:22 volumio kernel: [<80114250>] (do_PrefetchAbort) from [<80101024>] (ret_from_exception+0x0/0x1c)
Jul 28 18:04:22 volumio kernel: Exception stack(0x86895fb0 to 0x86895ff8)
Jul 28 18:04:22 volumio kernel: 5fa0: 7ef692a0 7ef6916c 0000000a 00000000
Jul 28 18:04:22 volumio kernel: 5fc0: 00000000 7ef696e8 0000000a 00000002 76b2ac70 00000029 00000020 7ef696dc
Jul 28 18:04:22 volumio kernel: 5fe0: 7ef692a1 7ef690d0 76a2fa44 76a11ac4 60000010 ffffffff
Jul 28 18:04:22 volumio kernel: r8:10c5387d r7:10c5383d r6:ffffffff r5:60000010 r4:76a11ac4
failures to start MPD:
Jul 28 21:25:21 volumio volumio[857]: error: MPD error: The expression evaluated to a falsy value:
Jul 28 21:25:21 volumio volumio[857]: assert.ok(self.idling)
Jul 28 21:25:22 volumio mpd[6672]: Jul 28 21:25 : exception: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg
Jul 28 21:25:22 volumio mpd[6672]: Jul 28 21:25 : exception: Input plugin 'tidal' is unavailable: No Tidal application token configured
Jul 28 21:25:22 volumio mpd[6672]: Jul 28 21:25 : exception: Input plugin 'qobuz' is unavailable: No Qobuz app_id configured
Jul 28 21:25:23 volumio systemd[1]: Started Music Player Daemon.
Jul 28 21:25:23 volumio volumio[857]: error: MPD error: The expression evaluated to a falsy value:
Jul 28 21:25:23 volumio volumio[857]: assert.ok(self.idling)
Jul 28 21:25:23 volumio volumio[857]: error: MPD error: The expression evaluated to a falsy value:
Jul 28 21:25:23 volumio volumio[857]: assert.ok(self.idling)
Jul 28 21:25:23 volumio volumio[857]: error: MPD error: The expression evaluated to a falsy value:
Jul 28 21:25:23 volumio volumio[857]: assert.ok(self.idling)
Jul 28 21:25:23 volumio volumio[857]: error: MPD error: The expression evaluated to a falsy value:
Jul 28 21:25:23 volumio volumio[857]: assert.ok(self.idling)
Jul 28 21:25:23 volumio volumio[857]: error: MPD error: The expression evaluated to a falsy value:
Jul 28 21:25:23 volumio volumio[857]: assert.ok(self.idling)
So I would suggest to take a new SD-card, burn it either with win32diskimager, Rufus or Raspberry Pi imager and try again.
Thank you for check the log
This morning did an install to a different card.
Could you please check now the kernel errors are gone?
Hi Davide, can you check the end of the log. failing to start MPD. Not sure what is causing this
(again a lot of kernel errors)
Gents,
Did another install to a brand new SD card.
Do you see any intersting in the log?
However the final result is the same 
he says that it’s a header problem after this file :
update: added NAS/Music/Tracks/2017-2018/iO (Mulen) - Stick Out (Original Mix) [ClapCrate.net].mp3
till:
Jul 29 16:02 : update: added NAS/Music/Tracks/2017-2018/Ioakim_Sayz_-Taboo_Original_Mix_.mp3
Jul 29 16:02 : update: added NAS/Music/Tracks/Gerardo Moro - When (Original Mix).mp3
till:
Jul 29 16:02 : update: added NAS/Music/Tracks/Ioakim_Sayz_-Taboo_Original_Mix_.mp3
all in between those have a header problem.
iso vob files with problems,
but there are more files with problems
Over the past 2½ years I’ve been using Volumio, I’ve seen a number of issues on this forum and elsewhere relating to file problems, the four that spring to mind are listed below - may be worth trying these to see if that is the problem (not sure if any of these problems were address in versions since they were discovered)
After carrying out 1, 2 or 3 do 4 then reboot and rescan your library
In this case, it was due to the system running critically low on memory and the kernel killed the MPD process which was using around 760MB out of the available 1GB at the time it was killed. Unfortunately, I do not know why MPD was consuming so much memory during scan, but I agree it could be because of corrupted files that led to memory leak in whatever library MPD used for reading those files. I do see a ton of messages generated by ffmpeg regarding .m4a files that look like this:
Jul 28 17:24 : ffmpeg/mov,mp4,m4a,3gp,3g2,mj2: stream 0, timescale not set
Jul 28 17:24 : update: added NAS/Music/Tracks/Magnolia - EP/01 4 The Record (feat. Boogie).m4a
For a start, I would try excluding .m4a files from the scan and see if that improves things. And perhaps also exclude file types that don’t seem to be relevant to Volumio. So create a file called .mpdignore in the root directory of your music (I suppose this would be NAS/Music ?)_ with the following contents:
*.m4a
*.iso
*.VOB
Restart Volumio. Go to Settings → Sources → Rescan (not update).
And try to fix/remove all broken mp3 files, as there are a lot in the logs.
Thank you for your answer.
It looks like mission impossible, just did a scan with https://checkmate.gissen.nl/ and after couple of hours it gives tons of corrupted files.
I never thought I have that much corrupted files :\
Which app can you recommend to do the repair or should I use any different app to scan?
Linux or windows doesnt matter
Thank you
It’s been a while since I had the problem, but pretty sure I used MP3 Diags - it’s open source so won’t hit your pocket