DigiOne dietpi-update failing due to full /boot partition

I’ve run into an issue running dietpi-update on my Allo DigiOne. It looks like the boot partition is only 42M:

root@DigiOne:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 15G 1.9G 13G 14% /
devtmpfs 455M 0 455M 0% /dev
tmpfs 488M 12K 488M 1% /dev/shm
tmpfs 488M 32M 456M 7% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 488M 0 488M 0% /sys/fs/cgroup
tmpfs 50M 184K 50M 1% /var/log
tmpfs 1023M 0 1023M 0% /tmp
/dev/mmcblk0p1 42M 42M 2.0K 100% /boot

Has anyone run into this before & any suggestions on how to get past it?

Thanks!

Whilst I’m not a dietpi user I can give you some pointers.

You’ve run out of space of /boot which may be caused by not cleaning out kernel images. So, you could try something along the lines of the following. Hopefully, the syntax is correct for dietpi … you may need to substitute apt with apt-get.

sudo apt list --installed | grep linux-image

Please post the output from this. If multiple images are listed you’ll need to remove some images with sudo apt remove. I can assist with this once I’ve seen the kernel versions.

Thanks for the response, and that’s what I was thinking as well (old kernel images) but I actually don’t get anything at all back from that command:

root@DigiOne:~# apt list --installed | grep linux-image
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
root@DigiOne:~#

This is the only/first time I’ve used DietPi, and only because it’s what shipped from Allo — as did the SD card and, I assume, the microscopic /boot partition. :confused:

If I drop the —installed option, I see these:

root@DigiOne:~# apt list | grep linux-image

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

linux-image-3.10-3-rpi/oldstable 3.10.11-1+rpi7 armhf
linux-image-3.16.0-4-rpi/oldstable 3.16.7-ckt4-1+rpi1+b2 armhf
linux-image-3.18.0-trunk-rpi/oldstable 3.18.5-1~exp1+rpi19+stretch armhf
linux-image-3.18.0-trunk-rpi2/oldstable 3.18.5-1~exp1+rpi19+stretch armhf
linux-image-3.6-trunk-rpi/oldstable 3.6.9-1~experimental.1+rpi7 armhf
linux-image-4.4.0-1-rpi/oldstable 4.4.6-1+rpi14 armhf
linux-image-4.4.0-1-rpi2/oldstable 4.4.6-1+rpi14 armhf
linux-image-4.9.0-6-rpi/oldstable 4.9.82-1+deb9u3+rpi1 armhf
linux-image-4.9.0-6-rpi-dbg/oldstable 4.9.82-1+deb9u3+rpi1 armhf
linux-image-4.9.0-6-rpi2/oldstable 4.9.82-1+deb9u3+rpi1 armhf
linux-image-4.9.0-6-rpi2-dbg/oldstable 4.9.82-1+deb9u3+rpi1 armhf
linux-image-rpi/oldstable 4.9+80+deb9u4+rpi1 armhf
linux-image-rpi-dbg/oldstable 4.9+80+deb9u4+rpi1 armhf
linux-image-rpi-rpfv/oldstable 4.9+80+deb9u4+rpi1 armhf
linux-image-rpi2/oldstable 4.9+80+deb9u4+rpi1 armhf
linux-image-rpi2-dbg/oldstable 4.9+80+deb9u4+rpi1 armhf
linux-image-rpi2-rpfv/oldstable 4.9+80+deb9u4+rpi1 armhf

That’s odd … can you post from ls -Fla /boot. I’d expect to only see kernels listed by apt --installed in /boot.

It may be easier to download Ropieee and install that on the flash drive. Works perfectly with the DigiOne. :slight_smile:

Yeah, I thought it was odd as well.

Good to know that Ropieee is an option. Part of my hesitation with just diving in, despite some (admittedly rusty) experience in *nix, is that the thing came “pre-configured”. :slight_smile:

Here’s the ls:

