Fresh install of Volumio 2.041 fails on Raspi B+

Hi,
tried yesterday a lot of times to deploy a fresh install of Volumio2.041 on my raspi B+, but didn’t succeed.
Used the described standard method. At first imaging via dd, but later with Etcher.
Tried it with a 8 GB and a 64 GB SD card.
Always the same result: ping works, but no web interface available. Also ssh works.

What went wrong?

Ciao

PS: in parallel I updated my existing installation on a Raspi2 which ran like a charme. Love Volumio2.

How long did you leave it after the first boot? You should leave it running for at least 10 minutes for various processes to complete before turning it off. There are a number of posts on the forum where this was root of the problem for RPi 0 and 1

Definately more than 10 min. I have read this.
Was busy he whole evening.

OK, this was the next try. Fresh install with Etcher, image checked by MD5 checksum.
Bootet at 6 p.m. and didn’t touch it till 6:25. No USB devices or something, just LAN cable, SD card and power.
Ping and ssh works, no web interface.

That’s what the file system looks like. No space left on /
Don’t know if that’s the way it should be.

root@volumio:/home/volumio# df -h Filesystem Size Used Avail Use% Mounted on /dev/mmcblk0p2 2.0G 497M 1.4G 26% /imgpart /dev/loop0 247M 247M 0 100% /static overlay 354M 346M 0 100% / devtmpfs 233M 0 233M 0% /dev tmpfs 242M 0 242M 0% /dev/shm tmpfs 242M 8.5M 233M 4% /run tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 242M 0 242M 0% /sys/fs/cgroup tmpfs 242M 4.0K 242M 1% /tmp tmpfs 242M 0 242M 0% /var/spool/cups tmpfs 242M 4.0K 242M 1% /var/log tmpfs 242M 0 242M 0% /var/spool/cups/tmp /dev/mmcblk0p1 61M 29M 33M 47% /boot tmpfs 49M 0 49M 0% /run/user/1000 root@volumio:/home/volumio#

Another try. Installed Volumio2 v0.928 and it worked! Changed IP address - still worked.
Went to system and fetched the update to 2.041. Update went successful and a restart was required.
After the restart same behavior than before, ping and ssh working - web interface not.
Logged in via ssh and performed volumio pull. Every line ended with ‘no space left on device’:

chown: changing ownership of '/volumio/pluginapi/getAvailablePlugins.js': No space left on device chown: changing ownership of '/volumio/pluginapi/getInstalledPlugins.js': No space left on device chown: changing ownership of '/volumio/pluginapi/getPluginDetails.js': No space left on device chown: changing ownership of '/volumio/pluginapi/getui.js': No space left on device chown: changing ownership of '/volumio/pluginapi/installPlugin.js': No space left on device chown: changing ownership of '/volumio/pluginapi/preuninstallPlugin.js': No space left on device chown: changing ownership of '/volumio/pluginapi/uninstallPlugin.js': No space left on device chown: changing ownership of '/volumio/pluginapi': No space left on device chown: changing ownership of '/volumio/wsclient.js': No space left on device chmod: changing permissions of '/volumio/app/plugins/system_controller/network/wireless.js': No space left on device Pull completed, restarting Volumio Done root@volumio:/home/volumio#

Very suspicious to me. Looks as if 2.041 doesn’t work with Raspi B+.
Maybe a bug.

The update from 0.928 will not work.

I’m wondering why it cannot start… Is there a way you can login with ssh and paste the output of

systemctl start volumio

and immediately after

sudo journalctl -f

OK, thanks for trying.
So just another fresh install via Etcher, starting up and the same.
Here are the requested infos:

[code] ___
/_ \ __
__ __ //\ \ __ __ ___ ___ /_\ ___
/\ /\ \ / __\\ \ \ /\ \/\ \ /' __ __\/\ \ / __\
\ \ _/ |/\ \L\ \
\ _\ \ _\ /\ /\ /\ \ \ /\ \L\
\ _
/ \ _//_\ _/\ _\ _\ _\ _\ _/
// // // // /////////___/

         Free Audiophile Linux Music Player - Version 2.0

      C 2015 Michelangelo Guarise - Volumio Team - Volumio.org

