No space left on device on fresh volumio 3 (Raspi-4) 64GB SD card

No, not yet, other than doing a reboot after the first one.

The overlay file system should actually get the size of the 3rd partition as it is is created after the resize. But for some unknown reason it does not (yet).

For an intermediate solution, you could use a smaller disk, I always use 8 or 16GB, they are much cheaper and you can also put your own music on a usb stick.
I know, not a solution, but this overlay file system issue could take a while.

OK,
I installed from scratch and then rebootet after initial configuration.
I did not install anything.
Looks still the same to me:

volumio@volumiobox:~$ df -k
Filesystem     1K-blocks   Used Available Use% Mounted on
/dev/mmcblk0p2   2532792 434388   1950028  19% /imgpart
/dev/loop0        371840 371840         0 100% /static
overlay           134727  17598    107094  15% /
devtmpfs          940828      0    940828   0% /dev
tmpfs             981136      0    981136   0% /dev/shm
tmpfs             981136   5320    975816   1% /run
tmpfs               5120      4      5116   1% /run/lock
tmpfs             981136      0    981136   0% /sys/fs/cgroup
tmpfs             981136      0    981136   0% /var/spool/cups
tmpfs             981136     32    981104   1% /tmp
tmpfs              20480     32     20448   1% /var/log
tmpfs             981136      0    981136   0% /var/spool/cups/tmp
/dev/mmcblk0p1     93548  54960     38588  59% /boot
tmpfs             196224      0    196224   0% /run/user/1000

No clue at the moment, strange that this only happens on some disks.
Was it a new SD or did you use it before?

This was a new one - ordered from raspishop.
Let me try it with another new one 32GB.

By the way, is there a manual way to extend the filesystem.
This is what the other users mentioned in the topic found from ~ 2 years a go.
But they did not describe it in detail, so I do not know which commands to use.

