Upgrade to Buster fails

[fir3drag0n]

Hi,

when I do want to upgrade my rpi1, I get the messages:

Code: Select all

Get: 305 http://raspbian.raspberrypi.org/raspbian buster/main armhf libpython2.7                                                                       -dev armhf 2.7.16-2 [30.9 MB]
Err http://raspbian.raspberrypi.org/raspbian buster/main armhf libpython2.7-dev                                                                        armhf 2.7.16-2
  Error writing to output file - write (28: No space left on device) Error writi                                                                       ng to file - write (28: No space left on device) [IP: 2a00:1098:0:80:1000:75:0:3                                                                        80]
Get: 306 http://raspbian.raspberrypi.org/raspbian buster/main armhf libpython2.7                                                                        armhf 2.7.16-2 [873 kB]
Err http://raspbian.raspberrypi.org/raspbian buster/main armhf libpython2.7 armh                                                                       f 2.7.16-2
  Error writing to output file - write (28: No space left on device) Error writi                                                                       ng to file - write (28: No space left on device) [IP: 2a00:1098:0:80:1000:75:0:3                                                                        80]
Get: 307 http://raspbian.raspberrypi.org/raspbian buster/main armhf python2.7 ar                                                                       mhf 2.7.16-2 [305 kB]
Err http://raspbian.raspberrypi.org/raspbian buster/main armhf python2.7 armhf 2                                                                       .7.16-2
  Error writing to output file - write (28: No space left on device) Error writi                                                                       ng to file - write (28: No space left on device) [IP: 2a00:1098:0:80:1000:75:0:3                                                                        80]
[...]

What can I do in order to solve this?

[trejan]

Your card/drive is full.

[fir3drag0n]

Okay, and what is your solution?

Code: Select all

Linux raspberrypi 4.19.57-v7+ 
pi@raspberrypi:~ $ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        15G  2.5G   12G  18% /
devtmpfs        459M     0  459M   0% /dev
tmpfs           464M  1.9M  462M   1% /dev/shm
tmpfs           464M   30M  434M   7% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           464M     0  464M   0% /sys/fs/cgroup
tmpfs           150M     0  150M   0% /var/cache/apt/archives
tmpfs            20M     0   20M   0% /var/tmp
tmpfs            70M   23M   48M  33% /var/log
tmpfs           100M   16K  100M   1% /tmp
/dev/mmcblk0p1   41M   40M  1.9M  96% /boot
tmpfs            93M     0   93M   0% /run/user/999
tmpfs            93M     0   93M   0% /run/user/1000
pi@raspberrypi:~ $

How can I clean /boot?

Code: Select all

Last login: Tue Aug  6 06:53:12 2019 from 192.168.1.51
pi@raspberrypi:~ $ ls -la /boot
total 39536
drwxr-xr-x  4 root root    3584 Aug  5 20:06 .
drwxr-xr-x 22 root root    4096 Mar  9  2018 ..
-rwxr-xr-x  1 root root   23946 Aug  5 20:06 bcm2708-rpi-b.dtb
-rwxr-xr-x  1 root root   24205 Aug  5 20:06 bcm2708-rpi-b-plus.dtb
-rwxr-xr-x  1 root root   23723 Aug  5 20:06 bcm2708-rpi-cm.dtb
-rwxr-xr-x  1 root root   23671 Aug  5 20:06 bcm2708-rpi-zero.dtb
-rwxr-xr-x  1 root root   24407 Aug  5 20:06 bcm2708-rpi-zero-w.dtb
-rwxr-xr-x  1 root root   25293 Aug  5 20:06 bcm2709-rpi-2-b.dtb
-rwxr-xr-x  1 root root   26463 Aug  5 20:06 bcm2710-rpi-3-b.dtb
-rwxr-xr-x  1 root root   27082 Aug  5 20:06 bcm2710-rpi-3-b-plus.dtb
-rwxr-xr-x  1 root root   25261 Aug  5 20:06 bcm2710-rpi-cm3.dtb
-rwxr-xr-x  1 root root   40284 Aug  5 20:06 bcm2711-rpi-4-b.dtb
-rwxr-xr-x  1 root root   52296 Aug  5 20:03 bootcode.bin
-rwxr-xr-x  1 root root     142 Jan  1  1980 cmdline.txt
-rwxr-xr-x  1 root root    1590 Nov 29  2017 config.txt
-rwxr-xr-x  1 root root   18693 Aug  5 20:06 COPYING.linux
-rwxr-xr-x  1 root root    3030 Aug  5 20:03 fixup4cd.dat
-rwxr-xr-x  1 root root    6068 Aug  5 20:03 fixup4.dat
-rwxr-xr-x  1 root root    9146 Aug  5 20:03 fixup4db.dat
-rwxr-xr-x  1 root root    9148 Aug  5 20:03 fixup4x.dat
-rwxr-xr-x  1 root root    2649 Aug  5 20:03 fixup_cd.dat
-rwxr-xr-x  1 root root    6724 Aug  5 20:03 fixup.dat
-rwxr-xr-x  1 root root    9802 Aug  5 20:03 fixup_db.dat
-rwxr-xr-x  1 root root    9798 Aug  5 20:03 fixup_x.dat
-rwxr-xr-x  1 root root     145 Nov 29  2017 issue.txt
-rwxr-xr-x  1 root root 5299240 Aug  5 20:06 kernel7.img
-rwxr-xr-x  1 root root 5600072 Aug  5 20:06 kernel7l.img
-rwxr-xr-x  1 root root 5017424 Aug  5 20:06 kernel.img
-rwxr-xr-x  1 root root    1494 Aug  5 20:03 LICENCE.broadcom
-rwxr-xr-x  1 root root   18974 Nov 29  2017 LICENSE.oracle
drwxr-xr-x  2 root root   15360 Aug  5 20:07 overlays
-rwxr-xr-x  1 root root  762880 Aug  5 20:03 start4cd.elf
-rwxr-xr-x  1 root root 4716552 Aug  5 20:03 start4db.elf
-rwxr-xr-x  1 root root 2759172 Aug  5 20:03 start4.elf
-rwxr-xr-x  1 root root 3672712 Aug  5 20:03 start4x.elf
-rwxr-xr-x  1 root root  685412 Aug  5 20:03 start_cd.elf
-rwxr-xr-x  1 root root 4854088 Aug  5 20:03 start_db.elf
-rwxr-xr-x  1 root root 2878052 Aug  5 20:03 start.elf
-rwxr-xr-x  1 root root 3791560 Aug  5 20:03 start_x.elf
drwxr-xr-x  2 root root     512 Dec 24  2017 System Volume Information
pi@raspberrypi:~ $

[DougieLawson]

As long as you've got a rescue system you can delete everything in /boot except config.txt and cmdline.txt.
With Buster you need /boot to be 256MB.

With gparted you can't resize FAT32 partitions, you can only delete and recreate them. So copy /boot/cmdline.txt and /boot/config.txt to a safe place (/root or /home/pi) before resizing the /boot partition.

You can use rpi-update (this time only) to repopulate /boot.

If you trash things then lose power you will need a Linux rescue system to recover it. Your Raspberry with another SDCard and a USB reader is perfect as a rescue system.

[fir3drag0n]

The thing is, I already did the upgrade from stretch to buster on a rpi2 without any errors. And the rpi2's /boot drive is now 95% full.

So I guess the error with the rpi1 must be related to something else.