It looks like the dashboard is telling me that this device has over 23G used out of a capacity of under 14G - and it seems confused about which end of the storage bar to mark red.
I’ve enabled support access on that device in case anyone at balena.io is interested in taking a look.
Device seems to be working fine, I suspect the SD card is 32GB, will take it offline and update this post with the partition structure when I finish the tasks I booted it up for.
Both OS and supervisor version are updated today - no reboot or power cycle since either update, so I’ll check whether the issue goes away when I do get round to bringing it down and up again.
It’s a 16GB class 10 Patriot microSD card, the output of lsblk (on an Ubuntu workstation, not the Pi) looks like this:
mmcblk0 179:0 0 14.8G 0 disk
├─mmcblk0p1 179:1 0 40M 0 part
├─mmcblk0p2 179:2 0 320M 0 part
├─mmcblk0p3 179:3 0 320M 0 part
├─mmcblk0p4 179:4 0 1K 0 part
├─mmcblk0p5 179:5 0 20M 0 part
└─mmcblk0p6 179:6 0 14.1G 0 part
Viewing the device an BalenaCloud dashboard after a power cycle still has the same weird pattern - the storage statistic reported is “21.3 GB/13.8 GB”, the bar indicator for storage is grey on the left and red on the right.
Thanks for bringing this to our attention. I haven’t been able to reproduce this so far. Can you provide the UI version from your balenaCloud dashboard, in the lower left under “Changelog”?
We traced this to a bump in systeminformation, the Supervisor’s system info reporting library. The affected version is limited to 17.6.1. We’ll be releasing 17.6.2 soon so keep an eye out for that, and let us know if the issue persists.
As of power on this morning, the storage is reported as 30.0 GB/13.8 GB and the red area which was at the right end of the bar has shrunken to nothing.