I tried it now with a 32GB SD card. The same behaviour.
Just to recap:

  • Flush SD card with image
  • Initial config of volumio
  • Reboot
  • Install touch screen plugin (seems to work correctly
  • Try to “enable” the plugin, then the error message comes up:
    “Failed to start volumio-kiosk.service: Unit volumio-kiosk.service not found”
  • Try to deinstall the plugin leads to the error message “…no space left …”
volumio@volumiobox:~$ df -k
Filesystem     1K-blocks   Used Available Use% Mounted on
/dev/mmcblk0p2   2532792 434388   1950028  19% /imgpart
/dev/loop0        371840 371840         0 100% /static
overlay           134727 131860         0 100% /
devtmpfs          940828      0    940828   0% /dev
tmpfs             981136      0    981136   0% /dev/shm
tmpfs             981136   9164    971972   1% /run
tmpfs               5120      4      5116   1% /run/lock
tmpfs             981136      0    981136   0% /sys/fs/cgroup
tmpfs             981136      0    981136   0% /var/spool/cups
tmpfs             981136     36    981100   1% /tmp
tmpfs              20480     36     20444   1% /var/log
tmpfs             981136      0    981136   0% /var/spool/cups/tmp
/dev/mmcblk0p1     93548  54960     38588  59% /boot
tmpfs             196224      0    196224   0% /run/user/1000
volumio@volumiobox:~$ sudo systemctl start volumio-kiosk.service
Failed to start volumio-kiosk.service: Unit volumio-kiosk.service not found.

Which tool do you use to flash these cards?
I mean, a card malfunction can happen (for what ever reason), but two?
And with a commonly used size of 32GB (still too big) getting the same issue?
Perhaps something else is wrong.

Yes, there is a manual procedure to res-size, but we just concluded res-size was OK.
This easily checked with sudo parted -s /dev/mmcblk0 print free
When there is no last line with a “FREE” amount of MB’s, then the data partition has its maximum size.
You can resize manually when you have an existing linux machine somewhere.

As I already mentioned, I use on my other Raspi the Pi Imager v1.6.2.
But I also tried with dd.
Do you think that the error message “Unit volumio-kiosk.service not found” is a follow-up error?

And yes, I think on my Raspi machine I can probably try the resize or not?

Yes, because that is being installed as part of the plugin.
You can’t resize in the PI, because the SD card IS already re-sized during the first boot.
We saw that and you can check as I mentioned above.
You could try to re-size the data partition before using the flashed SD in the PI.

  • You need the SD card reader (which one do you use?) and insert it with the 2nd card into a USB slot.
  • Boot
  • Run sudo fdisk -l to make sure that the 2nd SD is /dev/sda
  • Run
echo "$(sudo parted -s /dev/sda unit MB print free | tail -n 2 | grep Free | awk '{print $3}' | awk -F 'MB' '{print $1}')"
  • Note the returned, it should be a number equal or higher than 1
  • Run
echo "$(sudo parted -s /dev/sda unit MB print free | grep Free | tail -1 | awk '{print $2}' | grep -o '[0-9]\+')"
  • Mark the returned value and use it in the re-size command instead of <END>
  • Run
sudo parted -s /dev/sda resizepart 3 <END> 
sudo e2fsck -fy /dev/sda3
sudo resize2fs /dev/sda3

Done, now boot from the 2nd card.

I doubt whether it makes a difference, but never say never until you know the source of your problem.

I will try that.
Before, I just took my 1st SD card (64GB) and put it with a USB-SD-card-adapter into my other Raspi.
I tried with gparted to extend the /dev/sdb3 (volumio_data), but gparted could not do this.
Isn that strange - see my screenshot that I uploaded.
Thanks

Weird, but that should work, did you unmount /dev/sda3 first?

I solved it.
I used my Windows-PC and the BalenaEtcher to flash the SD card from scratch.
This, then, worked out of the box.
It seems that the PI Imaging Toold does not work correctly for the volumio image.
Thanks for your help.
Best regards
Eduardo

Glad it worked for you. Recently more have reported the opposite: that RPi Imager works better with Volumio than Etcher.

I too have a 64G sd card (Samsung EVO) and it looks like all the space is not available.
overly looks to only be 19G.
volumio@volumiop4:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mmcblk0p2 2.5G 425M 1.9G 19% /imgpart
/dev/loop0 364M 364M 0 100% /static
overlay 19G 150M 18G 1% /
devtmpfs 919M 0 919M 0% /dev
tmpfs 959M 0 959M 0% /dev/shm
tmpfs 959M 14M 945M 2% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 959M 0 959M 0% /sys/fs/cgroup
tmpfs 959M 0 959M 0% /var/spool/cups
tmpfs 20M 376K 20M 2% /var/log
tmpfs 959M 40K 959M 1% /tmp
tmpfs 959M 0 959M 0% /var/spool/cups/tmp
/dev/mmcblk0p1 92M 54M 38M 59% /boot
/dev/sdb1 29G 29G 198M 100% /media/MUSIC32
tmpfs 192M 0 192M 0% /run/user/1000

I have tried various install/flash methods (balena, dd, opensuse imager, raspi imager).
this is the best I have seen and was from an opensuse imager flash.

Any thoughts or comments?

Maybe you didn’t wait long enough for the filesystem to expand before first use. Apparently it takes a while. I have a 64GB card as well and see overlay is 54G with 49G available.

My solution was Not to use a usb-2-microsd card adapter in my other raspi4 with pi imager Tool. Instead i used rufus on my Windows PC that has a slot for sd-card. So i used a sd-2-microsd converter.

All the ideas trat were replied to me like “wait longer” had noch impact on my situation.

One thing that is VERY bad is using a micro SD to SD adapter sometimes delivered with the micro SD card.
ALWAYS use a proper USB card reader which takes the uSD directly, without a card adapter.

Why? I always use an microsd adapter…when flashing, I use SD port from my laptop

Then you’re one of the lucky ones.
General consensus is (google the subject) that these adapters are way from reliable.

Thanks you,
You have added another stress on the list :smiley:

So i have done some further testing.
Waiting and trying reboots seems to make no difference in my environment.
The 64G card showed 19G for the overlay above but after a re-image was only showing 130M.
I tried the method outlined here Out of Disk Space (overlayfs seems incorrect) - #18 by akelge but this caused the card to be non-bootable.
A 16G card I had was not resizing either so i used the resize2fs method and that worked fine.