Out of space on freshly flashed BeagleBone Black

GoogleGroups
1

Hi everyone,

I’m playing around with a BeagleBone Black that I have and I’m trying to flash the onboard eMMC with a new Debian image. I’m using the Debian 9.9 2019-08-03 4GB SD IoT image from https://beagleboard.org/latest-images.

Everything works as I would expect. I can burn the image to a microSD card, boot from it, setup the flasher script, and reboot and it flashes the internal eMMC as expected. The problem is that when I boot from the eMMC there isn’t any space to actually do anything. Here’s the output of df. Is this expected on a fresh install of Debian? Do I need to use a smaller image?

`
debian@beaglebone:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 215M 0 215M 0% /dev
tmpfs 49M 5.4M 44M 11% /run
/dev/mmcblk1p1 3.5G 3.3G 0 100% /
tmpfs 242M 0 242M 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 242M 0 242M 0% /sys/fs/cgroup
tmpfs 49M 0 49M 0% /run/user/1000

`

Thanks,
Mark

2

I fixed this a week later, i don't have access to that server... Just
get the latest Stretch Snapshot:

https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Stretch_IOT_Snapshot

Regards,

3

That doesn't look like the IoT image...

debian@beaglebone:~$ df -h
Filesystem Size Used Avail Use% Mounted on

/dev/mmcblk1p1 3.6G 2.5G 905M 74% /

  Does running the partition resize script make any change?

debian@beaglebone:~$ sudo /opt/scripts/tools/grow_partition.sh
<SNIP>

debian@beaglebone:~$ df -h
Filesystem Size Used Avail Use% Mounted on

/dev/mmcblk1p1 3.6G 2.5G 905M 74% /

{Obviously, no change on my system <G>} I wouldn't expect much on yours
either, but it might find a touch of space.