nems upgrade fails with /boot is too full for the upgrade

[HeikoAdams]

Hi,
trying to upgrade NEMS 1.5 to NEMS 1.5.1 on my RPI 3 B+ fails with

/boot is too full for the upgrade

How can I solve this?

[ottl05]

I#ve got the same problem.
my boot:
@nems:/boot $ ls -al
insgesamt 39603
drwxr-xr-x  5 root root    3584 Jan  1  1970  .
drwxr-xr-x 21 root root    4096 Feb 26  2019  ..
-rwxr-xr-x  1 root root   23946 Sep  2 13:09  bcm2708-rpi-b.dtb
-rwxr-xr-x  1 root root   24205 Sep  2 13:09  bcm2708-rpi-b-plus.dtb
-rwxr-xr-x  1 root root   23723 Sep  2 13:09  bcm2708-rpi-cm.dtb
-rwxr-xr-x  1 root root   23671 Sep  2 13:09  bcm2708-rpi-zero.dtb
-rwxr-xr-x  1 root root   24407 Sep  2 13:09  bcm2708-rpi-zero-w.dtb
-rwxr-xr-x  1 root root   25293 Sep  2 13:09  bcm2709-rpi-2-b.dtb
-rwxr-xr-x  1 root root   26463 Sep  2 13:09  bcm2710-rpi-3-b.dtb
-rwxr-xr-x  1 root root   27082 Sep  2 13:09  bcm2710-rpi-3-b-plus.dtb
-rwxr-xr-x  1 root root   25261 Sep  2 13:09  bcm2710-rpi-cm3.dtb
-rwxr-xr-x  1 root root   40559 Sep  2 13:09  bcm2711-rpi-4-b.dtb
-rwxr-xr-x  1 root root   52296 Sep  2 13:09  bootcode.bin
-rwxr-xr-x  1 root root     142 Jan  1  1980  cmdline.txt
-rwxr-xr-x  1 root root    1589 Feb 25  2019  config.txt
-rwxr-xr-x  1 root root   18693 Sep  2 13:09  COPYING.linux
-rwxr-xr-x  1 root root    3046 Sep  2 13:09  fixup4cd.dat
-rwxr-xr-x  1 root root    6089 Sep  2 13:09  fixup4.dat
-rwxr-xr-x  1 root root    9165 Sep  2 13:09  fixup4db.dat
-rwxr-xr-x  1 root root    9167 Sep  2 13:09  fixup4x.dat
-rwxr-xr-x  1 root root    2644 Sep  2 13:09  fixup_cd.dat
-rwxr-xr-x  1 root root    6729 Sep  2 13:09  fixup.dat
-rwxr-xr-x  1 root root    9801 Sep  2 13:09  fixup_db.dat
-rwxr-xr-x  1 root root    9801 Sep  2 13:09  fixup_x.dat
-rwxr-xr-x  1 root root     145 Nov 13  2018  issue.txt
-rwxr-xr-x  1 root root 5310800 Sep  2 13:09  kernel7.img
-rwxr-xr-x  1 root root 5625984 Sep  2 13:09  kernel7l.img
-rwxr-xr-x  1 root root 5026968 Sep  2 13:09  kernel.img
-rwxr-xr-x  1 root root    1494 Sep  2 13:09  LICENCE.broadcom
-rwxr-xr-x  1 root root   18974 Nov 13  2018  LICENSE.oracle
drwxr-xr-x  2 root root   15360 Sep  2 13:09  overlays
-rwxr-xr-x  1 root root  765920 Sep  2 13:09  start4cd.elf
-rwxr-xr-x  1 root root 4723208 Sep  2 13:09  start4db.elf
-rwxr-xr-x  1 root root 2762948 Sep  2 13:09  start4.elf
-rwxr-xr-x  1 root root 3677224 Sep  2 13:09  start4x.elf
-rwxr-xr-x  1 root root  685572 Sep  2 13:09  start_cd.elf
-rwxr-xr-x  1 root root 4855080 Sep  2 13:09  start_db.elf
-rwxr-xr-x  1 root root 2878340 Sep  2 13:09  start.elf
-rwxr-xr-x  1 root root 3792520 Sep  2 13:09  start_x.elf
drwxr-xr-x  2 root root     512 Feb 24  2019 'System Volume Information'
drwxr-xr-x  2 root root     512 Sep  8 00:02  vendor


How could I free up space on boot?

my running kernel:
4.19.66-v7+


I'm running nems on a
cat /proc/device-tree/model

Raspberry Pi 3 Model B Rev 1.2



thanks.

cu
ottl05

[Zunipox]

I had the same issue with /boot being full.
I did some reading on the issue, found several forums dealing with this based on ubuntu, but some on raspberry/raspbian.

Some said you could delete/move "kernel7.img" for example, as the kernel was only used upon boot, and as you can't find kernel version on raspberry (by typing uname -a for example) which you can on ubuntu, that would mean that it was kernel.img that are being used.
I'm not sure if this is correct but that's what the forums said.

So I did move the kernel7.img to /home/USER and could then run the upgrade.
But after reboot it never went up again...
It turned out the SD card got corrupted...

So I'm not sure it's the right way to free up space in /boot this way?
(I had backup so no worries :) )

After the restore, /boot was not full?
But there seems to be some issue with the update process from 1.5 to 1.51, see
https://forum.category5.tv/thread-575.html

[Roccos]

Could it be that the entire process is broken at this point?

[kd4pyr]

I had the same issue. After trying some work arounds to have enough space on /boot I gave up.

I just finished creating downloading and installing v. 1.51 and then followed the instructions for NEMS backup and restore.

Up and running on v. 1.51 as of this morning.

Rick

[ottl05]

I made the same. Backup, "install" new nems and restore.
now I'm running nems 1.5.1