Does not start after dist-upgrade

[zo0ok]

I have a RPi2 with Raspbian/jessie/8.0 that has been regularly upgraded. Originally, almost a year ago, it was installed using https://github.com/debian-pi/raspbian-ua-netinst.

Yesterday I did
$ sudo apt-get update
$ sudo apt-get upgrade
and rebooted.

After that I had:
$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
raspberrypi-bootloader-nokernel
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

So I ran (as usual)
$ sudo apt-get dist-upgrade

Now it does not start at all.
HDMI displays "colored splash screen" forever
Serial console outputs: "Uncompressing Linux... done, booting the kernel." (nothing more)

I think dist-upgrade should not make the system unbootable.
The package raspberrypi-bootloader-nokernel was, as far as I understand, already installed before the dist-upgrade, and should be present.

I have (at least) one other RPi where I would run dist-upgrade for the same reason, but now I hesitate.

Did I do anything stupid/was this expected?
What is the correct way to make it boot again?
(not clear to me what files on the FAT32-partition I should delete/replace not just to boot, but also to restore a correctly configured system)

If I can reproduce it I guess its a serious bug.

Any thoughts on this?

[pressy]

Same happen here. After dist-upgrade my raspberian bootet into the color screen.

Code: Select all

Start-Date: 2016-06-11  11:18:27
Commandline: apt-get dist-upgrade
Upgrade: libraspberrypi-doc:armhf (1.20160523-1~nokernel1, 1.20160523-1~nokernel2), libraspberrypi-bin:armhf (1.20160523-1~nokernel1, 1.20160523-1~nokernel2), raspberrypi-bootloader-nokernel:armhf (1.20160523-1~nokernel1, 1.20160523-1~nokernel2), libraspberrypi0:armhf (1.20160523-1~nokernel1, 1.20160523-1~nokernel2), libraspberrypi-dev:armhf (1.20160523-1~nokernel1, 1.20160523-1~nokernel2)
End-Date: 2016-06-11  11:19:31

To make it boot again I hat to override the boot partion with my backup.

This Error is reproducible. After reinstalling it didn't boot again and I had to override the boot partition again from backup.

Code: Select all

Start-Date: 2016-06-11  13:21:44
Commandline: apt-get install --reinstall raspberrypi-bootloader-nokernel
Reinstall: raspberrypi-bootloader-nokernel:armhf (1.20160523-1~nokernel2)
End-Date: 2016-06-11  13:22:39

[zo0ok]

I think the problem may be fixed.

After making a backup of my RPi v1 (700MHz) I did:

Code: Select all

$ sudo apt-get dist-upgrade
[...]
Err http://mirrordirector.raspbian.org/raspbian/ jessie/firmware raspberrypi-bootloader-nokernel armhf 1.20160523-1~nokernel1
  404  Not Found [IP: 5.153.225.207 80]
E: Failed to fetch http://mirrordirector.raspbian.org/raspbian/pool/firmware/r/raspberrypi-firmware-nokernel/raspberrypi-bootloader-nokernel_1.20160523-1~nokernel1_armhf.deb  404  Not Found [IP: 5.153.225.207 80]

I interpreted this as raspberrypi-bootloader-nokernel has been upgraded. So I:

Code: Select all

$ sudo apt-get update
[...]
$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
  libraspberrypi-bin libraspberrypi0
The following NEW packages will be installed:
  firmware-linux-free linux-image-4.4.0-1-rpi
The following packages will be upgraded:
  linux-image-rpi-rpfv raspberrypi-bootloader-nokernel
2 upgraded, 2 newly installed, 2 to remove and 0 not upgraded.
Need to get 21.2 MB of archives.
After this operation, 67.9 MB of additional disk space will be used.

A much bigger upgrade than just raspberrypi-bootloader-nokernel, and obviously a kernel upgrade from 3.18 to 4.4.
The system restarted properly.

I don't know if this applies only to RPi v1, but I would guess the problem is fixed for all RPi versions.

[zo0ok]

It seems 4.4 is installed, but still 3.18 is used. It is not a problem for me, but I find it peculiar.

Code: Select all

~$ ls /boot/
bcm2708-rpi-b.dtb            initrd.img-4.4.0-1-rpi
bcm2708-rpi-b-plus.dtb       installer-rpi1.cpio
bcm2708-rpi-cm.dtb           installer-rpi2.cpio
bcm2709-rpi-2-b.dtb          kernel.img
bcm2710-rpi-3-b.dtb          kernel-rpi1_install.img
bootcode.bin                 kernel-rpi2_install.img
cmdline.txt                  LICENCE.broadcom
config-3.18.0-trunk-rpi      overlays
config-4.4.0-1-rpi           start_cd.elf
config-reinstall.txt         start_db.elf
config.txt                   start.elf
fixup_cd.dat                 start_x.elf
fixup.dat                    System.map-3.18.0-trunk-rpi
fixup_db.dat                 System.map-4.4.0-1-rpi
fixup_x.dat                  vmlinuz-3.18.0-trunk-rpi
initrd.img-3.18.0-trunk-rpi  vmlinuz-4.4.0-1-rpi
$ uname -a
Linux hugin 3.18.0-trunk-rpi #1 PREEMPT Debian 3.18.5-1~exp1+rpi19 (2015-08-08) armv6l GNU/Linux

[SonOfAMotherlessGoat]

Have you rebooted the Pi? FWIU you can't update a running kernel, need to reboot for changes to take effect.

[pressy]

@zo0ok - thx, for the hint with the kernel. After installing linux-image-rpi2-rpfv (i have a version 2) the new kernel was loaded. After investigation I found out, that also an rpi-update needed to be done.

It seems 4.4 is installed, but still 3.18 is used. It is not a problem for me, but I find it peculiar.

By the rpi-update also 4.4 booted on my system.

Code: Select all

Linux rasp01 4.4.13-v7+ #893 SMP Wed Jun 8 14:39:18 BST 2016 armv7l GNU/Linux

Have you rebooted the Pi? FWIU you can't update a running kernel, need to reboot for changes to take effect.

If your read the thread you will find out, that the problem was an unbootable systems (hangs). This you will only find out if you boot.

[zo0ok]

Today I upgraded a RPi v2 with Raspbian that I had not touched since I discoved the problem.

The dist-upgrade was fine.
The system restarted.
It was running kernel 4.4.

I consider the original problem I reported gone. I dont think anyone dist-upgrading now should have this problem.

The RPi v2 that I did upgrade is still in unbootable state. I do not know how to repair it properly. That is not a problem, nothing is lost. But it would still be interesting to know how to repair a broken /boot-partition in a consistent way.
(I mean, copying /boot from a working system would probably be just fine, but it would probably confuse dpkg much)