Volumio 2 on rpi2b+ with 16Gb sdcard - overlay is 262M

Help and Support Help
1

Hello,

I’m a rather new user of Volumio (found it 2 weeks ago) - this far I’m really loving it.
Currently I’m running it on two devices and this is the first time I’m having a problem (I’m trying to get kodi to work but I have problems with the size of the root filesystem so I can’t install).

I believe that my problem is with the overlay (I’ve been using Linux for a few years but I haven’t previously used overlays/Union filesystems).

To create my image I ran:

dd if=volumio-2.175-2017-05-16-pi.img of=/dev/sdd

I then booted the pi off the sd-card, waited 10 minutes and finally performed a reboot (sudo reboot).

[code]volumio@volumio:~$ sudo fdisk -l /dev/mmcblk0
Disk /dev/mmcblk0: 14.9 GiB, 15931539456 bytes, 31116288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xb965e350

Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 * 1 125000 125000 61M c W95 FAT32 (LBA)
/dev/mmcblk0p2 125001 4882812 4757812 2.3G 83 Linux
/dev/mmcblk0p3 4882813 31116287 26233475 12.5G 83 Linux[/code]

The third partition seems to have been expanded correctly. Volumio seems to be working (I can access the website) but the root filesystem (overlay) is very small and fills up quickly (this is before even sudo apt update):

volumio@volumio:~$ df -h Filesystem Size Used Avail Use% Mounted on /dev/mmcblk0p2 2.2G 512M 1.6G 25% /imgpart /dev/loop0 254M 254M 0 100% /static overlay 262M 12M 230M 5% / devtmpfs 479M 0 479M 0% /dev tmpfs 487M 0 487M 0% /dev/shm tmpfs 487M 4.7M 482M 1% /run tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 487M 0 487M 0% /sys/fs/cgroup tmpfs 487M 16K 487M 1% /tmp tmpfs 487M 0 487M 0% /var/spool/cups tmpfs 20M 20K 20M 1% /var/log tmpfs 487M 0 487M 0% /var/spool/cups/tmp /dev/mmcblk0p1 61M 29M 33M 47% /boot tmpfs 98M 0 98M 0% /run/user/1000

I’m guessing I have missed to do something but I can’t seem to figure out what it can be…

Help would be much appreciated :slight_smile:

2

Hi,
Have a look volumio-plugins-collection-t6251.html . A plugin for kodi is available. 2 clicks and it’s done!

3

Thank you for a quick reply.

Unfortunately this is where my problems started. I have now tried again and I receive the same error (which tells me nothing).
In the zip-file there is a install.sh. When I tried running those commands in bash I got an error that the pi had ran out of disk.
That’s why I started trying to figure out how the file system works.

volumio-install-kodi-plugin-error.png
volumio-install-kodi-plugin-error.png1219×411 73.3 KB

4

I have seen this issue before when users were manually adding/ changing a partition before first boot.
In your case it could be something else, but let’s start with a clean image.
Reflash your SD and do not forget to do a sync after you finished before pulling it out.
Insert your freshly flashed SD into the PI and boot.
Then do your ‘df -h’ before rebooting…

5

I did:

sudo su dd if=volumio-2.175-2017-05-16-pi.img of=/dev/sdd sync umount /media/xubuntu/boot umount /media/xubuntu/volumio umount /media/xubuntu/volumio_data

Then I put the sdcard in the pi and put in the power (via the resyncer).

volumio@volumio:~$ df -h Filesystem Size Used Avail Use% Mounted on /dev/mmcblk0p2 2.2G 512M 1.6G 25% /imgpart /dev/loop0 254M 254M 0 100% /static overlay 262M 3.0M 239M 2% / devtmpfs 479M 0 479M 0% /dev tmpfs 487M 0 487M 0% /dev/shm tmpfs 487M 4.7M 482M 1% /run tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 487M 0 487M 0% /sys/fs/cgroup tmpfs 487M 4.0K 487M 1% /tmp tmpfs 487M 0 487M 0% /var/spool/cups tmpfs 20M 4.0K 20M 1% /var/log tmpfs 487M 0 487M 0% /var/spool/cups/tmp /dev/mmcblk0p1 61M 29M 33M 47% /boot tmpfs 98M 0 98M 0% /run/user/1000

