Just got phone, low disk space on "filesystem root" after trying to install Signal flatpak

[tehowe]

I just got the phone today, put in my 128Gb memory expansion card and SIM card, then due to the various posts in this forum recommending the elagost Signal flatpak here:

https://elagost.com/flatpak/

I went ahead with trying the install. The page reads:

To install system wide:

sudo flatpak remote-add --if-not-exists signal-arm https://elagost.com/flatpak/signal.flatpakrepo

sudo flatpak install signal-arm org.signal.Signal

After typing in the second command, I get

[Stuff redacted] Warning: While pulling runtime/org.freedesktop.Platform.GL.default/aarch64/22.08 from remote flathub: Delta requires 346.2 MB free space, but only 253.5 MB available
Warning: While pulling runtime/org.freedesktop.Platform.GL.default/aarch64/22.08-extra from remote flathub: Delta requires 346.2 MB free space, but only 253.5 MB available
Warning: Not enough disk space to complete this operation
Warning: Not enough disk space to complete this operation
Error: While pulling runtime/org.freedesktop.Platform/aarch64/22.08 from remote flathub: Delta requires 488.2 MB free space, but only 252.9 MB available
error: Failed to install org.freedesktop.Platform: While pulling runtime/org.freedesktop.Platform/aarch64/22.08 from remote flathub: Delta requires 488.2 MB free space, but only 252.9 MB available

The filesystem is shockingly full in the bits I need it not to be:

purism@pureos:~$ df -h
df: /run/user/1000/doc: Operation not permitted
Filesystem Size Used Avail Use% Mounted on
udev 1.3G 0 1.3G 0% /dev
tmpfs 300M 2.1M 298M 1% /run
/dev/dm-0 3.6G 3.4G 35M 99% /
/dev/mtdblock1 1.2M 1.2M 0 100% /usr/share/firmware-librem5-nonfree/firmware
overlay 3.6G 3.4G 35M 99% /usr/lib/firmware
tmpfs 1.5G 33M 1.5G 3% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
/dev/mmcblk0p1 451M 94M 334M 22% /boot
tmpfs 300M 108K 299M 1% /run/user/1000
/dev/sda1 120G 384K 120G 1% /media/purism/6638-6630

How can I fix this? How did this happen? Need to get Signal running so this will be useable. Thanks!

[dos]

Did you by any chance reflash the phone after receiving it?

[irvinewade]

@tehowe

/dev/dm-0 3.6G 3.4G 35M 99% /

Looks like the root file system hasn’t been expanded to its full actual size. The size should be close to 32 GB (i.e. minus whatever is in /boot).

[joao.azevedo]

@tehowe

can you run the following commands and post the output:

sudo parted /dev/mmcblk0

then;

print

Then:

quit

And post the output here.

[tehowe]

Sure! I’ll field the above questions in just the one reply here…

I did not reflash the phone

‘disks’ seems to think the main partition is ok

And parted appears to confirm this @joao.azevedo

[sharky]

I also am facing similar issue; which was also leading me to not be able to login successfully.

[marcf]

I had the same problem last week and solved it by doing :

$ df -kh /
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
/dev/disk/by-uuid/xxxx 3,6G 3,4G 79M 98% /

$ sudo resize2fs /dev/mapper/crypt_root
resize2fs 1.46.2 (28-Feb-2021)
Filesystem at /dev/mapper/crypt_root is mounted on /; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 4
The filesystem on /dev/mapper/crypt_root is now 7509504 (4k) blocks long.

$ df -kh /
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
/dev/disk/by-uuid/xxx 29G 3,4G 24G 13% /
$

Hope it helps

[Quarnero]

@sharky

which was also leading me to not be able to login successfully.

$ df -kh /boot

[tehowe]

Amazing, this works 100%

Thanks to everyone that helped, especially @irvinewade and @marcf for nailing the issue.

Let’s hope not too many phones are leaving the factory in this state.

[ivilata]

I also had the issue with the 3.something GiB root filesystem with a new device (no reflashing or anything), and I was also able to fix it with @marcf’s suggestion. Thanks!

[leetaur]

I might do a “df - h” to check the partition when I get mine just to be sure

Glad there is a fix posted.

[NyxTheNightHerself]

I am facing an analogous issue except that resize2fs thinks there’s nothing for it to do:

[matt2]

Looks like your file system has already been resized, but something is using the space. You can try this to check used disk space:

sudo du -hs ~/* ~ /lib /opt /usr /srv /var

You can leave off the sudo if you do not mind a few error messages when it checks /var.

[marcf]

Take a look here : Just got phone, low disk space on "filesystem root" after trying to install Signal flatpak

[dos]

This is how you resize the filesystem:

sudo growpart /dev/mmcblk0 2
sudo resize_rootfs

Fresh images should do it automatically on first boot now.

However, as @matt2 noted, your filesystem is already resized and you have 26GB already used.