Your pi is showing lots of page allocation errors without any indication of why. You’re not running anything else on the pi other than volumio? What is gpu_mem set at in /boot/config.txt?
I have problem scanning my library with cubox-i4-pro using latest image form oph.mdrjr.net/gkkpch/ (Volumio-debian-mpd-2017-03-31-cuboxi.img)
The log shows that it first scanned around 180 albums all HiRes 24/96 and than crashed with
Apr 17 08:44:25 volumio mpd[716]: update: added NAS/Music96/Donald Fagen/Kamakiriad/01 - Trans-Island Skyway.flac
Apr 17 08:44:25 volumio systemd[1]: mpd.service: main process exited, code=killed, status=11/SEGV
Apr 17 08:44:25 volumio systemd[1]: Unit mpd.service entered failed state.
Apr 17 08:44:26 volumio systemd[1]: mpd.service holdoff time over, scheduling restart.
Apr 17 08:44:26 volumio systemd[1]: Stopping Music Player Daemon...
Apr 17 08:44:26 volumio systemd[1]: Starting Music Player Daemon...
Apr 17 08:44:26 volumio systemd[1]: Started Music Player Daemon.
Apr 17 08:44:26 volumio mpd[4118]: [146B blob data]than the system tries to restart the process several times:
Apr 17 08:44:26 volumio systemd[1]: mpd.service: main process exited, code=exited, status=127/n/a
Apr 17 08:44:26 volumio systemd[1]: Unit mpd.service entered failed state.
Apr 17 08:44:26 volumio systemd[1]: mpd.service holdoff time over, scheduling restart.
Apr 17 08:44:26 volumio systemd[1]: Stopping Music Player Daemon...
Apr 17 08:44:26 volumio systemd[1]: Starting Music Player Daemon...
Apr 17 08:44:26 volumio systemd[1]: Started Music Player Daemon.
Apr 17 08:44:26 volumio mpd[4120]: [146B blob data]finally it shouts down and tries to do a system restart but failed several times.
Apr 17 08:44:27 volumio systemd[1]: mpd.service start request repeated too quickly, refusing to start.
Apr 17 08:44:27 volumio systemd[1]: Failed to start Music Player Daemon.
Apr 17 08:44:27 volumio systemd[1]: Unit mpd.service entered failed state.
Apr 17 08:44:28 volumio systemd-journal[4129]: Runtime journal is using 12.0M (max allowed 30.0M, trying to leave 284.2M free of 1.8G available → current limit 30.0M).
Apr 17 08:44:28 volumio systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
Apr 17 08:44:28 volumio systemd[1]: Stopping Journal Service...
Apr 17 08:44:28 volumio systemd[1]: Starting Journal Service...
Apr 17 08:44:28 volumio systemd[1]: Started Journal Service.
Apr 17 08:44:28 volumio systemd-journal[4129]: Journal started
Apr 17 08:44:28 volumio systemd[1]: systemd-journald.service: main process exited, code=killed, status=11/SEGV
Apr 17 08:44:28 volumio systemd[1]: Unit systemd-journald.service entered failed state.
Apr 17 08:44:28 volumio systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
Apr 17 08:44:28 volumio systemd[1]: udisks-glue.service: main process exited, code=killed, status=4/ILL
Apr 17 08:44:28 volumio systemd[1]: Unit udisks-glue.service entered failed state.
Apr 17 08:44:28 volumio systemd[1]: udisks.service: main process exited, code=killed, status=4/ILL
Apr 17 08:44:28 volumio systemd[1]: Unit udisks.service entered failed state.
Apr 17 08:44:28 volumio systemd[1]: volumio.service: main process exited, code=exited, status=1/FAILURE
Apr 17 08:44:28 volumio systemd[1]: Unit volumio.service entered failed state.finally it lost connection …in read
Apr 17 08:44:43 volumio volumio[4224]: info: Cannot initialize MPD Connection: MPD is not running
Apr 17 08:44:43 volumio sudo[4287]: PAM unable to dlopen(pam_systemd.so): /lib/security/pam_systemd.so: cannot open shared object file: No such file or directory
Apr 17 08:44:43 volumio sudo[4287]: PAM adding faulty module: pam_systemd.so
Apr 17 08:44:43 volumio sudo[4287]: pam_unix(sudo:auth): conversation failed
Apr 17 08:44:43 volumio sudo[4287]: pam_unix(sudo:auth): auth could not identify password for [volumio]
Apr 17 08:44:43 volumio volumio[4224]: info: Cannot read I2C interface or I2C interface not presentError: Command failed: /usr/bin/sudo /usr/sbin/i2cdetect -y 1scanning some single folders worked but not the entire library. Do I run into some limitations?
Daniel
Yepp, volumio is allone on all my Rapis.
Here is config text
initramfs volumio.initrd
gpu_mem=16
max_usb_current=1
dtparam=audio=on
dtparam=i2c_arm=on
disable_splash=1
cheers
T
Well I’m really sorry Torsten, but I have to admit defeat here. I have no idea what is causing your problems, and it is difficult to make further suggestions other than purely speculative based on web-searches for “page allocation” errors… for example, playing with the “swappiness”. What I do find strange is that these problems are not reported by anyone else on these forums as far as I am aware. It may well be worth your while to try posting to a general RPi forum such as the official one for Raspbian here. When you do find a solution, then please post back, and let us know how you got on. Good luck.
Your problem is completely separate, and you should make a new post with a appropriate topic title. 
Let’s see what I tried now:
Actually you pointed in the right direction with the Raspi config files I did some web search and trial and error . . .
First I wanted to update firmware . . . did no work.
Then I made a change in cmdline.txt
I changed
“smsc95xx.turbo_mode=N”
to
“smsc95xx.turbo_mode=Y”
aaaaand . . . seems to work
I still get a lot of these
net_ratelimit: 49283 callbacks suppressed
Apr 18 15:59:09 musikzimmer kernel: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped
Apr 18 15:59:09 musikzimmer kernel: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped
Apr 18 15:59:09 musikzimmer kernel: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped
Apr 18 15:59:09 musikzimmer kernel: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped
Apr 18 15:59:09 musikzimmer kernel: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped
Apr 18 15:59:09 musikzimmer kernel: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped
Apr 18 15:59:09 musikzimmer kernel: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped
Apr 18 15:59:09 musikzimmer kernel: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped
Apr 18 15:59:09 musikzimmer kernel: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped
Apr 18 15:59:09 musikzimmer kernel: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped
at least the Raspi stays alive ( for now ) and populated the library
Slightly to optimistic . . .
all of a sudden I get ans ALSA error
Apr 18 18:59:42 musikzimmer mpd[1572]: alsa_output: Failed to open "alsa" [alsa]: Failed to open ALSA device "softvolume": No such device
Apr 18 18:59:42 musikzimmer mpd[1572]: output: Failed to open audio output
Apr 18 18:59:42 musikzimmer mpd[1572]: player: problems opening audio device while playing "NAS/Musik/Alceo Bocchino/Brasiliana no. 1.mp3"
Apr 18 18:59:42 musikzimmer volumio[1094]: info: CoreCommandRouter::servicePushState
Apr 18 18:59:42 musikzimmer volumio[1094]: info: [1492534782284] CoreStateMachine::syncState
Apr 18 18:59:42 musikzimmer volumio[1094]: info: [1492534782287] CorePlayQueue::getTrack 7
Apr 18 18:59:42 musikzimmer volumio[1094]: info: STATE SERVICE {"status":"stop","position":null,"seek":null,"duration":null,"samplerate":null,"bitdepth":null,"channels":null,"random":false,"updatedb":false,"repeat":false,"isStreaming":false,"title":null,"artist":null,"album":null,"uri":null}
Apr 18 18:59:42 musikzimmer volumio[1094]: info: CURRENT POSITION 7
It played … but I wanted to enable a mixer. The dvice is running with a HiFiBerry DAC ( it worked fin ) but I could not set the volume remotely . . . quick fix I thought. I only changed the mixer type to “software” and got the mess . . .
ok, got the ALSA part fixed . . . reset ALSA did the trick
Well that makes this story even more strange … that setting in config.txt effects the operation of the network controller. The new errors that you are seeing are allocation errors for the network device. Anyway, if it works, that’s great that you have a solution 
P.S. You don’t have anything attached to the usb ports do you?
I know that it is the network controller . . . I also do miss the link to the problem
believe it or not even the smaller Pi comes up now with the setting changed
Ok, it needed a couple of rounds to populate the library but once it did it, it is just fine
There is nothing connected to USB ports
Now I added this to /etc/sysctl.conf
[code]
rpi tweaks
vm.swappiness=1
vm.min_free_kbytes = 8192[/code]
found it in a bit older thread here github.com/divergentdave/raspbe … ysctl.conf
and some others also referring to it . . .
So far even the 256MB Pi is working quite ok
I just prepared my third device - a B+ with HiFiBerry Amp
It also required the above mentioned adjustments to run and populate the library . . . .
Something strange now . . . ( might be different topic)
after all three are up and running I tried to use my preferred remote control app which is ( of course ) Sound@Home.
I configured it manually all three devices are there but I only can select one, whatever I do it jumps back to only one ( always the same ) device.
S@H is the latest version
I’ve worked to find a fix for this issue.
If you’re on a PI, please do this:
- Connect via SSH to volumio
Do this:
wget http://repo.volumio.org/Volumio2/Binaries/arm/mpd_0.20.6-1_armv6.deb
sudo dpkg -i mpd_0.20.6-1_armv6.deb
type volumio and press enter
press enter again
once done
systemctl restart mpdThis will install mpd 20.6 (people do it only for testing purpose, if that works it will be integrated in a next release. If you do it manually then you WON’T BE ABLE TO UPDATE WITH OTA without issues).
After it, try to rescan your library. Please let us know if the crash does not occur
Thanks
Hi,
sorry too a little longer . …
I use a test device now which is a Pi3 in front of me.
I did a fresh install, only changed the name and installed as you suggested mpd 20.6 . . .
The device is still populating the library … my first observation when I run journalctl . . . the track names are not thrown on the screen anymore.
Stay tuned . . . this might take a little while
cheers
T
I am tuned indeed, this is a very important fix for us…
Since you have flashed a new system, I will send you a new image in minutes, with direct DSD support (if you want to test it…)
OK, this was successful . . . library is populated and the Pi is still alive . . .
I might even test again on one of my “poorer” devices
cheers
T
Great!
in addition . . . it also worked on WiFi so far
Hi again,
if you have to pack a new image . . . would it by any chance be possible to add support for the VU7 Odroid touchscreen ?
As of now it works as a display only . . . seems to lack USB support to read the touch information.
cheers
T
Hi Torsten,
I’m not sure if we are able to help, you need the multitouch usb (HID) driver, which needs to be ported to the PI kernel, this not something we do.
Perhaps you already have this info, it is not a trivial thing: https://github.com/derekhe/waveshare-7inch-touchscreen-driver
(The VU7 is nearly identical to the Waveshare 7" and should “theoretically” work).