I recently install Balena-cloud on a Rpi3 in a sd 16Go
I see my sorage at 170Mb and is allraedy full
I see the partion be at 14Go > how to have the fuill space disk ?
root@aec37a1:~# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 449M 0 449M 0% /dev
tmpfs 486M 4.0K 486M 1% /tmp
/dev/mmcblk0p2 307M 235M 53M 82% /mnt/sysroot/active
/dev/disk/by-state/resin-state 19M 394K 17M 3% /mnt/state
none 307M 235M 53M 82% /
/dev/mmcblk0p6 170M 141M 17M 90% /mnt/data
tmpfs 486M 24K 486M 1% /dev/shm
tmpfs 486M 8.9M 477M 2% /run
tmpfs 486M 0 486M 0% /sys/fs/cgroup
tmpfs 486M 20K 486M 1% /var/volatile
/dev/mmcblk0p1 40M 8.5M 31M 22% /mnt/boot
/dev/mmcblk0p3 307M 2.1M 285M 1% /mnt/sysroot/inactive
Disk /dev/mmcblk0: 14.64 GiB, 15707668480 bytes, 30679040 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: 0xbb6525ed
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 * 8192 90111 81920 40M c W95 FAT32 (LBA)
/dev/mmcblk0p2 90112 745471 655360 320M 83 Linux
/dev/mmcblk0p3 745472 1400831 655360 320M 83 Linux
/dev/mmcblk0p4 1400832 30679039 29278208 14G f W95 Ext’d (LBA)
/dev/mmcblk0p5 1409024 1449983 40960 20M 83 Linux
/dev/mmcblk0p6 1458176 30679039 29220864 14G 83 Linux
tanks for your help
I flash a 64bit version and is ok
What you are experiencing seems to correspond to a problem that was fixed since balenaOS v2.89.15. If it´s the same issue, upgrading should fix it. If for any reason you can’t upgrade, there’s the following workaround.
If the issue is still observed on v2.89.15 or newer, a reboot should fix it (the resize will be tried on each boot). If it is still failing, it is likely due to the underlying storage issues, initrd logs should have the actual error message.
Between v2.89.6 and v2.89.14 there was a bug that would only resize the data partition on 2nd boot - it would only resize the partition on first boot and then resize the filesystem on 2nd boot. Therefore a reboot is all that is necessary to finish the resizing process.
For v2.89.5 and earlier you can check whether the underlying partition has been resized using e.g.
fdisk -l /dev/mmcblk0. If the size reported for the data partition (
mmcblk0p6) does not match what df reports for
/mnt/data, you can try the following:
At least for some devices, resizing the filesystem manually has been tested to work. It can be done in the following way:
root@37966c0:~# umount /mnt/data
root@37966c0:~# umount /resin-data/
root@37966c0:~# umount /var/lib/docker
root@37966c0:~# mount | grep mmcblk0p6
root@37966c0:~# resize2fs -f /dev/mmcblk0p6
resize2fs 1.45.4 (23-Sep-2019)
Resizing the filesystem on /dev/mmcblk0p6 to 3618816 (4k) blocks.
The filesystem on /dev/mmcblk0p6 is now 3618816 (4k) blocks long.
After reboot the filesystem should fill all available space on the partition.