Observations first time use

Background am a former Unix System Administrator now working in Security. Run Raspberry Pi’s for Reticulation and DNS Sink hold for tracking, Pi-Hole. In addition an Ubuntu desktop user, and Mac user by preference has Unix under the hood. The following is observation from installing version 2.5.13 onto a Raspberry Pi.

Details
Volumio version 2.5.13
Raspberry Pi 3
64Gb Micro SD

Copied image to SD using Etcher. Noted three partitions:
boot
volumio
volumio_data

The initial install only had about 300Mb. after initial start up and install the partition remained the same. First attempt to expand that outside of the Pi resulted in the image not booting. Next attempt tried on the Pi through SSh. Same outcome not boot.

Next attempt wrote image then expanded volumio_data to rest of partition. Started up as normal, did reboot to check. This time all ok the nearly 60Gb is now available to copy up music too.

Second problem encountered went to plugins and choose to install backup and restore. This “error’d” on install. Through SSh noted this downloaded then attempted to run a shell in the archive. The downloaded file was a zip. In terminal through SSh noted not zip command installed, and unable to get installed with a apt-get install unzip (using sudo).

Manually downloaded on Ubuntu, did and unzip, and then tar archived. Copied this up to the running Pi, using scp. SSh in and at terminal manually installed the backup and restore plugin.

Thought I’d share this, such a great product Volumio however these two niggly issues would deter an average user.

Feedback welcome.

Thank you
Gordon

The expansion of the partition should happen automatically on your first boot of the RPi … did you try this?

I can’t reproduce your issue with the plugin. You could try looking at systemd logs directly or post a link to an uploaded log.

And to unzip, use miniunzip, already installed.

Observation on expansion of file system. Yes did expect as described the first boot to expand, however did not. That was why I then manually did prior to first run and that worked.

The plugin good to note the alternate unzip program. Decided to try installing another plugin, choose the Spotify one. Got message at end of attempted install:
Downloading plugin at volumio.github.io/volumio-plugin … p/spop.zip
END DOWNLOAD: volumio.github.io/volumio-plugin … p/spop.zip
Creating folder on disk
Unpacking plugin
Checking for duplicate plugin
Copying Plugin into location
Installing dependencies
The following error occurred when installing the plugin: Error

Checking /var/log/volumio.log noted
2019-01-05T08:57:39.461Z - info: Downloading plugin at volumio.github.io/volumio-plugin … p/spop.zip
2019-01-05T08:57:41.477Z - info: END DOWNLOAD: volumio.github.io/volumio-plugin … p/spop.zip
2019-01-05T08:57:41.481Z - info: Folder /tmp/plugins removed
2019-01-05T08:57:41.655Z - info: Checking if plugin already exists
2019-01-05T08:57:41.659Z - info: Rename folder
2019-01-05T08:57:41.676Z - info: Folder /tmp/downloaded_plugin.zip removed
2019-01-05T08:57:41.685Z - info: Move to category
2019-01-05T08:58:32.775Z - info: Checking if install.sh is present
2019-01-05T08:58:32.788Z - info: Executing install.sh
2019-01-05T08:58:37.077Z - info: Install script return the error Error: Command failed: echo volumio | sudo -S sh /data/plugins/music_service/spop/install.sh > /tmp/installog
[sudo] password for volumio: Sorry, try again.
[sudo] password for volumio:
sudo: 1 incorrect password attempt

At which point did a cleanup and aborted install. Have put a new password on the Volumio account. So my guess now i need to have something like
/data/plugins/*/install.sh in the allowed with no password in sudoers file for volumio?

Hmmm read before post !!! Noting in the install.sh assumes default password for volumio. For now will reset password install plugin and reset back. Better than wildcards and avoids leaving default user/password combinations in use.

Thank you for responses, next time am doing fresh install will check on the expanding file system.