Volumio Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
volumio@volumio:~$ systemctl start volumio
volumio@volumio:~$ sudo journalctl -f
– Logs begin at Mon 2016-12-12 00:22:25 UTC. –
Dec 14 12:12:14 volumio systemd[1]: Stopping Volumio Backend Module…
Dec 14 12:12:14 volumio systemd[1]: Starting Volumio Backend Module…
Dec 14 12:12:14 volumio systemd[1]: Started Volumio Backend Module.
Dec 14 12:12:14 volumio volumio[1643]: 512 MB or less RAM Detected, need to enable swap
Dec 14 12:12:14 volumio volumio[1643]: Enabling Swap
Dec 14 12:12:14 volumio volumio[1643]: swapon: /data/swapfile: swapon failed: Device or resource busy
Dec 14 12:12:14 volumio systemd[1]: dynamicswap.service: main process exited, code=exited, status=255/n/a
Dec 14 12:12:14 volumio systemd[1]: Unit dynamicswap.service entered failed state.
Dec 14 12:12:17 volumio sudo[1656]: volumio : TTY=pts/0 ; PWD=/home/volumio ; USER=root ; COMMAND=/bin/journalctl -f
Dec 14 12:12:18 volumio sudo[1656]: pam_unix(sudo:session): session opened for user root by volumio(uid=0)
Dec 14 12:12:25 volumio volumio[1644]: /volumio/node_modules/fs-extra/lib/mkdirs/mkdirs-sync.js:47
Dec 14 12:12:25 volumio volumio[1644]: throw err0
Dec 14 12:12:25 volumio volumio[1644]: ^
Dec 14 12:12:25 volumio volumio[1644]: Error: ENOSPC: no space left on device, mkdir ‘/data/albumart’
Dec 14 12:12:25 volumio volumio[1644]: at Error (native)
Dec 14 12:12:25 volumio volumio[1644]: at Object.fs.mkdirSync (fs.js:922:18)
Dec 14 12:12:25 volumio volumio[1644]: at mkdirsSync (/volumio/node_modules/fs-extra/lib/mkdirs/mkdirs-sync.js:29:9)
Dec 14 12:12:25 volumio volumio[1644]: at Object.mkdirsSync (/volumio/node_modules/fs-extra/lib/mkdirs/mkdirs-sync.js:35:16)
Dec 14 12:12:25 volumio volumio[1644]: at Object.setFolder (/volumio/app/plugins/miscellanea/albumart/albumart.js:29:8)
Dec 14 12:12:25 volumio volumio[1644]: at Object. (/volumio/index.js:17:10)
Dec 14 12:12:25 volumio volumio[1644]: at Module._compile (module.js:570:32)
Dec 14 12:12:25 volumio volumio[1644]: at Object.Module._extensions…js (module.js:579:10)
Dec 14 12:12:25 volumio volumio[1644]: at Module.load (module.js:487:32)
Dec 14 12:12:25 volumio volumio[1644]: at tryModuleLoad (module.js:446:12)
Dec 14 12:12:25 volumio systemd[1]: volumio.service: main process exited, code=exited, status=1/FAILURE
Dec 14 12:12:25 volumio systemd[1]: Unit volumio.service entered failed state.
Dec 14 12:12:26 volumio systemd[1]: Starting dynamicswap.service…
Dec 14 12:12:26 volumio systemd[1]: Started dynamicswap.service.
Dec 14 12:12:26 volumio volumio[1662]: 512 MB or less RAM Detected, need to enable swap
Dec 14 12:12:26 volumio volumio[1662]: Enabling Swap
Dec 14 12:12:26 volumio volumio[1662]: swapon: /data/swapfile: swapon failed: Device or resource busy
Dec 14 12:12:26 volumio systemd[1]: dynamicswap.service: main process exited, code=exited, status=255/n/a
Dec 14 12:12:26 volumio systemd[1]: Unit dynamicswap.service entered failed state.
Dec 14 12:12:26 volumio systemd[1]: volumio.service holdoff time over, scheduling restart.
Dec 14 12:12:26 volumio systemd[1]: Starting dynamicswap.service…
Dec 14 12:12:26 volumio systemd[1]: Started dynamicswap.service.
Dec 14 12:12:26 volumio systemd[1]: Stopping Volumio Backend Module…
Dec 14 12:12:26 volumio systemd[1]: Starting Volumio Backend Module…
Dec 14 12:12:26 volumio systemd[1]: Started Volumio Backend Module.
Dec 14 12:12:26 volumio volumio[1669]: 512 MB or less RAM Detected, need to enable swap
Dec 14 12:12:26 volumio volumio[1669]: Enabling Swap
Dec 14 12:12:26 volumio volumio[1669]: swapon: /data/swapfile: swapon failed: Device or resource busy
Dec 14 12:12:26 volumio systemd[1]: dynamicswap.service: main process exited, code=exited, status=255/n/a
Dec 14 12:12:26 volumio systemd[1]: Unit dynamicswap.service entered failed state.
[/code]

Thanks for your help.

Hmm, so it seems v2.041 isn’t running with Raspi B+ due to an issue with the swap file or /data file system at all.
Really pity.

Is there a download for the version before 2.030?