Only 1GB in /mnt/data?


#1

I was expecting all of the excess storage to be allocated to /mnt/data in the rootOS, so that it could be made available to services (containers) but it looks like it’s only 1GB.

Am I missing something? I flashed it with the latest download for the Fin.


#28

Hi @jgentes,

That is odd. I have a fin flashed and it was expanded correctly. Do you happen to have any custom setup in terms of the OS? Maybe running the data partition from an external drive? If not, can you share with us the exact steps how to reproduce this, with versions and anything that might be relevant?

As well, you can open a support ticket to take a closer look at the device.

Regards,
Andrei


#37

We just took it out of the box and flashed it with the latest balenaOS, which said 2.29.2 but the device shows it is running 2.12.3+rev1 with supervisor 7.1.14. So something is odd.

Here’s the filename: balena-cloud-cellmateDev-fincm3-2.29.2+rev2-dev-v9.0.1.img


#39

I just flashed a dashboard downloaded image: balena-cloud--fincm3-2.29.2+rev7-v9.0.1.img.zip. The device came online and you can see that it has full disk available on data partition and also advertises the right version:

root@156f602:~# df -h
Filesystem                         Size  Used Avail Use% Mounted on
devtmpfs                           480M     0  480M   0% /dev
/dev/disk/by-partuuid/73a610f4-02  300M  252M   29M  90% /mnt/sysroot/active
/dev/disk/by-label/resin-state      19M  215K   17M   2% /mnt/state
none                               300M  252M   29M  90% /
tmpfs                              488M   16K  488M   1% /dev/shm
tmpfs                              488M  6.8M  482M   2% /run
tmpfs                              488M     0  488M   0% /sys/fs/cgroup
tmpfs                              488M     0  488M   0% /tmp
tmpfs                              488M   28K  488M   1% /var/volatile
/dev/mmcblk0p1                      40M  8.3M   32M  21% /mnt/boot
/dev/mmcblk0p6                     6.4G   64M  6.0G   2% /mnt/data
/dev/mmcblk0p3                     300M  2.2M  278M   1% /mnt/sysroot/inactive
root@156f602:~# uname -a
Linux 156f602 4.14.98 #1 SMP Mon Feb 18 13:50:25 UTC 2019 armv7l armv7l armv7l GNU/Linux
root@156f602:~# cat /etc/os-release
ID="balena-os"
NAME="balenaOS"
VERSION="2.29.2+rev7"
VERSION_ID="2.29.2"
PRETTY_NAME="balenaOS 2.29.2+rev7"
RESIN_BOARD_REV="910fd15"
META_RESIN_REV="22fffcd"
SLUG="fincm3"
MACHINE="fincm3"
VARIANT="Production"
VARIANT_ID="prod"

What compute module are you using?


#40

I just flashed a dashboard downloaded image: balena-cloud-
root@156f602:~# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 480M 0 480M 0% /dev
/dev/disk/by-partuuid/73a610f4-02 300M 252M 29M 90% /mnt/sysroot/active
/dev/disk/by-label/resin-state 19M 215K 17M 2% /mnt/state
none 300M 252M 29M 90% /
tmpfs 488M 16K 488M 1% /dev/shm
tmpfs 488M 6.8M 482M 2% /run
tmpfs 488M 0 488M 0% /sys/fs/cgroup
tmpfs 488M 0 488M 0% /tmp
tmpfs 488M 28K 488M 1% /var/volatile
/dev/mmcblk0p1 40M 8.3M 32M 21% /mnt/boot
/dev/mmcblk0p6 6.4G 64M 6.0G 2% /mnt/data
/dev/mmcblk0p3 300M 2.2M 278M 1% /mnt/sysroot/inactive
root@156f602:~# uname -a
Linux 156f602 4.14.98 #1 SMP Mon Feb 18 13:50:25 UTC 2019 armv7l armv7l armv7l GNU/Linux
root@156f602:~# cat /etc/os-release
ID=“balena-os”
NAME=“balenaOS”
VERSION=“2.29.2+rev7”
VERSION_ID=“2.29.2”
PRETTY_NAME=“balenaOS 2.29.2+rev7”
RESIN_BOARD_REV=“910fd15”
META_RESIN_REV=“22fffcd”
SLUG=“fincm3”
MACHINE=“fincm3”
VARIANT=“Production”
VARIANT_ID=“prod”
What compute module are you using?


#42

Could you also expand on how exactly you flashed the board? Did you get any errors while doing that?