No space left on device error message during installation of touchscreen plugin

I am doing a manual installation of the RPi touchscreen plugin, because I got an error message “cannot connect to x-server” after the installation.

The manual installation process is described in https://community.volumio.org/t/help-touch-screen-plugin-installaltion/11385/4

I have flashed volumio-2.917-2021-10-06-pi.img.zip on a 16G SD card an rebooted the system.

During the installation I get 50+ error messages, here are some examples:-

Blockquote
cannot copy extracted data for ‘./usr/lib/gcc/arm-linux-gnueabihf/4.9/cc1’ to ‘/usr/lib/gcc/arm-linux-gnueabihf/4.9/cc1.dpkg-new’: failed to write (No space left on device)
cannot copy extracted data for ‘./usr/bin/xprop’ to ‘/usr/bin/xprop.dpkg-new’: failed to write (No space left on device)
cannot copy extracted data for ‘./usr/bin/iceauth’ to ‘/usr/bin/iceauth.dpkg-new’: failed to write (No space left on device)
cannot copy extracted data for ‘./usr/share/man/man1/xauth.1.gz’ to ‘/usr/share/man/man1/xauth.1.gz.dpkg-new’: failed to write (No space left on device)
cannot copy extracted data for ‘./usr/include/X11/bitmaps/noletters’ to ‘/usr/include/X11/bitmaps/noletters.dpkg-new’: failed to write (No space left on device)
error creating directory ./usr/share/fonts/X11': No space left on device unable to flush /var/lib/dpkg/updates/tmp.i after padding: No space left on device cannot copy extracted data for './usr/lib/arm-linux-gnueabihf/dri/nouveau_vieux_dri.so' to '/usr/lib/arm-linux-gnueabihf/dri/nouveau_vieux_dri.so.dpkg-new': failed to write (No space left on device) cannot copy extracted data for './usr/lib/gcc/arm-linux-gnueabihf/4.9/cc1' to '/usr/lib/gcc/arm-linux-gnueabihf/4.9/cc1.dpkg-new': failed to write (No space left on device) cannot copy extracted data for './usr/bin/xprop' to '/usr/bin/xprop.dpkg-new': failed to write (No space left on device) cannot copy extracted data for './usr/bin/iceauth' to '/usr/bin/iceauth.dpkg-new': failed to write (No space left on device) cannot copy extracted data for './usr/share/man/man1/xauth.1.gz' to '/usr/share/man/man1/xauth.1.gz.dpkg-new': failed to write (No space left on device) cannot copy extracted data for './usr/include/X11/bitmaps/noletters' to '/usr/include/X11/bitmaps/noletters.dpkg-new': failed to write (No space left on device) error creating directory ./usr/share/fonts/X11’: No space left on device
Blockquote

The procedure described in https://community.volumio.org/t/no-space-left-on-device/42175 did not help me.

The filesystem on the SD card looks like this:

Blockquote
volumio@volumio:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mmcblk0p2 2.2G 826M 1.3G 40% /imgpart
/dev/loop0 355M 355M 0 100% /static
overlay 262M 14M 229M 6% /
devtmpfs 471M 0 471M 0% /dev
tmpfs 485M 0 485M 0% /dev/shm
tmpfs 485M 8.7M 477M 2% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 485M 0 485M 0% /sys/fs/cgroup
tmpfs 485M 28K 485M 1% /tmp
tmpfs 20M 24K 20M 1% /var/log
tmpfs 485M 0 485M 0% /var/spool/cups
tmpfs 485M 0 485M 0% /var/spool/cups/tmp
/dev/mmcblk0p1 61M 57M 3.4M 95% /boot
tmpfs 97M 0 97M 0% /run/user/1000

Blockquote

I am using an RPi 3B with a HifiBerry DAC plugged on top.

Any suggestions would be appreciated.

I would not recommend that as it will not help if you encounter too less space. Regarding the amount of space available:

Did you wait serveral minutes after the first boot of Volumio so the data partition could fully expand?

If not try running

touch /boot/resize-volumio-datapart

and rebooting.

Check if size of “overlay” is bigger now. Proceed only if that’s the case.

Then if the Touch Display should still be installed uninstall and reinstall it from the plugin store.

Thanks for the suggestion.
I did not wait several minutes after the reboot, so I am going to try that.
Would I be able to see the size of the data partition using the “df” command to make sure the resizing has completed?

Check size of “overlay” in the output of df -h. E.g. on a 32G card “overlay” here has 27G (Volumio 2.917).

I flashed the 16G SD card again to have a clean start.
After running about an hour, the output of df -h shows:

volumio@volumio:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/mmcblk0p2  2.2G  826M  1.3G  40% /imgpart
/dev/loop0      355M  355M     0 100% /static
overlay         262M   14M  228M   6% /
devtmpfs        471M     0  471M   0% /dev
tmpfs           485M     0  485M   0% /dev/shm
tmpfs           485M  8.7M  477M   2% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           485M     0  485M   0% /sys/fs/cgroup
tmpfs           485M   28K  485M   1% /tmp
tmpfs           485M     0  485M   0% /var/spool/cups
tmpfs            20M   24K   20M   1% /var/log
tmpfs           485M     0  485M   0% /var/spool/cups/tmp
/dev/mmcblk0p1   61M   57M  3.4M  95% /boot
tmpfs            97M     0   97M   0% /run/user/1000

So the overlay is still very small (262M). It seems the expansion has not taken place.

I agree. On 16Gb card I would expect overlay having 13Gb.

Did you already try

touch /boot/resize-volumio-datapart

followed by a reboot?

I did touch /boot/resize-volumio-datapart and the reboot as you suggested.
Looks promising…

volumio@volumio:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/mmcblk0p2  2.2G  826M  1.3G  40% /imgpart
/dev/loop0      355M  355M     0 100% /static
overlay          13G   14M   12G   1% /
devtmpfs        471M     0  471M   0% /dev
tmpfs           485M     0  485M   0% /dev/shm
tmpfs           485M  4.7M  481M   1% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           485M     0  485M   0% /sys/fs/cgroup
tmpfs           485M   28K  485M   1% /tmp
tmpfs           485M     0  485M   0% /var/spool/cups
tmpfs            20M   16K   20M   1% /var/log
tmpfs           485M     0  485M   0% /var/spool/cups/tmp
/dev/mmcblk0p1   61M   57M  3.4M  95% /boot
tmpfs            97M     0   97M   0% /run/user/1000

And bingo - the touchscreen plugin installed via the UI.

Many thanks for your excellent advice gvolt

:tada: Glad it’s solved!