As a bonus:

[code]volumio@volumio:~$ sudo fdisk -l /dev/mmcblk0

Disk /dev/mmcblk0: 14.9 GiB, 15931539456 bytes, 31116288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xb965e350

Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 * 1 125000 125000 61M c W95 FAT32 (LBA)
/dev/mmcblk0p2 125001 4882812 4757812 2.3G 83 Linux
/dev/mmcblk0p3 4882813 31116287 26233475 12.5G 83 Linux
[/code]

I’ll leave it on for the night and check in first thing tomorrow morning…
Hoping for something to try :slight_smile:

Have I understood things correctly if I believe that “df -h” should show the size of the overlay “/” to be 12.5G?

Thank you for helping! I really appreciate it! :smiley:

6

Carrying on where I left off yesterday I configured audio output (via the Piano 2.1) and rebooted the pi.
I tried uploading the plugin again and saw the following error in the output (so I went to the logs to find and post it):

volumio@volumio:/var/log$ tail -n 300 volumio.log | less ... 2017-05-23T05:06:59.138Z - info: Selecting previously unselected package libllvm3.9:armhf. 2017-05-23T05:06:59.156Z - info: Preparing to unpack .../libllvm3.9_1%3a3.9-4_armhf.deb ... 2017-05-23T05:06:59.192Z - info: Unpacking libllvm3.9:armhf (1:3.9-4) ... 2017-05-23T05:07:02.462Z - info: dpkg: error processing archive /var/cache/apt/archives/libllvm3.9_1%3a3.9-4_armhf.deb (--unpack): 2017-05-23T05:07:02.477Z - info: cannot copy extracted data for './usr/lib/arm-linux-gnueabihf/libLLVM-3.9.so.1' to '/usr/lib/arm-linux-gnueabihf/libLLVM-3.9.so.1.dpkg-new': failed to write (No space left on device) 2017-05-23T05:07:02.480Z - info: dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

volumio@volumio:/var/log$ df -h Filesystem Size Used Avail Use% Mounted on /dev/mmcblk0p2 2.2G 512M 1.6G 25% /imgpart /dev/loop0 254M 254M 0 100% /static overlay 262M 235M 7.0M 98% / devtmpfs 479M 0 479M 0% /dev tmpfs 487M 0 487M 0% /dev/shm tmpfs 487M 4.7M 482M 1% /run tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 487M 0 487M 0% /sys/fs/cgroup tmpfs 487M 1.7M 485M 1% /tmp tmpfs 487M 0 487M 0% /var/spool/cups tmpfs 20M 108K 20M 1% /var/log tmpfs 487M 0 487M 0% /var/spool/cups/tmp /dev/mmcblk0p1 61M 29M 33M 47% /boot tmpfs 98M 0 98M 0% /run/user/1000

I’ll reflash my sdcard again to be ready.

7

I think that I just solved it by putting the memorycard in another computer, and issue the following commands:

$ sudo su $ e2fsck -f /dev/sdd3 $ resize2fs /dev/sdd3

$ df -h Filesystem Size Used Avail Use% Mounted on /dev/mmcblk0p2 2.2G 512M 1.6G 25% /imgpart /dev/loop0 254M 254M 0 100% /static overlay 13G 46M 12G 1% / devtmpfs 479M 0 479M 0% /dev tmpfs 487M 0 487M 0% /dev/shm tmpfs 487M 4.7M 482M 1% /run tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 487M 0 487M 0% /sys/fs/cgroup tmpfs 487M 16K 487M 1% /tmp tmpfs 487M 0 487M 0% /var/spool/cups tmpfs 20M 16K 20M 1% /var/log tmpfs 487M 0 487M 0% /var/spool/cups/tmp /dev/mmcblk0p1 61M 29M 33M 47% /boot tmpfs 98M 0 98M 0% /run/user/1000