root@DigiOne:~# ls -Fla /boot
total 39683
drwxr-xr-x 5 root root 3584 Jan 1 1970 ./
drwxr-xr-x 21 root root 4096 Jul 18 2020 …/
-rwxr-xr-x 1 root root 23219 Aug 16 2018 bcm2708-rpi-0-w.dtb*
-rwxr-xr-x 1 root root 23966 Sep 18 2019 bcm2708-rpi-b.dtb*
-rwxr-xr-x 1 root root 24229 Sep 18 2019 bcm2708-rpi-b-plus.dtb*
-rwxr-xr-x 1 root root 23747 Sep 18 2019 bcm2708-rpi-cm.dtb*
-rwxr-xr-x 1 root root 23671 Sep 18 2019 bcm2708-rpi-zero.dtb*
-rwxr-xr-x 1 root root 24407 Sep 18 2019 bcm2708-rpi-zero-w.dtb*
-rwxr-xr-x 1 root root 25293 Sep 18 2019 bcm2709-rpi-2-b.dtb*
-rwxr-xr-x 1 root root 26463 Sep 18 2019 bcm2710-rpi-3-b.dtb*
-rwxr-xr-x 1 root root 27082 Sep 18 2019 bcm2710-rpi-3-b-plus.dtb*
-rwxr-xr-x 1 root root 25277 Sep 18 2019 bcm2710-rpi-cm3.dtb*
-rwxr-xr-x 1 root root 40559 Sep 18 2019 bcm2711-rpi-4-b.dtb*
-rwxr-xr-x 1 root root 52296 Sep 18 2019 bootcode.bin*
-rwxr-xr-x 1 root root 142 Jul 18 2020 cmdline.txt*
-rwxr-xr-x 1 root root 2364 Sep 11 02:49 config.txt*
-rwxr-xr-x 1 root root 18693 Jul 2 2019 COPYING.linux*
drwxr-xr-x 4 root root 3584 Jan 18 16:00 dietpi/
-rwxr-xr-x 1 root root 6129 Aug 14 2018 dietpi-README.md*
-rwxr-xr-x 1 root root 10624 Jul 18 2020 dietpi.txt*
-rwxr-xr-x 1 root root 41 Aug 16 2018 .firmware_revision*
-rwxr-xr-x 1 root root 3073 Sep 18 2019 fixup4cd.dat*
-rwxr-xr-x 1 root root 6169 Sep 18 2019 fixup4.dat*
-rwxr-xr-x 1 root root 9249 Sep 18 2019 fixup4db.dat*
-rwxr-xr-x 1 root root 9247 Sep 18 2019 fixup4x.dat*
-rwxr-xr-x 1 root root 2657 Sep 18 2019 fixup_cd.dat*
-rwxr-xr-x 1 root root 6736 Sep 18 2019 fixup.dat*
-rwxr-xr-x 1 root root 9806 Sep 18 2019 fixup_db.dat*
-rwxr-xr-x 1 root root 9808 Sep 18 2019 fixup_x.dat*
-rwxr-xr-x 1 root root 1024 Jan 1 1980 FSCK0000.REC*
-rwxr-xr-x 1 root root 145 Jun 20 2019 issue.txt*
-rwxr-xr-x 1 root root 5310552 Sep 18 2019 kernel7.img*
-rwxr-xr-x 1 root root 5628360 Sep 18 2019 kernel7l.img*
-rwxr-xr-x 1 root root 5027744 Sep 18 2019 kernel.img*
-rwxr-xr-x 1 root root 1494 Jul 2 2019 LICENCE.broadcom*
-rwxr-xr-x 1 root root 18974 Mar 13 2018 LICENSE.oracle*
drwxr-xr-x 2 root root 15360 Nov 7 2019 overlays/
-rwxr-xr-x 1 root root 6129 Aug 14 2018 README.md*
-rwxr-xr-x 1 root root 770560 Sep 18 2019 start4cd.elf*
-rwxr-xr-x 1 root root 4732968 Sep 18 2019 start4db.elf*
-rwxr-xr-x 1 root root 2769380 Sep 18 2019 start4.elf*
-rwxr-xr-x 1 root root 3683656 Sep 18 2019 start4x.elf*
-rwxr-xr-x 1 root root 685604 Sep 18 2019 start_cd.elf*
-rwxr-xr-x 1 root root 4854696 Sep 18 2019 start_db.elf*
-rwxr-xr-x 1 root root 2877956 Sep 18 2019 start.elf*
-rwxr-xr-x 1 root root 3792200 Sep 18 2019 start_x.elf*
drwxr-xr-x 2 root root 512 Jul 2 2019 System Volume Information/
root@DigiOne:~#

Problem solved… sorta: Installed RoPieee rather than bothering with expanding the partition. Thanks @Martin_Webster for the suggestion. :slight_smile:

1 Like